HFS-P3 Pen type pocket geiger counter / dosimeter Pt.2

I was asked by Gissio to try and download the original firmware from my HFS-P3, so I tried. Alas, no joy so far. ☹️ Under the battery (stuck down with sticky tape) is a pin header. Probably designed to have a pogo pin connector connect to it as there is no room to solder on an actual pin header. I just soldered wires to it directly. I managed to work out the pins by tracing the circuit, but I had to use my microscope as the connections on the MCU really are that small! I took photos of both sides and flipped one then overlaied one over the other so I could line up the vias on the board. You can see in the pictures. Below is what I believe to be the correct pinout going from the datasheet of the MCU.

The instructions Gissio gave me was to do pretty much exactly the same as for the FS2011. I may need to connect +3.3v, but do this for as short time as possible. For some reason it just won't read the MCU. Maybe I got the pins wrong? The messages from ST Link are below. I have tried with just GND, SWIO and SWCLK, with and without +3.3v connected. I have tried in it's off state with +3.3v applied and also tried in various iterations with the NRST held low, and connected to RST on the ST LINK dongle. All with no joy.

The main message that kept coming back from the ST Link software was 'connect under reset'

D:\stlink\bin>st-flash read backup.bin 0x08000000 0x10000
st-flash 1.7.0
libusb: info [winusb_get_device_list] The following device has no driver: 'USB\VID_2E8A&PID_000A&MI_02\7&2C249F46&0&0002'
libusb: info [winusb_get_device_list] libusb will not be able to access it
[!] send_recv read reply failed: LIBUSB_ERROR_PIPE
[!] send_recv STLINK_DEBUG_READCOREID
2023-07-12T08:36:33 ERROR common.c: Failed to read core_id
[!] send_recv read reply failed: LIBUSB_ERROR_PIPE
[!] send_recv STLINK_JTAG_READDEBUG_32BIT
2023-07-12T08:36:33 ERROR common.c: Can not connect to target. Please use 'connect under reset' and try again
Failed to connect to target

The error about "The following device has no driver: 'USB\VID_2E8A&PID_000A&MI_02\7&2C249F46&0&0002'" can safely be ignored as I apparently have a device on my PC that has no driver. Not sure what this is (something with my PC) but nothing to do with ST Link.

I also got a picture of the battery of the HFS-P3 whilst it was apart. A tiny 150mAh lipo cell.

Update: I finally got around to looking at this again, but sadly, still no joy. I'm not sure if it something with my setup or just can't be done. It did work with the FS2100 though. The output below makes little sense to me. I even went back to the datasheet to verify the connections were correct, and does seem so.

D:\stlink\bin>st-info.exe --probe --connect-under-reset
[!] send_recv read reply failed: LIBUSB_ERROR_PIPE
[!] send_recv STLINK_JTAG_WRITEDEBUG_32BIT
[!] send_recv read reply failed: LIBUSB_ERROR_PIPE
[!] send_recv STLINK_JTAG_READDEBUG_32BIT
[!] send_recv read reply failed: LIBUSB_ERROR_PIPE
[!] send_recv STLINK_JTAG_READDEBUG_32BIT
[!] send_recv read reply failed: LIBUSB_ERROR_PIPE
[!] send_recv STLINK_JTAG_WRITEDEBUG_32BIT
[!] send_recv read reply failed: LIBUSB_ERROR_PIPE
[!] send_recv STLINK_JTAG_WRITEDEBUG_32BIT
[!] send_recv read reply failed: LIBUSB_ERROR_PIPE
[!] send_recv STLINK_JTAG_WRITEDEBUG_32BIT
[!] send_recv read reply failed: LIBUSB_ERROR_PIPE
[!] send_recv STLINK_JTAG_READDEBUG_32BIT
[!] send_recv read reply failed: LIBUSB_ERROR_PIPE
[!] send_recv STLINK_JTAG_WRITEDEBUG_32BIT
[!] send_recv read reply failed: LIBUSB_ERROR_PIPE
[!] send_recv STLINK_DEBUG_READCOREID
[!] send_recv read reply failed: LIBUSB_ERROR_PIPE
[!] send_recv STLINK_JTAG_READDEBUG_32BIT
Found 1 stlink programmers
  version:    V2J29S7
  serial:     360036002933353739303541
  flash:      0 (pagesize: 0)
  sram:       0
  chipid:     0x0000
  descr:      unknown device

D:\stlink\bin>st-flash.exe --connect-under-reset read backup.bin 0x00000000 0x40000
st-flash 1.7.0
libusb: info [winusb_get_device_list] The following device has no driver: 'USB\VID_2E8A&PID_000A&MI_02\7&2C249F46&0&0002'
libusb: info [winusb_get_device_list] libusb will not be able to access it
[!] send_recv read reply failed: LIBUSB_ERROR_PIPE
[!] send_recv STLINK_JTAG_WRITEDEBUG_32BIT
[!] send_recv read reply failed: LIBUSB_ERROR_PIPE
[!] send_recv STLINK_JTAG_READDEBUG_32BIT
[!] send_recv read reply failed: LIBUSB_ERROR_PIPE
[!] send_recv STLINK_JTAG_READDEBUG_32BIT
2023-10-16T18:11:16 WARN common.c: NRST is not connected
[!] send_recv read reply failed: LIBUSB_ERROR_PIPE
[!] send_recv STLINK_JTAG_WRITEDEBUG_32BIT
[!] send_recv read reply failed: LIBUSB_ERROR_PIPE
[!] send_recv STLINK_JTAG_WRITEDEBUG_32BIT
[!] send_recv read reply failed: LIBUSB_ERROR_PIPE
[!] send_recv STLINK_JTAG_WRITEDEBUG_32BIT
[!] send_recv read reply failed: LIBUSB_ERROR_PIPE
[!] send_recv STLINK_JTAG_READDEBUG_32BIT
[!] send_recv read reply failed: LIBUSB_ERROR_PIPE
[!] send_recv STLINK_JTAG_WRITEDEBUG_32BIT
2023-10-16T18:11:16 ERROR common.c: Soft reset failed: error write to AIRCR
[!] send_recv read reply failed: LIBUSB_ERROR_PIPE
[!] send_recv STLINK_DEBUG_READCOREID
2023-10-16T18:11:16 ERROR common.c: Failed to read core_id
[!] send_recv read reply failed: LIBUSB_ERROR_PIPE
[!] send_recv STLINK_JTAG_READDEBUG_32BIT
2023-10-16T18:11:16 ERROR common.c: Can not connect to target. Please use 'connect under reset' and try again
Failed to connect to target

Archived from radmon.org - originally posted 12/06/2023