Thingy 91 debug using J link Edu

RE: Thingy 91 debug using J link Edu

Carl Richard — Wed, 09 Dec 2020 10:38:11 GMT

Hi again, Rahul!

It seems like the bootloader may have been deleted. Could you try to follow the steps below closely:

Download and unzip the newest Thingy:91 firmware.
Connect your Thingy:91 to your JLINK Edu and turn it on. Make sure SW2 is at the nRF91-position.
Open the nRF Connect programmer app and select the debugger.
Update modem firmware: press the "update modem" button and navigate to the folder you extracted in step 1. Select the file "mfwnrf9160122.zip". Press "Write" in the following dialog and let the program finish.
Update application firmware: press the "add hexfile" button in the Programmer app and the press "browse". Navigate to the folder you extracted in step 1. and then enter the folder img_app_bl. This folder contains application hex files that also includes the bootloader. For the asset tracker choose one of the following hex files:
1. For LTE-M select: thingy91_ltem_2020-10-30_5522ca2b.hex
2. For NB-IoT select: thingy91_nbiot_2020-10-30_5522ca2b.hex
Observer that the "Memory Layout" now shows the occupied memory of the selected hex-file.
Press "Erase & write" and let the programming finish.

You should now have the asset_tracker including MCUBoot flashed to your Thingy:91. When programming applications in the future with the JLINK Edu make sure that they have MCUBoot enabled by having "CONFIG_BOOTLOADER_MCUBOOT=y" in prj.conf, or else the bootloader will be overwritten.

When it comes to your issues with opening a project in Segger Embedded Studio do the following:

1. Make sure that there are no "space" characters in the path of the SDK. I see that you have "DARK HORSE" as a part of your path, which will result in errors because of the space character.

2. Program the application for the correct board name: thingy91_nrf9160ns

Hope this works!

Best regards,
Carl Richard

RE: Thingy 91 debug using J link Edu

Rkidechaa — Tue, 08 Dec 2020 23:06:45 GMT

[quote userid="68044" url="~/f/nordic-q-a/67496/thingy-91-debug-using-j-link-edu/277317#277317"]What are you seeing in the nRF Connect programmer app when connected through the JLink Edu? Please provide a screenshot.[/quote]

check below Image

RE: Thingy 91 debug using J link Edu

Rkidechaa — Tue, 08 Dec 2020 03:03:52 GMT

Hi Carl,

What kind of errors did you experience when trying to flash hello_world with the JLink EDU?
Yes I tried to flash hello_world with JLink EDU

Did you try to do it using the nRF Connect Programmer app?
I was following this link to debug thingy 91 using segger.
developer.nordicsemi.com/.../ug_thingy91.html

When I am debugging using Segger software was getting hang and not allowing me to do anything. after step 3 ( doing setting nrf connect setting )

Do I need to make changes in the directory?

Regards,

Rahul Kidecha

RE: Thingy 91 debug using J link Edu

Carl Richard — Wed, 28 Oct 2020 09:46:22 GMT

I see.

