We have a custom board with a P1 (SWD and serial connections only, no USB) that is giving us trouble. Before flashing it, when we first powered it up, it went into listening mode as expected (I’m assuming it came with Tinker on it.) We saw it appear in the network list on our computer, went to connect and the connection timed out. We don’t have USB, so we couldn’t get the device ID that way. A second board behaved in exactly the same manner.
Then we built an image from source based on our app (in main,
% make clean all v=1 APP=ourApp PLATFORM_ID=8 USE_SWD=y MODULAR=n) and loaded that over SWD. We are using this ST-Link V2 interface + st-util. Then we get the SOS hard fault blink pattern so we try loading a another image, this time with APP=tinker, and we get the same SOS pattern.
In hindsight, flashing the FW would not have solved the original problem of getting the device ID. We were clearly flailing at this point. But this result of SOS hard fault after flashing is also unexpected. I checked the flashing logs and we never wrote anything above 0x8020000 so we did not overwrite any of the DCT/EEPROM regions so I would expect things like the server keys to be intact.
I’ve combed the forum for answers but almost everyone has USB. Any suggestions on next steps without using dfu-util?