16:56 <karlp> when haohmaru comes back, pickit basic is out now, which is usb-hs, cmsis-dap, all sorts: https://www.microchip.com/en-us/development-tool/PG164110

16:57 <karlp> looks pretty decent honestly.

17:04 <PaulFertser> antto is still here

17:17 <antto> hm?

17:24 <antto> i'll throw an eyeball

18:25 <NishanthMenon> borneoa___: when ever you get a chance, two very recent series (should be not controversial, I hope): https://review.openocd.org/c/openocd/+/8792 https://review.openocd.org/c/openocd/+/8798 and ofcourse the older mspm0 series https://review.openocd.org/c/openocd/+/8386

19:02 <antto> karlp, that's not bad.. maybe for $job (we might need another programmer for f*cking pics)

19:03 <antto> otherwise for me personally - if it works as cmsis-dap - good, but i don't see UART, so i find this daplink more convenient (i put SWD and UART TX/RX onto the debugger connector on my boards for convenience)

21:27 <karlp> NishanthMenon: my biggest confusion with that series, and all the ones before, is who uses the k3 nomenclature?

21:28 <karlp> given that's what the user is meant to know.

21:28 <pi0> PaulFertser: can you kindly suggest a cfg for this type of board, https://keeb.io/products/supermini-nrf52840-pro-micro-bluetooth-le-ble-controller

21:28 <pi0> anyone can also chime in if they know

21:29 <karlp> pi0: -f interface/whateveryouhave.cfg -f target/nrf52.cfg?

21:30 <karlp> not you would need to use the tiny pads on the side of the board, because, "lol, fuck debug"

21:31 <pi0> i found a guy on discord that created a custom pcb and sent me the file, i will snap some pics of it when i get home

21:32 <pi0> i agree it was a terrible design and not fair for ppl

21:32 <karlp> I dunno, keeb people seem towant to live in that world, "I just want to to configure my keymap and I'm done"

21:33 <PaulFertser> Heh, yes, too tiny to fit 2 extra signals:)

21:33 <pi0> i actually want to use these with the nrf52480 ble sniffer hex

21:33 <PaulFertser> pi0: but it's not that hard to solder two wires there to the pads, so yes, just do not try stlinkv3 with it. What debug adapter do you have?

21:34 <NishanthMenon> karlp: k3 is a family of devices. Linux uboot, .... Lots of usage. I am out from my desk ATM. I can clarify if anything specific

21:34 <pi0> i have a segger edu, and i just got 5 stlink v2's from ali

21:34 <pi0> got the text message confirmation that they arrived at my door :D

21:34 <pi0> so i am excited to rush home

21:35 <pi0> between work and school, now ai killed the job market

21:35 <pi0> i should of learned how to play sports instead

21:35 <pi0> lol

21:36 <pi0> PaulFertser: would any of those work?

21:37 <PaulFertser> pi0: segger would work sure

21:37 <pi0> how about the stlink v2?

21:37 <PaulFertser> Should work too

21:37 <pi0> those should also right, with the stlink software

21:37 <pi0> nice

21:38 <pi0> i do have a ubuntu box and windows system, so which ever is the easiest

21:39 <PaulFertser> Guess ubuntu is easier

21:45 <pi0> nice, i should be home within 4 hours

21:45 <pi0> traffic is crazy over here

21:46 <pi0> oshpark only charges 3.00 for 6 of these flex pcb's

21:46 <pi0> free shipping too

21:46 <pi0> last order took a little over a month tho

21:46 <pi0> but its worth seeing if this pcb works

21:53 <pi0> just to understand the work flow, i will need openocd and https://github.com/stlink-org/stlink

21:54 <pi0> https://github.com/seemoo-lab/openhaystack/wiki/Flashing-nRF-with-OpenOCD---ST-Link

21:54 <pi0> i saw this, but is .bin the same as .hex?

21:58 <pi0> karlp: would i have to change anything from these instructions

21:59 <pi0> PaulFertser: i think i should be able to follow this, correct, or do you see anything that i may have to change

22:08 <pi0> however i did not notice they have a .bin on that example, not in my situation, not sure if that can be interchangable

22:22 <PaulFertser> pi0: bin is not the same as hex, as for bin you need to specify the right offset and for hex it's part of the file.

22:22 <PaulFertser> pi0: and no, you do not need https://github.com/stlink-org/stlink

22:23 <PaulFertser> share/openocd/scripts/interface/stlink.cfg can be shortened to interface/stlink.cfg

22:24 <PaulFertser> In that listing the bin file is flashed from 0 offset so it's not specified so in this particular case using a .hex is fully equivalent.

22:24 <PaulFertser> But they shouldn't run program twice, and especially shouldn't do it the second time without verify.

22:30 <pi0> just to clarify, i could use "program ble_sniffer.dex"

22:30 <pi0> and this will flash my hex file to my board without specifying anything else?

22:40 <pi0> PaulFertser: i believe another follow up question i have as well, based off your response i do not need an offset for hex?

22:41 <pi0> or perhaps i might of misunderstood

22:43 <PaulFertser> pi0: yes

22:43 <PaulFertser> No need for offset. But I'd recommend to add " verify"

22:45 <pi0> ah i see so the entire command would be "program ble_sniffer.hex verify" not only will this flash but also verify as well

22:50 <pi0> PaulFertser: i did notice other tutorials rain init, and reset init, not sure if these pre commands are necessary

22:53 <PaulFertser> pi0: not needed, it's all automatic inside "program".

22:53 <pi0> ah nice, understood

23:29 <pi0> ugh its rainin, gonna be a nightmare to get home :/ see you guys in a bit