Has my Thingy91 died?

RE: Has my Thingy91 died?

Michal — Thu, 29 Feb 2024 17:51:54 GMT

Hello Brian,

West is installed with the zephyr toolchain. If you open nRF Connect terminal (not just standard terminal/powershell) from VS Code it should have PATH set up correctly so that you can use west from there.

Best regards,

Michal

RE: Has my Thingy91 died?

Brian Fuller — Wed, 28 Feb 2024 00:13:21 GMT

Michal,

I spoke too soon. I can flash firmware to my new Thingy:91 (the one that arrived in the mail yesterday) but I still cannot flash to the old Thingy:91 that had been working until I set the switch on the Thingy:91 to nrf52 than back to nrf91. The flash command has failed since then.

I still get the following error when I flash to the old Thingy:91

west flash -d /nordicsemi/myapps/fund_less4_exer1/build --skip-rebuild --dev-id 52001021

-- west flash: using runner nrfjprog
-- runners.nrfjprog: Flashing file: /nordicsemi/myapps/fund_less4_exer1/build/zephyr/merged.hex
[ ###### ] 0.000s | Erase file - Check image [ #### ] 0.000s | Check image validity - Initialize device info [ ######## ] 0.000s | Check image validity - Check region 0 settings [ ############ ] 0.000s | Check image validity - block 1 of 3 [ ################ ] 0.007s | Check image validity - block 2 of 3 [ #################### ] 0.032s | Check image validity - Finished [ ############# ] 0.000s | Erase file - Erasing [ ###### ] 0.000s | Erasing non-volatile memory - block 1 of 2 [ ############# ] 0.569s | Erasing non-volatile memory - block 2 of 2 [ #################### ] 0.000s | Erasing non-volatile memory - Erase successful [ #################### ] 4.221s | Erase file - Done erasing
[ ###### ] 0.000s | Program file - Checking image [ #### ] 0.000s | Check image validity - Initialize device info [ ######## ] 0.000s | Check image validity - Check region 0 settings [ ############ ] 2.878s | Check image validity - block 1 of 3 [ ################ ] 1.080s | Check image validity - block 2 of 3 [ #################### ] 0.008s | Check image validity - Finished [ ############# ] 0.000s | Program file - Programming [ ###### ] 0.000s | Programming image - block 1 of 2 [error] [ Client] -

Encountered error -102: Command program_file executed for 74 milliseconds with result -102
[error] [ nRF91] - The write access failed, but no cause could be determined.
[error] [ nRF91] - It may be due to an unaligned access, accessing a nonexistent memory, or a communication issue.
[error] [ nRF91] - Failed while performing 'Write' operation on target address 0x00000000.
-102: An unknown error.
[error] [ nRF91] - Failed while reading device information.
[error] [ Worker] - An unknown error.
ERROR: JLinkARM DLL reported an error. Try again. If error condition
ERROR: persists, run the same command again with argument --log, contact Nordic
ERROR: Semiconductor and provide the generated log.log file to them.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.
FATAL ERROR: command exited with status 33: nrfjprog --program /nordicsemi/myapps/fund_less4_exer1/build/zephyr/merged.hex --sectorerase --verify -f NRF91 --snr 52001021

* The terminal process terminated with exit code: 33.
* Terminal will be reused by tasks, press any key to close it.

So the JLink is working since I can flash to the new Thingy:91.

I am unable to run the west flash.... command in the Visual Studio Code Terminal so I cannot run the --log command. See below

west flash -d /nordicsemi/myapps/fund_less4_exer1/build --skip-rebuild --dev-id 52001021
Command 'west' not found, did you mean:
command 'jest' from deb jest (27.5.1~ds+~cs69.51.22-2)
command 'test' from deb coreutils (8.32-4.1ubuntu1)
Try: sudo apt install <deb name>
brianf@devbook:/nordicsemi/myapps/cppTest$

The following executable files are in my directory /opt/nrf-command-line-tools/bin

Where would the west command live? Isn't west installed when I Installed the nrf-command-line-tools?

Thanks,

Brian

RE: Has my Thingy91 died?

Michal — Tue, 27 Feb 2024 21:03:34 GMT

Hello Brian,

I am glad to hear that.

Best regards,

Michal

RE: Has my Thingy91 died?

Brian Fuller — Tue, 27 Feb 2024 00:55:55 GMT

Hello Michal,

I have resolved the problem with my system. I reloaded nRF command line tools package, explicitly set

/opt/nrf-command-line-tools/bin in PATH, sourced the .bashrc file, and restarted Visual Studio Code. I can now flash my projects in nRF91. Thank you for your help.

Best regards,

Brian Fuller

RE: Has my Thingy91 died?

Brian Fuller — Sat, 24 Feb 2024 16:19:03 GMT

Saturday, Feb 24, 2024 - 08:49 Mountain Standard Time (North America)

Hello Michal,

A new Thingy:91 arrived at my office. I plugged it in to the JLink Base. As expected it blinks Green on startup right out of the box.

I then flashed blinky to the new Thingy:91 and got the following error message in the Visual Studio Code Terminal window.

Flashing build to 52001021
west flash -d /nordicsemi/myapps/blinky_01/build --skip-rebuild --dev-id 52001021

-- west flash: using runner nrfjprog
-- runners.nrfjprog: Flashing file: /nordicsemi/myapps/blinky_01/build/zephyr/zephyr.hex
[ ###### ] 0.000s | Erase file - Check image [ ##### ] 0.000s | Check image validity - Initialize device info [ ########## ] 0.000s | Check image validity - Check region 0 settings [ ############### ] 0.000s | Check image validity - block 1 of 2 [ #################### ] 0.043s | Check image validity - Finished [ ############# ] 0.000s | Erase file - Erasing [ ########## ] 0.000s | Erasing non-volatile memory - block 1 of 1 [error] [ Client] - Encountered error -102: Command erase_file executed for 86 milliseconds with result -102
[error] [ nRF91] - Failed while performing Erase operation on target address 35068.
-102: JLinkARM.dll WriteU32 returned error -1.
[error] [ nRF91] - Failed while erasing device. -102: JLinkARM.dll WriteU32 returned error -1.
[error] [ Worker] - JLinkARM.dll WriteU32 returned error -1.
ERROR: JLinkARM DLL reported an error. Try again. If error condition
ERROR: persists, run the same command again with argument --log, contact Nordic
ERROR: Semiconductor and provide the generated log.log file to them.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.
FATAL ERROR: command exited with status 33: nrfjprog --program /nordicsemi/myapps/blinky_01/build/zephyr/zephyr.hex --sectorerase --verify -f NRF91 --snr 52001021

* The terminal process terminated with exit code: 33.
* Terminal will be reused by tasks, press any key to close it.

As a reminder, the "west" command fails when I run it in the Visual Studio Code TERMINAL window.

I get the following response when I directly repeat the west command that was executed to give the error above.

west flash -d /nordicsemi/myapps/blinky_01/build --skip-rebuild --dev-id 52001021
Command 'west' not found, did you mean:
command 'test' from deb coreutils (8.32-4.1ubuntu1)
command 'jest' from deb jest (27.5.1~ds+~cs69.51.22-2)
Try: sudo apt install <deb name>

The final recommendation of Try: sudo apt install <deb name> indicates I need to install something but clearly west is already in the system since the build/flash system was working perfectly before I briefly set the switch to nrf52 to play with the Bluetooth LE and then switched back to nrf91.

Finally: The new Thingy:91 continues to blink a green light indicating that the firmware that the Thingy was loaded with at the factory is still active and that the flash command did not get to the point of erasing the firmware, which is indicated in the flash error that appears above.

Thank you for your help.

Brian

RE: Has my Thingy91 died?

Brian Fuller — Fri, 23 Feb 2024 20:35:12 GMT

Hi Michal,

I do not currently have another device to test with the JLink device though there is a new Thingy:91 arriving in the mail later today. I'll test it when it arrives and report.

Regarding the --log command:

I am not able to successfully execute the "west flash" command. I execute the command in the nRF TERMINAL window where I would expect

the environmental variables to be set but I get the following results:

brianf@devbook:/nordicsemi/myapps/cppTest$ west flash -d /nordicsemi/myapps/blinky_01/build --log --skip-rebuild --dev-id 52001021

Command 'west' not found, did you mean:
command 'test' from deb coreutils (8.32-4.1ubuntu1)
command 'jest' from deb jest (27.5.1~ds+~cs69.51.22-2)
Try: sudo apt install <deb name>
brianf@devbook:/nordicsemi/myapps/cppTest$

I'll look through DevAcademy for how to compile and link from the command line unless you have a better suggestion.

Have a good weekend Michal og tusen takk.

Brian

RE: Has my Thingy91 died?

Michal — Fri, 23 Feb 2024 13:08:05 GMT

Does this JLink work with other devices?

Are both of the chips not connecting, or is nRF52 or nRF91 still able to connect via JLink?

Could you try running the command with --log as shown in the output and upload the file here?

Best regards,

Michal

RE: Has my Thingy91 died?

Brian Fuller — Wed, 21 Feb 2024 15:31:12 GMT

Good morning Michal, Thank you for the response. The response to nrfjprog --recover is below.

brianf@devbook:/nordicsemi/nrf_gitHub_repos/ncs-fund/v2.x.x/lesson4/fund_less4_exer1$ nrfjprog --recover
[error] [ Client] - Encountered error -102: Command connect_to_emu_with_snr executed for 1420 milliseconds with result -102
ERROR: Unable to connect to a debugger.
[error] [ Worker] - An unknown error.
ERROR: JLinkARM DLL reported an error. Try again. If error condition
ERROR: persists, run the same command again with argument --log, contact Nordic
ERROR: Semiconductor and provide the generated log.log file to them.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.
brianf@devbook:/nordicsemi/nrf_gitHub_repos/ncs-fund/v2.x.x/lesson4/fund_less4_exer1$

RE: Has my Thingy91 died?

Michal — Wed, 21 Feb 2024 13:54:32 GMT

Hello Brian,

What happens when you run nrfjprog: --recover

Best regards,

Michal