Search Results

I've confirmed that I can work around the issue using Pylink's open(), connect(), read(), close() operations each time I need to use the J-Link API. In hindsight, the lack of a J-Link disconnect() operation should have been a red flag as well as the target_connected() call only returning the true state immediately after connect(). My program can now poll the J-Link interface to determine if a target device is connected or not, and to read the device details and FICR identity. After close() the d…

Running with J-Link v7.98g software and a J-Link Plus USB probe S/N 601006986 and nrfjprog 10.24.0 Test 1; 1) Connect J-Link Plus to target device (with a Laird BL652) 2) Start J-Flash, open nRF52832_xxAA device, SWD speed 4000 3) Erase chip, program & verify application (device uses ~3.2mA at 3v) 4) Close J-Flash (device is not reset and now uses ~5.4mA at 3v) 5) Run J-Link and execute reset script (device resets and drops to ~32uA at 3v). 6) Disconnect J-Link Plus from target device (device us…

After further investigation, I've confirmed that "nrfjprog --reset" is doing the same reset as J-Flash. I'm looking for the device to go into low power mode after programming (~2uA at 3v). It does after J-Flash (F9) but not after my programmatic reset. The difference seems to be that my application has the J-Link DLL open (pylink.readthedocs.io/en/lates…l#pylink.jlink.JLink.open) while performing the reset. The reset occurs, but the J-Link DLL then forces the device back to a higher power state …

I've written a custom manufacturing programming tool for ARM Cortex-M4 nRF52832 and nRF52810 devices. It uses a J-Link Plus USB programmer (J-Link V7.98g) and is implemented in Python using the Pylink package. The program configures J-Link to use SWD and connects to the target with chip_name 'nRF52832_xxAA' or 'nRF52810_xxAA', allowing the FICR device id and UICR information to be read. I have a problem resetting the processor programmatically from Python. The Pylink reset() function does someth…