04:46 <Guest35> hi guys, can command like cortex_m be used with hla_swd? I tried to use it with stlink dongle but got "invalid command name "cortex_m""

07:25 <PaulFertser> Guest35: no, it can't. hla_swd is very limited. But with new enough stlink firmware you can use the "dap" mode.

08:54 <karlp> the cortexm profiling works on hla_swd though, at least. though I think that bypasses the cortex_m command,

08:55 <karlp> hrm, yeah, iirc I had to hook that up on the side

08:55 <karlp> profiling is higher level and has a cortex_m and a hla_target implementaition

08:55 <karlp> nvm then :)

08:56 <karlp> Guest35: which commands were you hoping to be using?

11:09 <indy> olerem, hi, were you able to get more informations regarding nexus in rh850?

11:13 <olerem> indy: hi. no. I do not have any projects with this chip, so was not trying to get NDA docs

13:44 <Guest1295> Good day.

13:44 <Guest1295> This is Keshav from Germany.

13:44 <Guest1295> I am a beginner with OpenOCD and TCL programming. I am in the process of trying to find out how to flash multiple STM32 microcontroller targets as JTAG Chain. I am able to individually flash one target at a time. But I need help in understanding how I could do that for more than 1 target in a chain.

13:44 <Guest1295> It would be amazing if I am advised on how to proceed with this.

13:44 <Guest1295> Thank you.

13:46 <Guest1295> I am using a ST-Link v2 debugger

13:58 <keshav> "C:\Program Files\GNU ARM Eclipse\OpenOCD\0.10.0-201601101000-dev\bin\openocd" -f "C:\Program Files\GNU ARM Eclipse\OpenOCD\0.10.0-201601101000-dev\scripts\interface\stlink-v2.cfg" -f "C:\Program Files\GNU ARM Eclipse\OpenOCD\0.10.0-201601101000-dev\scripts\target\stm32f3x.cfg" -c init -c targets -c "halt" -c "flash  erase_sector 0 0 127" -c

13:58 <keshav> "reset halt" -c "flash write_image C:/Users/Buero-1/Desktop/openOCD/init.hex" -c "verify_image C:/Users/Buero-1/Desktop/openOCD/init.hex" -c "reset run" -c shutdown

13:58 <keshav> This is the code I execute to flash single STM32 microcontrollers.

13:59 <karlp> unrelated, bu you can in general simplifyt that to "openocd -f interface/stlink-v2.cfg -f target/stm32f3x.cfg blah blah"

13:59 <karlp> the install path of oocd is implied.

14:00 <karlp> I'm not sure the high level interface that stlink provides gives enough access to the jtag chain to do it honestly, but you'll definitely need to add more commands to run in jtag mode.

