11:41 <Haohmaru> does openocd allow specifying the chip or chip ID or something, so that if it's not "the expected flavor of chip" things can be aborted?

11:42 <PaulFertser> Haohmaru: let's discuss specifics

11:42 <PaulFertser> e.g. stm32f4 variant?

11:42 <Haohmaru> sam e5x/d5x and samd20 variants

11:43 <Haohmaru> basically, the variants with different amounts of flash/ram

11:43 <PaulFertser> I suggest using Tcl to parse [flash info 0]

11:44 <Haohmaru> i see openocd detects enough of the relevant letters from the part number

11:44 <Haohmaru> "SAMD20E16A" <- that contains the variant, the flash/ram size, the number of pins, even the hardware revision

11:44 <Haohmaru> hm, i don't schprachen ze tcl :/

11:46 <Haohmaru> a possible other way i could think of is if it allowed you to specify a concrete part number, and if that's not the chip connected - abort the whole command (in my case, i'm invoking openocd from a .sh script to flash and verify an .elf, so aborting the whole command would be good enough perhaps)

20:12 <xenlauz> Hey, I find that Openocd user manual describes (a) "Config commands" which we can use in the e.g. openocd.cfg but user manual also documents (b) "Commands" which I don't know how to use. Can anyone tell me how to use these commands?

20:14 <xenlauz> Never mind. I found it! Thanks.