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,
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.
This is what you would have thought, I just wanted to make sure.
Could you answer the other questions I raised earlier also:
Karl Ylvisaker said: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.
Best regards,
Karl
Hello,
I have discussed this with a colleague, which was able to reproduce the issue you describe.
It seems that your device does not have the MCUboot - you can program this using an external debugger, or a nRF91 DK with a 10 pin connector.
If you then flash one of the newest samples onto your kit, it will also contain the MCUboot.
Best regards,
Karl
Thank you for your involvement.
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?
Physically same device
It seems that your device does not have the MCUboot
so this seems to be not the case.
If you then flash one of the newest samples onto your kit, it will also contain the MCUboot.
We also did that with 10 pin connector.
I guess I will renistall nRF Connect later today. Not a big hope tho.
Thank you for your involvement.
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?
Physically same device
It seems that your device does not have the MCUboot
so this seems to be not the case.
If you then flash one of the newest samples onto your kit, it will also contain the MCUboot.
We also did that with 10 pin connector.
I guess I will renistall nRF Connect later today. Not a big hope tho.
edgars.dev said:Thank you for your involvement.
No problem at all, I am happy to help and I hope we are able to resolve this issue shortly.
edgars.dev said:Physically same device
edgars.dev said:so this seems to be not the case.
Agreed, if you were able to flash the physically same device then the MCUboot must be present.
Do you know which operating system and nRF Connect version your friend was using?
I will check with the nRF Connect team, to see if they have any insight on the issue. I will update you when I have spoken with them.
Best regards,
Karl
Hello again,
Could you also verify for me which JLink version you have? In the case that it is not the latest version ( v6.80a ) then please update that as well.
This would be highly beneficial to know, in addition to the questions posed in my previous reply.
I am not sure that reinstalling nRF Connect will resolve this issue, but you may very well attempt it.
Let me know how it goes.
I am looking forward to resolving this issue together!
Best regards,
Karl
