Hello!
Thanks for your help last time, highly appreciated.
However I haven't got till actuall programming because now I can't upload hex files. I start Thingy:91 in boot mode, connect, press write and it immidiately goes in application mode and programmer sofware throws error that I have to check that it is in boot mode. I have no clue how to fix this. Any hints?
Edit: This videoplayer seems to be out of order. Uploaded video to youtube.
Kind regards!
Hello,
Thanks for your help last time, highly appreciated.
No problem at all, we are here to help!
However I haven't got till actuall programming because now I can't upload hex files. I start Thingy:91 in boot mode, connect, press write and it immidiately goes in application mode and programmer sofware throws error that I have to check that it is in boot mode. I have no clue how to fix this. Any hints?
I am sure you have seen the programming applications through USB ( MCUBoot ) guide, but I link it here just in case.
To verify if the issue is with the .hex used, or nRF Connect desktop application, could you go ahead and download the latest firmware from this site, and follow the programming applications guide to program the thingy91_ltem_dfu_2020-04-29_bc7ade8b.hex from the downloaded zip folder?
Please let me know if this works, or if you are encountering the same issue when doing this.
For the record, could you also tell me which NCS version you are working with?
Best regards,
Karl
Yes. Did everything exactly as it was told in instruction. Problem is that when I press Write button it immidiately resets MCU and after that it goes in to application mode (LEDs fade in) It doesn't even matter what hex file I provide.
v0.5, the one that I had hard time to set up and now it compiles hex. Anyhow. I don't see how it is related.
Programmer is v1.4.2
Hello again,
edgars.dev said:Problem is that when I press Write button it immidiately resets MCU and after that it goes in to application mode (LEDs fade in) It doesn't even matter what hex file I provide.
As shown in your video, it seems that the device stays in MCUBoot until you press write, at which point it reverts to application. What .hex files have you tried?
The .hex files needs to have the correct memory range, to be acceptable. The note from step 7 of the programing guide reads:
Note: A normal firmware image HEX file cannot be used when programming applications through USB, since the MCUboot bootloader is used. The HEX file needs to contain the application at the appropriate memory offset for use with MCUboot.
edgars.dev said:v0.5, the one that I had hard time to set up and now it compiles hex. Anyhow. I don't see how it is related.
What does this mean, what parts of my comment are you referring to here?
If you highlight a part of a comment and click the "quote" button that appears, it will be much easier to follow references in longer discussions here on the forum.
edgars.dev said:Programmer is v1.4.2
And which nRF Connect SDK Version are you working with, v.3.4.0?
Is the application you are trying to flash the unmodified asset tracker sample, or a modified version?
Best regards,
Karl
Hello again,
edgars.dev said:Problem is that when I press Write button it immidiately resets MCU and after that it goes in to application mode (LEDs fade in) It doesn't even matter what hex file I provide.
As shown in your video, it seems that the device stays in MCUBoot until you press write, at which point it reverts to application. What .hex files have you tried?
The .hex files needs to have the correct memory range, to be acceptable. The note from step 7 of the programing guide reads:
Note: A normal firmware image HEX file cannot be used when programming applications through USB, since the MCUboot bootloader is used. The HEX file needs to contain the application at the appropriate memory offset for use with MCUboot.
edgars.dev said:v0.5, the one that I had hard time to set up and now it compiles hex. Anyhow. I don't see how it is related.
What does this mean, what parts of my comment are you referring to here?
If you highlight a part of a comment and click the "quote" button that appears, it will be much easier to follow references in longer discussions here on the forum.
edgars.dev said:Programmer is v1.4.2
And which nRF Connect SDK Version are you working with, v.3.4.0?
Is the application you are trying to flash the unmodified asset tracker sample, or a modified version?
Best regards,
Karl
Is the application you are trying to flash the unmodified asset tracker sample, or a modified version?
Tried to write my own compiled hex from example. Tried the one you suggested. Tried one that my friend compiled and succesfully uploaded with his computer to the same thingy device. Some others as well, but that's irrelevant.
If you highlight a part of a comment and click the "quote" button that appears, it will be much easier to follow references in longer discussions here on the forum.
Ok, thanks, I will.
And which nRF Connect SDK Version are you working with, v.3.4.0?
Correct.
edgars.dev said:Ok, thanks, I will.
Great, the readability is highly increased already, thank you.
edgars.dev said:Tried one that my friend compiled and succesfully uploaded with his computer to the same thingy device.
When you say "the same thingy device", do you mean your friend's own thingy91, or the physically same device as you are having trouble with?
In case of the latter, I would recommend reinstalling your nRF Connect.
Have you updated your device to the most recent modem firmware, since you got it?
The process is described in the Updating Thingy:91 Firmware section.
Karl Ylvisaker said:edgars.dev said:v0.5, the one that I had hard time to set up and now it compiles hex. Anyhow. I don't see how it is related.
Furthermore, could you elaborate what you meant with this comment?
Looking forward to solving this issue together,
Best regards,
Karl
Furthermore, could you elaborate what you meant with this comment?
See my previous post. https://devzone.nordicsemi.com/f/nordic-q-a/61872/problem-with-setting-up-segger-on-mac
Now it is compiling.
Hello,
edgars.dev said:Now it is compiling.
By this, do you mean that your original issue is resolved - that you are now able to program your thingy 91 using the nRF Connect Programmer?
If so, was this resolved by updating the firmware of your device?
I am asking for future reference, if someone else should encounter the same issue.
Best regards,
Karl
Noo, not at all. I solved compiling issue in previous post. Now I am trying to solve hex write to mcu issue. Just answering your questions.
