crabbedhaloablut has quit [Remote host closed the connection]
crabbedhaloablut has joined #openocd
IoTMaker has quit [Quit: Client closed]
thinkfat_ has quit [Remote host closed the connection]
thinkfat has joined #openocd
thinkfat has quit [Quit: Konversation terminated!]
renrelkha has quit [Quit: bye]
renrelkha has joined #openocd
<PaulFertser>
phr3ak: forum is useless.
<PaulFertser>
phr3ak: mailing list or IRC or if you found a bug please create a ticket.
IoTMaker has joined #openocd
<zapb_>
PaulFertser, maybe we should remove the forum link at all?
<PaulFertser>
zapb_: guess so, I just thought it was still kinda working and that some people were still using it.
<zapb_>
PaulFertser, it's no "official" OpenOCD forum anyway
<PaulFertser>
Spencer used to be quite active there I think.
<phr3ak>
a forum would be good, eg to discuss issues related to various programmers
<PaulFertser>
How is the mailing list any worse for that?
<phr3ak>
I think the advantage of a forum is that it is easier to find and display information if it is already stored in a structured way.
IoTMaker has quit [Ping timeout: 260 seconds]
IoTMaker has joined #openocd
<PaulFertser>
phr3ak: web forums are usually much worse structured than a threaded mailing list archive.
<IoTMaker>
PaulFertser i was able to read a memory dump with jlink commander from am335x device. Here's a log from jlink but doesn't look useful to me https://pastebin.ubuntu.com/p/mc72XZfT6x/
<phr3ak>
IRLen: 04 is it bits or bytes?
<phr3ak>
I suppose bytes
<borneoa__>
phr3ak: irlen is in bits
<phr3ak>
oh really, the basic instructions are quite short
buldi has joined #openocd
nerozero has quit [Ping timeout: 255 seconds]
buldi777 has joined #openocd
crabbedhaloablut has quit [Ping timeout: 255 seconds]
<borneoa__>
phr3ak: that's only for the JTAG interface. Then after JTAG you can have something by far more complex
crabbedhaloablut has joined #openocd
buldi777 has quit [Quit: Leaving]
buldi has quit [Quit: Leaving]
crabbedhaloablut has quit [Ping timeout: 255 seconds]
crabbedhaloablut has joined #openocd
ttmrichter has quit [Ping timeout: 248 seconds]
<IoTMaker>
@ph3ak Interesting, i just noticed that this is the different between openocd and JLink Commander. openocd does not show up the id of the second device. JLink Commander show me #0 Id: 0x3BA00477, IRLen: 04, CoreSight JTAG-DP and the one that openocd identifies LAO #1 Id: 0x2B94402F, IRLen: 06, TI ICEPick. Openocd show me 0x0000000 as IdCode for
<IoTMaker>
the second one.
<Mis012[m]>
IoTMaker: hm, does it print a description for the ID?
<Mis012[m]>
it doesn't seem to with SWD
<IoTMaker>
Mis012[m] description in openocd or JLink Commander?
<Mis012[m]>
openocd
<Mis012[m]>
Info : 61 75 adi_v5_swd.c:370 swd_connect_single(): SWD DPIDR 0x5ba02477
<Mis012[m]>
clearly this should be a well-known ID
<IoTMaker>
openocd show me this https://bpa.st/ICIZS am335x jrc -irlen 6 -ircapture 0x1 -irmask 0x3f -expected-id 0x0b94402f and twotimes -irlen 4 -ircapture 0x1 -irmask 0xf -expected-id 0x4b6b902f
<IoTMaker>
does adi_v5_swd... mean a SWD connection? I didn't use SWD port and didn't configure the interface for SWD.
IoTMaker has quit [Ping timeout: 260 seconds]
<Mis012[m]>
I'm just wondering why it shows a textual description for JTAG but not for SWD