boru has quit [Killed (NickServ (GHOST command used by boru`))]
boru` is now known as boru
tsal has quit [Ping timeout: 245 seconds]
tsal has joined #openocd
indy has quit [Ping timeout: 264 seconds]
indy has joined #openocd
Hawk777 has joined #openocd
zjason` has joined #openocd
zjason has quit [Read error: Connection reset by peer]
rkta_ has joined #openocd
rkta has quit [Remote host closed the connection]
Haohmaru has joined #openocd
Hawk777 has quit [Quit: Leaving.]
zjason` is now known as zjason
wingsorc has joined #openocd
tarekb has joined #openocd
troth has quit [Quit: Leaving]
Haohmaru has quit [Remote host closed the connection]
wingsorc has quit [Quit: Leaving]
crabbedhaloablut has joined #openocd
tarekb has quit [Quit: Leaving.]
<_franck_>
I've understood the flash memory operations (erase, flash, compare) part of the Renesas FINE protocol (at least for RX devices). However, I didn't work on the debug operations.
<_franck_>
would it be ok to put this into openocd ? Because openocd is not a flashing tool but more a debug interface controller tool, I'm not sure.
<_franck_>
Or, I'll wait until I have a working debug interface...
sys64738 has quit [Ping timeout: 272 seconds]
sbach has quit [Ping timeout: 272 seconds]
sys64738 has joined #openocd
Hawk777 has joined #openocd
sbach has joined #openocd
<PaulFertser>
_franck_: flashing is already nice if you can do it with OpenOCD. E.g. support for atmega is just flashing, no debug.
Fleck has quit [Remote host closed the connection]