What kind of errors did you experience when trying to flash hello_world with the JLink EDU? Did you try to do it using the nRF Connect Programmer app? The IC is probably not damaged, but as mentioned the bootloader may have been erased (which is why MCUBoot won't work).

If the bootloader is erased the only way to restore the device is using a debugger, like the JLink Edu. The debugger can also be used to flash the modem file.

What are you seeing in the nRF Connect programmer app when connected through the JLink Edu? Please provide a screenshot.

Best regards,
Carl Richard

RE: Thingy 91 debug using J link Edu

Rkidechaa — Wed, 28 Oct 2020 00:02:40 GMT

Hi Carl,

I got your point regarding MCU boot mode. I did it earlier successfully but now when I tried to reload the modem firmware but every time showing the below error.

But when I tried to set nRF52840 into MCU boot mode it goes under boot mode but nRF9160 did not.

So the question is we tried to load the hello_world program using J link Edu (which was not done successfully) due to this IC got damaged or blocked? otherwise, it should go under MCU boot mode.

Might be we had done some mistake while flashing the code but there should be the other way to reset the nRF9160 or bring it back to life.

Can we upload the modem file using J link Edu?

Thanks and Regards,

Rahul Kidecha

RE: Thingy 91 debug using J link Edu

Carl Richard — Tue, 27 Oct 2020 10:04:30 GMT

Hello, Rahul.

I see. I believe that the "install package" prompt you are getting when opening Segger is because you already have a standalone Segger installation on your computer. Correct? You can try one of the fixes described in this thread. However, the error should be harmless.

When it comes to SES hanging. Is it totally unresponsive, or are you able to do some things (like opening a new project for example)? It can be a bit slow and stutter at times, mind you.

When it comes to the Thingy:91 programming, it may be that the bootloader was overwritten (which is required for MCU Boot). Are you able to read the memory of the Thingy:91 in the nRF Connect programmer app when it's connected using the JLINK? If so, post a screenshot of it here.

To reenable MCU Boot I recommend flashing one of the full images from the Thingy:91 firmware package, located on the product page.

Best regards,
Carl Richard

RE: Thingy 91 debug using J link Edu

Rkidechaa — Tue, 27 Oct 2020 00:18:33 GMT

Hello Carl,

Now to avoid all the problems what I have done is created a new account with just a name and tried to build and flash the hello program using j link Edu.

we tried 1st time everything worked well but we were not able to see the output on the terminal. So we tried to flash it again but now, what is happening that when I open segger with toolchain manager software was getting hang not allowing to anything?

Also showing below error everytime when I click on open IDE.

Now when clicking on Yes to all or No to all. software is getting the hang (while j link Edu is connected)

Another thing is that now when I tried to load the pre-compiled Hex file it was not going under the MCU mode. (I know how to set in MCU mode)

Questions:

might be earlier we have done some mistake while flashing the hello program which led to any failure of the thingy:91?

can we reset thingy 91 OR clear the flash memory?

I am enclosing the photos of physical connection pf thingy 91 with PC using j link Edu.( Let me know if you find any problem in connection)

With regards,

Rahul Kidecha

RE: Thingy 91 debug using J link Edu

Rkidechaa — Mon, 26 Oct 2020 20:59:22 GMT

Hello, carl!!

Thank you for your reply.

What version of the Thingy:91 are you using?

Version :PCA20035

Regarding the error will sport a screenshot shortly. Do you have any features where I can upload the whole procedure?

Thanks,

Rahul Kidecha

RE: Thingy 91 debug using J link Edu

Carl Richard — Mon, 26 Oct 2020 13:06:25 GMT

Hi again, Rahul.

Thank you for the response. What version of the Thingy:91 are you using?

[quote user="Rkidechaa"]I have done the research for the error and that could be one possibility that space between my user name. which are not allowing segger to connect path.[/quote]

This is most likely correct! Changing the username and updating the path correctly can be a bit of a hassle, but Microsoft have described the approach here. Anyway, what kind of hang/error did you get on the other PC? Could you provide some screenshots/logs?

We do not have any video tutorial, but we provide a quite extensive guide on getting started with the Thingy:91. It also describes how you can setup projects in SES.

Most samples are configured for output over UART, which will require a micro-usb to be able to display it in the terminal. Alternatively the sample can be configured to use RTT. The output from the debugger will then be available with the Segger RTT Viewer.

Best regards,
Carl Richard

RE: Thingy 91 debug using J link Edu

Rkidechaa — Mon, 26 Oct 2020 03:50:41 GMT

Hello, CARL!!

Could you first state what Thingy:91 version you have and whether or not you are using the Toolchain manager?
Ans: tried to debug thingy 91 using j link Edu using SWD pins.

Secondly, you are flashing the Zephyr hello_world sample, correct? There are not supposed to be any blinking LEDs when using that sample, and for MCU boot to function with the sample it must be added in prj.conf like this
CONFIG_MCUBOOT=y

Ans:  Yes. I have created the prj.conf file as per the tutorial.
Lastly, I see that you are building for the "board name" thingy91_nrf9160, use thingy91_nrf9160ns instead.
Ans:  Got it I have downloaded the board file for thingy 91 and made the changes as you said.
I Made all changes but I am still getting the same error that I informed you of at the beginning. I have done the research for the error and that could be one possibility that space between my user name. which are not allowing segger to connect path. I tried to change the user name folder but I guess now I can not change the same. (suggest to me how to solve this problem).
To avoid the user name problem I used another PC and did the step shown in the tutorial. after setting the cmakelist.txt, Board directory, board name, and build directory when I click on the OK button segger was getting hang. (Tried 3 times and getting the same error)
Do you have any videos tutorial which can show the step clearly?
also to check the output do we need to connect more cable to the micro USB connector or just j-link Edu cable is sufficient?
Thanks,
Rahul Kidecha

RE: Thingy 91 debug using J link Edu

Carl Richard — Thu, 22 Oct 2020 14:29:10 GMT

Hello, Rahul!

Thank you for reaching out! Could you first state what Thingy:91 version you have and wheter or not you are using the Toolchain manager?

Secondly, you are flashing the Zephyr hello_world sample, correct? There are not supposed to be any blinking LEDs when using that sample, and for MCU boot to function with the sample it must be added in prj.conf like this:

CONFIG_MCUBOOT=y

Lastly, I see that you are building for the "board name" thingy91_nrf9160, use thingy91_nrf9160ns instead.

Hope this helps!

Best regards,
Carl Richard