boru has quit [Killed (NickServ (GHOST command used by boru`))]
boru` is now known as boru
<_franck_>
Ok great, I'll work on it
Hawk777 has quit [Quit: Leaving.]
crabbedhaloablut has quit [Remote host closed the connection]
crabbedhaloablut has joined #openocd
zapb has left #openocd [Leaving]
zapb has joined #openocd
rkta_ is now known as rkta
Hawk777 has joined #openocd
rudar has joined #openocd
Hawk777 has quit [Quit: Leaving.]
_franck_7 has joined #openocd
_franck_ has quit [Ping timeout: 252 seconds]
_franck_7 is now known as _franck_
Hawk777 has joined #openocd
rudar has quit [Quit: Leaving]
<_franck_>
zapb: do you have more information about the 0xE0 command of the JLink ? From what I've read it should be FINE read/write.
<_franck_>
I could figure it out by reversing the JLink firmware but that would take some time
<_franck_>
for your information, in order to use the Renesas FINE interface you need to control the reset pin and use an half duplex UART
<zapb>
_franck_, yes, 0xe0 is CMD_HW_FINE_WRITE_READ
<zapb>
_franck_, do you need libjaylink support?
<_franck_>
zapb: would be great
<_franck_>
I understood how FINE works (at least for the programming) and I wanted to add this to openocd
<zapb>
_franck_, What have you already done for FINE support?
<_franck_>
I talk with my target (Renesas RX) with a microcontroller (emulating FINE)
<_franck_>
I can connect to target, send ID code and read memory
<zapb>
_franck_, nice, what target exactly?
<_franck_>
RX65
<zapb>
Okay, I have somewhere an RPBRX111
<zapb>
I also have some rough understanding how FINE works on the J-Link protocol
<_franck_>
I don't ask you to do the job :) But yes, if you could tell me how you think FINE is handled on the JLink, I could give it a try then you can try on your target
<zapb>
_franck_, maybe I can push a branch with initial support you can base your work on
<_franck_>
ok cool, thanks
<_franck_>
first, I'll write a test program using libjaylink then when it works I can try to include this into openocd
<zapb>
_franck_, is it correct that every operation on the protocol is address based?
<_franck_>
I don't understand
<_franck_>
available commands for the bootloader serial interface are described in the RX reference manual. FINE commands are almost the same.
<zapb>
From my understanding there is only a single FINE command on the J-Link protocol that performs a read / write from / to an address
<_franck_>
so the JLink is not a "passive" interface ? It knows some of the protocol
<_franck_>
I though this command would just send/receive bytes to/from the FINE data line
<zapb>
_franck_, maybe there is a even more low-level command but at the moment I'm not aware of any
<_franck_>
ok so with this command it should be possible to read/write memory without knowing the protocol ?
<_franck_>
I really need to reverse the firmware to see what's going on
<_franck_>
ths first this is:
<_franck_>
H: 9D 43 75 C0
<_franck_>
D: 23 02
<_franck_>
the host ask for a chip id, the device answer back
<_franck_>
if you could check the JLink firmware you have to see if you can find 9D 43 in it....
<_franck_>
I have a V11 firmware, I can binary grep
ipatch has joined #openocd
<_franck_>
oh no, I don't have one
<zapb>
_franck_, is this an USB dump?
<_franck_>
no, raw FINE
<_franck_>
host means debug interface
<zapb>
_franck_, if you have an USB dump of the communication with the J-Link that would be helpful
<zapb>
At the moment I don't have access to my target
ipatch has quit [Client Quit]
<_franck_>
I don't, I use an Renesas E2 lite interface
<_franck_>
it's embedded on my eval board
<_franck_>
when I have time, I'll use the JLink with the renesas programmer (it's possible) and do an USB dump
<_franck_>
I'll ping you
<zapb>
Ah, I see
<zapb>
_franck_, sure, let me know if I can help you