<pi0>
which is meant for an nrf52480 dongle, not an nrf52480 super mini
<PaulFertser>
It doesn't matter and doesn't set UICR anyway.
<pi0>
not sure if that would make a big difference, i just figured since it was the same chip 52480, but different board of course, it would not matter
<PaulFertser>
So what was the change?
<pi0>
let me connect and paste the new error message
<pi0>
when i plug it in the board does not even light up anymore
<pi0>
Error: init mode failed (unable to connect to the target)
<PaulFertser>
Probably it shouldn't if the LED is controlled by the board and not hardwired to power.
<PaulFertser>
Have you tried pulling reset pin down to see if it changes the behaviour?
<PaulFertser>
I think it's really important to understand what you changed between https://pastebin.com/NFiek3Ny (which was exactly the same error!) and when it connected.
<pi0>
i get a blinking led with connected via usb c
<pi0>
but no led when connected via stlink v2
<PaulFertser>
How do you power the target board when connecting with stlink?
<pi0>
vcc, gnd, and the swd, clk
<PaulFertser>
stlink isn't supposed to provide any power
<pi0>
so remove the power keep the ground
<pi0>
and plug it via usb again
<PaulFertser>
The board needs to be powered, yes.
<PaulFertser>
Also, you got a blinking LED and then what happened?
<pi0>
powered the board via led
<pi0>
perhaps i did brick it since i did it powered via stlink v2
<pi0>
and not external power
<pi0>
right now i have it powered via eternal pack
<pi0>
and stlink has swd clk and gnd connected
<pi0>
still no target
<PaulFertser>
It can not be bricked I think.
<PaulFertser>
So what exactly happened after the LED was blinking? Did you reflash it?
<pi0>
correct
<pi0>
i plugged in some wires to reset it
<pi0>
but that did nothing
<pi0>
there isnt an actual reset button on this
<pi0>
i am runnig out of ideas
<pi0>
i will see you in a few i gotta wake up in a few hours
<pi0>
feel free to leave some troubleshooting tips
<PaulFertser>
pi0: probably that new hex files is using those pins you shorted with SWD for something?
<PaulFertser>
pi0: I already told you the idea of that board is fishy.
<PaulFertser>
If firmware is trying to use those pins then it would mess up SWD.
Haohmaru has joined #openocd
Hawk777 has quit [Quit: Leaving.]
^Dan has joined #openocd
^Dan has quit [Remote host closed the connection]
<Haohmaru>
you know what's dumb... i just installed f*cking MPLABX IDE/IPE (particularly the IPE that is basically the program that talks to the programmer so you can flash these sh*ts), i had to install an older version because pickit3 is not supported in the newest version
<Haohmaru>
so now if we buy one of those newer programmers, what was it, pickit mplab Basic or whatever, it 99.9% won't work with that version
<Haohmaru>
it'll need a new version
<Haohmaru>
shouldn't microsh*t offer a "return your old garbagekit3 and get the newest one with a discount"
Deneb has joined #openocd
en-sc has joined #openocd
<pi0>
PaulFertser: i think i might just try arduino framework on this board, i mean for the price to get zigbee and matter, and bluetooth
<pi0>
i think i might have thin enough mag wire to make it happen, i am running out of pcb boards
<pi0>
but i did want to clarify on one thing, you said the stlink is not suppose to power the board at all, so plugging in the board via usb and keeping the gnd swd clk still connected to the board and stlink would be ok
<pi0>
i think it might be geting 5v via usb c
Haohmaru has quit [Quit: saionara]
Hawk777 has joined #openocd
<pi0>
i should just avoid the headache with this board and get an esp32-c6 super mini and just deal with the zigbee and matter on those via usb instead of soldering the pads on each board
en-sc has quit [Remote host closed the connection]
<pi0>
but i will look into amazon for one of these SEQURE S60P
<pi0>
i think i burned through 2 of my 10 of these boards with soldering and such, its a good learning exp.... on cheap boards
<pi0>
PaulFertser: arg!!! i needed reset pin from the mcu to the stlink v2 as well?
<pi0>
here seems to be so many different methods, what are you thoughts on this? programmer connecting to an NRF52840 board via SWDIO+SWCLK+SRST (naturally also VCC and GND).
nerozero has quit [Ping timeout: 276 seconds]
<pi0>
PaulFertser: also just to clarify there really isnt a way to upload to this board via arduino framework without installing the .hex via stlink, correct?
<pi0>
the only thing that works on this board right now out the box is circuit python via uf2 i believe
renrelkha has quit [Remote host closed the connection]
renrelkha has joined #openocd
<PaulFertser>
pi0: I have no idea what you imply by mentioning arduino framework. SWD should just work. Have you checked what exactly are you shorting with that strange additional board?
<PaulFertser>
I do not understand how one nrf52 board should be any different from another, different pinout you account for in the source code and that's it.
<pi0>
PaulFertser: i see what you mean, this is just my first time getting exposed to openocd and trying to get this stlink to work, i mean it is exciting and fuasrating at the same time lol
<PaulFertser>
pi0: it's nothing OpenOCD specific, I'm asking if that board of yours connects SWD directly to some GPIOs that firmware you flashed configures so it's driven by both and fails to work with SWD no matter what adapter and host software are used.
<pi0>
PaulFertser: oooh! i understand what you mean now, in this case i am not sure if the updated firmware does this
<PaulFertser>
I do not understand why it's considered a good idea in the first place to short SWD to anything.
<pi0>
however when i return home I will take more pictures of my devices and post them online, i think i ruined some pads already
<pi0>
hmm let me provide a updated pic and see i understand what you mean
<pi0>
one second
<pi0>
PaulFertser: what is the name of that image provide you prefer
<pi0>
so i can upload it to
<PaulFertser>
What temperature are you soldering at if it can ruin a pad?..
<pi0>
i will be soldering some pins but wanted to confirm if these are the required pins to perform this task
<pi0>
PaulFertser: so my question would be, i solder those pins, connect it to my stlink v2, and power the nrf52480 supermini via usb
<pi0>
and in theory that should be good?
<PaulFertser>
pi0: I do not think you should solder more of those odd flex boards before figuring out what they short.
<PaulFertser>
pi0: yes, and I think you do not need RST normally there.
<PaulFertser>
pi0: And I'd try desoldering the board from one of the "ruined" boards.
<pi0>
i will try it again tonight, so only solder the gnd, swd and clk
<pi0>
that should be enough i suppose
<PaulFertser>
Yes, and power via Type-C
<PaulFertser>
btw, you connect one of the pins to ground with that board so if that pin is configured to output logical one that's immediate MCU crash.
<pi0>
the interesting thing tho, is that this project https://github.com/pdcook/nRFMicro-Arduino-Core, provides a uf2 type file that i can toss onto my board when it loads it in storage mode
<pi0>
but it doesnot work
<PaulFertser>
But you can convert uf2 to ihex, right? And OpenOCD knows ihex.
<pi0>
just to verify on your last statement, i will be soldering a gnd (ground) wire and connecting it to the stlink v2
<pi0>
this is what you meant, correct?
<PaulFertser>
pi0: my last statement was about that strange flex board.
<PaulFertser>
If it really connects GND to one of GPIOs and firmware uses that GPIOs to output 1 then the target will crash. Same if it's connecting a GPIO to VDD and the GPIO tries to output zero.
<pi0>
oh i see, i will remove it
<pi0>
and solder directly to the actual pcb
<PaulFertser>
How do you convert from uf2 btw?
<PaulFertser>
Or how do you flash uf2 directly?
<pi0>
for example on this board, i would simply just reset the board shorting the rst and gnd