I'm testing out my new PCA10040 dev board. I can see the board in Windows Explorer when it's connected and I can see the two preloaded files as in the attached screen shot. However I get an error when I try to drag and drop one of the example hex files (ble_app_hrs_pca10040_s132.hex) as show in the second screen shot.
I think the board has the HRS app, but the nRF Toolbox does not show the Nordic_HRS device, even though the board and the phone are about 2 feet apart.
Just for grins, I tried to delete the zero-length hex file using the Windows delete command in the JLINK window. It caused Windows to crash, which leads me to believe I have a corrupted JLINK file system. Is there a way to do a factory reset of the dev board so I get a fresh file system?
My hope is that I can use the old-school programming tool to re-flash the JLINK firmware. Using the Windows file system is cool, but maybe not quite ready for prime time.
Hi,
What is the DK version on the white sticker? Please be aware that Segger hasn't support v.3.0.0 for the drag-and-drop feature.
Bret Foreman said:Is there a way to do a factory reset of the dev board so I get a fresh file system?
You use the image from Blinky Example which is the same as the factory image.
Bret Foreman said:My hope is that I can use the old-school programming tool to re-flash the JLINK firmware.
Why would you need to re-flash the JLink firmware? What is the status of LED5?
Bret Foreman said:If I do an "erase all" in the programmer tool then I'm able to drag and drop the hex file as shown. However it does not begin advertising.
It should use the programmer to write the images after "erase all".
Are you able to write images with the nRF Connect/Programmer?
Regards,
Amanda H.
The version of the DK is 3.0.0. So I guess I need to use the programmer. I did an "erase all" and loaded the HRS example (using the programmer) and it didn't advertise. The only LED that ever lights is the power-on.
The version of the DK is 3.0.0. So I guess I need to use the programmer. I did an "erase all" and loaded the HRS example (using the programmer) and it didn't advertise. The only LED that ever lights is the power-on.
If Segger doesn't support version 3.0.0 of the DK, I wonder if the s132 soft device supports it. Have you tried it? That's the SD that the HRS example uses.
Hi,
Bret Foreman said:Have you tried it? That's the SD that the HRS example uses.
The S132 can support DK v3.0.0.
Do you get any errors while using the nRF Programmer to flash? Could you provide the log from the nRF Programmer?
-Amanda H.
Here's the programmer log in verbose mode when I did an "erase all" and loaded the HRS app. After loading the app, none of the LEDs are lit except power and the board is not advertising.
09:45:26.998 Using nrf-device-lib-js version: 0.4.13 09:45:26.998 Using nrf-device-lib version: 0.12.8 09:45:26.998 Using nrfjprog DLL version: 10.16.0 09:45:26.998 Using JLink version: JLink_V7.80c 09:45:27.028 [nrfdl][warning](09:45:27.027) [JlinkARM] JlinkARM version non expected one found: JLink_V7.80c, expected: JLink_V7.66a 09:45:27.028 Installed JLink version does not match the provided version (V7.66a) 09:45:27.166 [nrfdl][error](09:45:27.157) [jlink] [NRFJPROG][DebugProbe][] Failed reading device info. 09:45:27.166 [nrfdl][warning](09:45:27.157) [jlink] [NRFJPROG][DebugProbe][] Warning: Could not read device info because the device is locked. 09:45:27.167 [nrfdl][warning](09:45:27.157) [jlink] [NRFJPROG][DebugProbe][] Warning: No actions other than recover will be available. 09:45:27.167 [nrfdl][warning](09:45:27.157) [jlink] [NRFJPROG][DebugProbe][] Warning: Try recovering the device if you want to unlock it. 09:45:27.167 [nrfdl][warning](09:45:27.157) [jlink] [NRFJPROG][DebugProbe][] Device info is blank. Attempting to reread. 09:45:27.170 [nrfdl][error](09:45:27.163) [jlink] [NRFJPROG][nRF52][] Access protection is enabled, can't read device version. 09:45:27.175 [nrfdl][error](09:45:27.166) [jlink] [NRFJPROG][DebugProbe][] Failed reading device info. 09:45:27.175 [nrfdl][warning](09:45:27.166) [jlink] [NRFJPROG][DebugProbe][] Warning: Could not read device info because the device is locked. 09:45:27.177 [nrfdl][warning](09:45:27.166) [jlink] [NRFJPROG][DebugProbe][] Warning: No actions other than recover will be available. 09:45:27.177 [nrfdl][warning](09:45:27.166) [jlink] [NRFJPROG][DebugProbe][] Warning: Try recovering the device if you want to unlock it. 09:45:27.177 [nrfdl][error](09:45:27.166) [jlink] [NRFJPROG][HighLevel][] Failed to read device info from the device. 09:45:27.182 [nrfdl][error](09:45:27.177) [jlink] [NRFJPROG][nRF52][] Access protection is enabled, can't read device version. 09:45:41.209 Using @nordicsemiconductor/nrf-device-lib-js to communicate with target via JLink 09:45:41.209 JLink OB firmware version J-Link OB-nRF5340-NordicSemi compiled Dec 3 2021 15:46:49 09:45:41.212 Device family NRF52_FAMILY 09:45:41.212 Device version UNKNOWN 09:45:41.213 Board version PCA10040 09:45:41.214 Loading readback protection status for Application core 09:45:41.220 [nrfdl][info](09:45:41.215) Loaded plugin C:\Users\Bret Foreman\AppData\Local\Programs\nrfconnect\resources\app.asar.unpacked\node_modules\@nordicsemiconductor\nrf-device-lib-js\Release\nrfdl-jlink-plugin.nrfdl, starting to resolve symbols 09:45:41.425 [nrfdl][error](09:45:41.425) [jlink] [NRFJPROG][DebugProbe][] Failed reading device info. 09:45:41.425 [nrfdl][warning](09:45:41.425) [jlink] [NRFJPROG][DebugProbe][] Warning: Could not read device info because the device is locked. 09:45:41.425 [nrfdl][warning](09:45:41.425) [jlink] [NRFJPROG][DebugProbe][] Warning: No actions other than recover will be available. 09:45:41.425 [nrfdl][warning](09:45:41.425) [jlink] [NRFJPROG][DebugProbe][] Warning: Try recovering the device if you want to unlock it. 09:45:41.431 [nrfdl][error](09:45:41.428) [jlink] [NRFJPROG][nRF52][] Access protection is enabled, can't read device version. 09:45:41.610 [nrfdl][info](09:45:41.610) close plugin dll at path: C:\Users\Bret Foreman\AppData\Local\Programs\nrfconnect\resources\app.asar.unpacked\node_modules\@nordicsemiconductor\nrf-device-lib-js\Release\nrfdl-jlink-plugin.nrfdl 09:45:41.610 Readback protection status: NRFDL_PROTECTION_STATUS_ALL 09:45:41.614 Parse memory regions for Application core 09:45:41.617 Update files regions according to Application core 09:45:41.617 Parse memory regions for file 09:45:41.620 Device is loaded and ready for further operation 09:45:45.262 Recovering NRFDL_DEVICE_CORE_APPLICATION core 09:45:45.271 [nrfdl][info](09:45:45.262) Loaded plugin C:\Users\Bret Foreman\AppData\Local\Programs\nrfconnect\resources\app.asar.unpacked\node_modules\@nordicsemiconductor\nrf-device-lib-js\Release\nrfdl-jlink-plugin.nrfdl, starting to resolve symbols 09:45:45.461 [nrfdl][error](09:45:45.462) [jlink] [NRFJPROG][DebugProbe][] Failed reading device info. 09:45:45.461 [nrfdl][warning](09:45:45.462) [jlink] [NRFJPROG][DebugProbe][] Warning: Could not read device info because the device is locked. 09:45:45.461 [nrfdl][warning](09:45:45.462) [jlink] [NRFJPROG][DebugProbe][] Warning: No actions other than recover will be available. 09:45:45.461 [nrfdl][warning](09:45:45.462) [jlink] [NRFJPROG][DebugProbe][] Warning: Try recovering the device if you want to unlock it. 09:45:45.468 [nrfdl][error](09:45:45.464) [jlink] [NRFJPROG][nRF52][] Access protection is enabled, can't read device version. 09:45:48.721 Recovering NRFDL_DEVICE_CORE_APPLICATION core completed 09:45:48.723 Device recovery completed 09:45:48.724 Using @nordicsemiconductor/nrf-device-lib-js to communicate with target via JLink 09:45:48.724 JLink OB firmware version J-Link OB-nRF5340-NordicSemi compiled Dec 3 2021 15:46:49 09:45:48.725 Device family NRF52_FAMILY 09:45:48.726 Device version UNKNOWN 09:45:48.727 Board version PCA10040 09:45:48.727 Loading readback protection status for Application core 09:45:48.728 [nrfdl][info](09:45:48.722) close plugin dll at path: C:\Users\Bret Foreman\AppData\Local\Programs\nrfconnect\resources\app.asar.unpacked\node_modules\@nordicsemiconductor\nrf-device-lib-js\Release\nrfdl-jlink-plugin.nrfdl 09:45:48.728 [nrfdl][info](09:45:48.728) Loaded plugin C:\Users\Bret Foreman\AppData\Local\Programs\nrfconnect\resources\app.asar.unpacked\node_modules\@nordicsemiconductor\nrf-device-lib-js\Release\nrfdl-jlink-plugin.nrfdl, starting to resolve symbols 09:45:49.285 Readback protection status: NRFDL_PROTECTION_STATUS_NONE 09:45:49.285 [nrfdl][info](09:45:49.285) close plugin dll at path: C:\Users\Bret Foreman\AppData\Local\Programs\nrfconnect\resources\app.asar.unpacked\node_modules\@nordicsemiconductor\nrf-device-lib-js\Release\nrfdl-jlink-plugin.nrfdl 09:45:49.285 [nrfdl][info](09:45:49.286) Loaded plugin C:\Users\Bret Foreman\AppData\Local\Programs\nrfconnect\resources\app.asar.unpacked\node_modules\@nordicsemiconductor\nrf-device-lib-js\Release\nrfdl-jlink-plugin.nrfdl, starting to resolve symbols 09:45:49.804 [nrfdl][info](09:45:49.804) close plugin dll at path: C:\Users\Bret Foreman\AppData\Local\Programs\nrfconnect\resources\app.asar.unpacked\node_modules\@nordicsemiconductor\nrf-device-lib-js\Release\nrfdl-jlink-plugin.nrfdl 09:45:49.807 Parse memory regions for Application core 09:45:49.808 Update files regions according to Application core 09:45:49.808 Parse memory regions for file 09:45:49.811 Device is loaded and ready for further operation 09:45:56.908 Parsing HEX file: C:\Nordic\SDK_17.1.0\examples\ble_peripheral\ble_app_hrs\hex\ble_app_hrs_pca10040_s132.hex 09:45:56.916 File was last modified at 12/8/2022, 9:19:12 AM 09:45:56.989 Update files regions according to Application core 09:45:56.989 Parse memory regions for file 09:45:56.989 SoftDevice detected, id 0x101 (S132 v7.2.0)
Hi,
Please try to reset the board after writing the image.
I see the same issue as you, but pressing the reset button on DK can help.
-Amanda H.
I always power-cycle the board after I flash it, which I believe resets the board. I also did another reset after power-cycling and the board is still not advertising. Did your board advertise after reset?
