10:39 <IoT-Maker> Hi, i got a problem getting openocd to work with an am335x CPU.   I use an Olimex Tiny H adapter. I start with openocd -d1 -f interface/ftdi/olimex-arm-usb-tiny-h.cfg -f target/am335x.cfg and get the error am335x.jrc: IR capture error; saw 0x3f not 0x01

10:40 <IoT-Maker> when connecting to the server, scan_chain finds "2 am335x.jrc             Y     0x00000000 0x*b94402f     6 0x01  0x3f"

10:43 <IoT-Maker> In windows i checked with Topprobe which finds 2B94402Fh as a Target.

10:52 <IoT-Maker> i found two bsdl files, AM335x_ZCZ.bsd and  F781962A.bsdl which i can use with Topprobe/Topflash in Windows. The Olimex adapter seems not to be the problem because i can find the Chip with Topprobe/Topflash/openocd. Any idea what might be the culprit why i can't use the am335x.cfg with the chip? This is the -d3 output when starting openocd

10:52 <IoT-Maker> https://bpa.st/HYMGM

10:59 <PaulFertser> IoT-Maker: hii

10:59 <PaulFertser> IoT-Maker: please use some pastebin to show full OpenOCD output.

10:59 <PaulFertser> Along with the invocation command line

11:03 <IoT-Maker> PaulFertser https://bpa.st/HYMGM

11:06 <IoT-Maker> TRST/SRST is not connected to the adapter. Jtagulator found some candidates but none of them seems to be working. So i left it unconnected

11:07 <PaulFertser> IoT-Maker: "JTAG scan chain interrogation failed: all ones" is where it's already wrong.

11:07 <PaulFertser> IoT-Maker: Is 6 MHz not too high for the setup? Is your Topprobe using same speed?

11:08 <IoT-Maker> yes, that was the default speed in Topprobe for Olimex

11:09 <PaulFertser> IoT-Maker: the JTAG scan chain interrogation is very basic thing, and MPSSE protocol of FTDI doesn't allow any possibility to swap TMS/TCK/TDO/TDI signals.

11:09 <PaulFertser> IoT-Maker: do I understand it right that without changing anything in hardware at all you start topprobe and it's able to read JTAG idcode?

11:11 <PaulFertser> IoT-Maker: it looks like you made some manual changes to interface/ftdi/olimex-arm-usb-tiny-h.cfg ?

11:13 <IoT-Maker> PaulFertser same error when starting with 100kHz https://bpa.st/KE4G6

11:15 <PaulFertser> Please do not modify upstream configs, that's confusing.

11:15 <IoT-Maker> PaulFertser i added adapter settings https://bpa.st/VX2GO

11:17 <PaulFertser> IoT-Maker: do you confirm the very same hardware without any changes works with topprobe?

11:17 <PaulFertser> IoT-Maker: settings like that should be added in command line or openocd.cfg , without changing the installed configs normally.

11:18 <PaulFertser> You do not need serial if you have just one adapter connected.

11:19 <IoT-Maker> yes and it works on another device. The device i'm working on is a Rigol DG2052. Last week the same openocd config worked on a Rigol DS1054Z.

11:20 <IoT-Maker> i tried serial because i read that in the Olimex manual. Was just a try.

11:25 <IoT-Maker> could the missing trst/srst line be the problem?

11:29 <PaulFertser> IoT-Maker: it shouldn't be in general. TRST should have pull ups on the board or internally.

11:30 <PaulFertser> IoT-Maker: but topprobe works without srst connected, so openocd should too

11:30 <PaulFertser> IoT-Maker: are you sure you connected just those 4 signals and GND and nothing else?

11:32 <IoT-Maker> The Rigol DG2052 has  a Spartan 6 and nearby exposed jtag pin holes, TMS, TDI, TDO, TCK, GND, VCC, no xRST Pin. The daughterboard with the Ti AM3352 i'm working on has a 20 pin connector with unknown connections. The Jtagulator found the jtag pins TMS, TDI, TDO and TCK and also 4 TRST pins. I tested all of them. And since none of them worked, they

11:32 <IoT-Maker> are now unconnected.

11:33 <PaulFertser> IoT-Maker: you can get a USB dump of communications from topprobe and compare to that of OpenOCD. But I so far suspect there's some difference in hardware when you're running topprobe and openocd.

16:48 <IoT-Maker> PaulFertser Don't know how i can grab a USB dump of my USB communication from OracleVM. But I tried different adapters now. CJMCU-323h https://bpa.st/HPTD4 TIAO-tumpa https://bpa.st/KP6PW Jlink https://pastebin.ubuntu.com/p/YhHPrXzCbj/ and the olimex tiny h from above. scan_chain and targets show me this https://bpa.st/CKNSA IdCode seems wrong.

17:13 <IoT-Maker> wow, i just started a uart session and stopped the system in uboot shell an you know what?  I just worked with the cjmcu-232h adapter https://bpa.st/OF4XA but after halt command it rebooted after some seconds

18:01 <Mis012[m]> PaulFertser: what does this mean? is it trying to access some non-existent AP?

22:11 <Guest14> I am still relatively new to openocd. Can anyone tell me if it is able to read/flash an SST29LE010 chip?

22:12 <PaulFertser> Guest14: hi

22:13 <PaulFertser> Guest14: connected to an MCU?

22:15 <PaulFertser> Guest14: it's not a CFI part but you can just use a series of suitable mdw/mww commands instead I guess.

22:16 <Guest14> I have a bricked xplorer64 cartridge (see https://europe1.discourse-cdn.com/arduino/original/4X/c/f/7/cf7a40452a22f0c32ce5a1eb2be9506fb392dd84.jpeg)

22:17 <Guest14> The PLD is a ATF1508AS

22:18 <Guest14> Is there any documentation/tutorials that could point in the right direction to using mdw/mww commands? I'd need to write my own .cfg file right?

22:27 <Guest14> I noticed that the ATF1508AS has JTAG pins, could I use these to flash the SST29LE010 chips?