rbaron / b-parasite

🌱💧 An open source DIY soil moisture sensor
1.84k stars 143 forks source link

Can not connect to the board. Target voltage too low? #197

Closed Exeu closed 1 month ago

Exeu commented 1 month ago

Hi,

is there any more detailed guide in how to get the firmware on the borad properly? I never used J-Link before and Just got an original JLInk Edu. For me it is fully unclear how i need to set this now up.

If i call JLinkExe and do the following:

`SEGGER J-Link Commander V7.96g (Compiled May 8 2024 15:00:40) DLL version V7.96g, compiled May 8 2024 15:00:19

Connecting to J-Link via USB...O.K. Firmware: J-Link ARM V8 compiled Nov 28 2014 13:44:46 Hardware version: V8.00 J-Link uptime (since boot): N/A (Not supported by this model) S/N: 268006668 License(s): FlashBP, GDB OEM: SEGGER-EDU VTref=0.530V

Type "connect" to establish a target connection, '?' for help J-Link>connect Please specify device / core. : NRF52 Type '?' for selection dialog Device>NRF52833_XXAA Please specify target interface: J) JTAG (Default) S) SWD T) cJTAG TIF>S Specify target interface speed [kHz]. : 4000 kHz Speed> Device "NRF52833_XXAA" selected.

Connecting to target via SWD Target voltage too low. Please check https://wiki.segger.com/J-Link_cannot_connect_to_the_CPU#Target_connection. Error occurred: Could not connect to the target device. For troubleshooting steps visit: https://wiki.segger.com/J-Link_Troubleshooting`

I enabled power with "Power ON" -> Removed the battery from my parasite board and connected the jlink to the proper pins.

I am a bit clueless what i need to do now

Exeu commented 1 month ago

Ok i at least solved the problem with too low volage. I now connected VCC Pin to VTRef on Jlink... then it was at least working to connect.

But i now get a different issue:

[error] [ JLink] - Failed to initialize CPU module in firmware because probe is low on memory (heap). [error] [ Client] - Encountered error -11: Command read_device_info executed for 720 milliseconds with result -11 [error] [ Worker] - Could not connect to CPU core. This may indicate that AP protection is enabled. Emulator does not have enough memory to perform the requested operation. [error] [ Client] - Encountered error -104: Command read_memory_descriptors executed for 17 milliseconds with result -104 Failed to read device memories. [error] [ nRF52] - Device memory generation failed. [error] [ Worker] - JLinkARM.dll ReadMemU32 detected a read error 1. This typically indicates the read was blocked by a memory protection mechanism. ERROR: nrfjprog failed for an unknown reason. Run the same command again with ERROR: argument --log, contact Nordic Semiconductor and provide the generated ERROR: log.log file to them.