14:00 <karlp> stlink will default to swd, which is single target (stlink doesn't support multidrop at least, and not all targets do either)

14:03 <karlp> you might get far enough with -f interface/stlink-v2.cfg -c "transport_select jtag" and see what's autodetected as taps.

14:03 <karlp> but not my field sorry

14:03 <karlp> you'll benefit a lot from updating to 0.11 as well.

14:03 <bencoh> how is that multidrop thing supposed to work though?

14:04 <karlp> multidrop swd? don't remember the details, but it's documented on arm if you want to go have a read.

14:04 <karlp> but yeah, _very_ few targets that support it, let alone debuggers.

14:05 <bencoh> I found a mux from TI

14:06 <bencoh> (for those wondering, see the multi-device link at https://developer.arm.com/architectures/cpu-architecture/debug-visibility-and-trace/coresight-architecture/serial-wire-debug )

14:11 <keshav> Hi again. Thanks for the response. I tried setting it up to Jtag as you mentioned. I might be a bit stupid on how to go around with this since this is probably the first week I am working with OpenCAD and TCL.

14:11 <keshav> But I executed this code

14:11 <keshav> "C:\Program Files\GNU ARM Eclipse\OpenOCD\0.10.0-201601101000-dev\bin\openocd" -f "C:\Program Files\GNU ARM Eclipse\OpenOCD\0.10.0-201601101000-dev\scripts\interface\stlink-v2.cfg" -f "transport_select jtag" -c

14:11 <keshav> and it threw an error that says

14:11 <keshav> C:\Program Files\GNU ARM Eclipse\OpenOCD\0.10.0-201601101000-dev\bin\openocd: option requires an argument -- c

14:11 <keshav> embedded:startup.tcl:60: Error: Can't find transport_select jtag

14:11 <keshav> in procedure 'script'

14:11 <keshav> at file "embedded:startup.tcl", line 60

14:12 <PaulFertser> keshav: it means what it says

14:12 <PaulFertser> keshav: stlink doesn't support jtag

14:12 <PaulFertser> keshav: use some proper adapter if you have more than one device on the jtag chain.

14:14 <keshav> Hi PaulFertser, thank you for your response.

14:14 <keshav> That is a bummer. Is there an adapter that you would recommend in this case?

14:14 <PaulFertser> keshav: if you need something fast, right there right now, take raspberrypi or some other single-board computer if you have one around.

14:15 <PaulFertser> keshav: if you're doing it for non-commercial purposes, consider getting jlink edu.

14:15 <PaulFertser> keshav: you can

14:15 <PaulFertser> also get busblaster. Or Olimex. Or TUMPA.

14:15 <PaulFertser> Or some reasonable CMSIS-DAP device.

14:15 <PaulFertser> Plenty of options.

14:16 <karlp> oh, there's hla_jtag

14:16 <karlp> stlink does support jtag paul.

14:16 <PaulFertser> No, it doesn't really work for anything.

14:16 <PaulFertser> iirc it's for TI "icdi" hla.

14:17 <karlp> pretttttty sure it works for stlink as well, but I'm not motivated enough to go and dig out appropriate hardware right now :)

14:17 <PaulFertser> keshav: stlink "supports" jtag in a useless way, it's so stupid that nobody bothered to implement it.

14:17 <karlp> does dap mode on anewer stlink firmware work then?

14:17 <karlp> or is that an swd only mode?

14:18 <PaulFertser> I do not remember but probably you can use stlink with jtag only if stm32 is the first on the chain.

14:23 <keshav> That means if there are multiple stm32s in the chain, it wont work with ST-link, but if there are other microcontrollers after the stm32, then it would work?

14:23 <PaulFertser> keshav: idk and I never saw any reason to bother. It's not like there's shortage of saner debug adapters.

14:26 <PaulFertser> keshav: also stlinkv3 seems to be incompatible with everything that's not stm32 _on purpose_ which was plain nasty on the side of the stlink firmware team.

14:28 <keshav> Thanks a lot Karl and Paul. I will look more into other adapters that I could use for this application and will get back on this. Thanks again

14:28 <PaulFertser> keshav: don't you already have some?

14:29 <PaulFertser> keshav: you can even use a "blue pill" for that with appropriate (cmsis-dap) firmware.

14:30 <keshav> I unfortunately dont have other adapters except Olimex.

14:30 <keshav> And the disadvantage with Olimex is that i am unable to find a driver which works for windows 11 and the last driver available is from 2017

14:31 <keshav> I tried to test it to run for single target flashing and it doesnt communicate with win11

14:31 <PaulFertser> keshav: Olimex is awesome

14:32 <PaulFertser> keshav: and you do not need to be looking for any driver for it dammit

14:32 <PaulFertser> keshav: you need WinUSB from Microsoft themselves, and you can install it with Zadig. Read README.Windows in OpenOCD.

14:37 <keshav> I istalled the driver through Microsoft and Zadig 2.7 today. But somehow Olimex did not respond in Windows 11 OpenOCD. The same thing worked in Windows 10 with all the same circumstances.

14:37 <keshav> That is why I thought of maybe shifting to ST Link v2

14:37 <PaulFertser> keshav: did you install it for the composite device parent?

14:39 <keshav> Do you mean the first interface (Interface 0) of Olimex?

14:40 <PaulFertser> keshav: no, the composite device parent

14:44 <keshav> I do not think I did.

14:44 <keshav> I installed the driver directly through Zadig as I connected the olimex device

14:45 <PaulFertser> keshav: please do

14:45 <PaulFertser> Unless windows 11 broke USB in some horrible way it should work...

14:46 <keshav> I will try it out for sure.

14:46 <keshav> I have an Olimex-arm-usb-ocd-h with me

14:47 <PaulFertser> keshav: I have used this device many times, it's quite nice.

14:48 <keshav> I have a similar program as mentioned above to run flash on a single target with it. Except the cfg file for olimex differs. Do you think I could run jtag chain with this code?

14:48 <keshav> "C:\Program Files\GNU ARM Eclipse\OpenOCD\0.10.0-201601101000-dev\bin\openocd" -f "C:\Program Files\GNU ARM Eclipse\OpenOCD\0.10.0-201601101000-dev\scripts\interface\ftdi\olimex-arm-usb-ocd-h.cfg" -f "C:\Program Files\GNU ARM Eclipse\OpenOCD\0.10.0-201601101000-dev\scripts\target\stm32f3x.cfg" -c init -c targets -c "halt" -c "flash  erase_sector 0

14:48 <keshav> 0 127" -c "reset halt" -c "flash write_image C:/Users/Buero-1/Desktop/openOCD/init.hex" -c "verify_image C:/Users/Buero-1/Desktop/openOCD/init.hex" -c "reset run" -c shutdown

14:49 <PaulFertser> keshav: of course. BTW, it looks like your OpenOCD is quite old. It's year 2021 now.

14:50 <keshav> I noticed. I had an installed which was ancient in our server that I installed. I just noticed as Karl mentioned that I have to update it

14:51 <PaulFertser> keshav: please use some pastebin the next time to show what it has to say about your olimex once you install winusb on the composite device.

14:51 <keshav> I definitely will and I will keep you posted. Thank you so much.

15:25 <karlp> are you targetting a _board_ with multiple stm32s, or are ou trying to make a mass flashing thing? I'm asking if it realllly need to be multiple stm32s on the chain, of if your needs would be met by N*USB devices, instead....

15:37 <GyrosGeier> FWIW, I have the same problem

15:37 <GyrosGeier> a panel with 8 STM32 based boards

15:37 <bencoh> but are they all connected in a jtag chain?

15:37 <GyrosGeier> before they are separated, that is a single long chain

15:38 <bencoh> ah

16:08 <karlp> I'dpersonally have designed it to just get 8x stlinks pinned on, avoids all the fuckaround with jtag chains... but hey, if you built it like that.

16:08 <karlp> are you planning on using actual boundary scan or was this just what someone said "was the way things are done" ?

16:27 <PaulFertser> I think it's neat to be able to flash the whole panel by connecting to it once.

16:30 <GyrosGeier> yes

16:30 <GyrosGeier> but I've found it to be overrated

16:31 <GyrosGeier> most assembly houses will run a SVF file for you after assembly at little to no extra cost

16:32 <GyrosGeier> and they don't care whether they need to connect to a single set of test points or multiple

16:32 <GyrosGeier> if the download takes very long, then an SVF that programs all at once would be beneficial

16:33 <GyrosGeier> but you don't save that much, because you still need to shift all the bits

16:34 <GyrosGeier> (and for machines with enough probe tips, it is faster to have one JTAG connection per board and let it run in parallel)

16:40 <PaulFertser> How do you convert stm32 flashing procedure to SVF

16:40 <PaulFertser> ?

20:50 <karlp> what gyrosgeir is mostly my feeling as well. it soudns cute and all, but it doesn't really save you anything

21:35 <antto> wtf... https://i.imgur.com/uOWFopn.png