Thingy91: Process to flash s340 and 52840

RE: Thingy91: Process to flash s340 and 52840

Albrecht Markus Schellenberger — Mon, 29 Nov 2021 09:55:36 GMT

[quote user="Brett"]

Thank You !!

That was the answer, I should have RTM - it was all there - code runs now as it does on the 9160 DK.

[/quote]

My pleasure, Brett! I’m glad to hear that it works now :-)

Cheers,

Markus

RE: Thingy91: Process to flash s340 and 52840

Brett — Fri, 26 Nov 2021 19:48:12 GMT

Hi Markus,

Thank You !!

That was the answer, I should have RTM - it was all there - code runs now as it does on the 9160 DK.

In the end:
52840:

.tx_pin = 25,
.rx_pin = 32,

9160:
&uart1 {
        compatible = "nordic,nrf-uarte";
        status = "okay";
        current-speed = <115200>;
    hw-flow-control;
        tx-pin = <22>;
        rx-pin = <23>;
        rts-pin = <24>;
        cts-pin = <25>;
};

regards
-brett

RE: Thingy91: Process to flash s340 and 52840

Albrecht Markus Schellenberger — Fri, 26 Nov 2021 12:38:13 GMT

Hello Brett,

[quote user="Brett"]Yes I am, thats how I was connecting UART's between the 52840 and the 9160. I gather based on your question, I need to use different pins in the thingy vs the 9160DK.[/quote]

Yes, this is my theory at least :-) See, the SWD interface can also be controlled by the nRF52840, as explained here.

And according to the Thingy:91 pin mapping, P0.14 and P0.17 of the nRF52840 are assigned to the nRF9160 SWD interface data/control line.

P0.14	IF_SWD_IO	nRF9160 SWD interface data line
P0.17	IF_SWD_CTRL	nRF9160 SWD interface control

So what I think happens here is that your nRF52840 application interferes the nRF9160 SWD interface control line and causes the trouble your are currently facing.

However, in order to establish a proper UART connection between the nRF9160 &nRF52840, you might need to change the pin configuration anyway. The pictures below provide you with an overview of which pins you can choose from, respectively. They are taken from the latest Thingy:91 schematic and PCB layout file, which can be downloaded here.

Regards,

Markus

RE: Thingy91: Process to flash s340 and 52840

Brett — Thu, 25 Nov 2021 21:16:40 GMT

Hi Markus:

Yes I am, thats how I was connecting UART's between the 52840 and the 9160. I gather based on your question, I need to use different pins in the thingy vs the 9160DK.

52840:

nrf_libuarte_async_config_t nrf_libuarte_async_config = {
      .tx_pin = 17,
      .rx_pin = 20,
      .baudrate = NRF_UARTE_BAUDRATE_115200,
      .parity = NRF_UARTE_PARITY_EXCLUDED,
      .hwfc = NRF_UARTE_HWFC_DISABLED,
      .timeout_us = 100,
      .int_prio = APP_IRQ_PRIORITY_LOW};

9160:

&uart1 {
        compatible = "nordic,nrf-uarte";
        status = "okay";
        current-speed = <115200>;
    hw-flow-control;
        tx-pin = <18>;
        rx-pin = <17>;
        rts-pin = <19>;
        cts-pin = <21>;
}:

regards
-brett

RE: Thingy91: Process to flash s340 and 52840

Albrecht Markus Schellenberger — Thu, 25 Nov 2021 11:55:04 GMT

Hello Brett,

[quote user="Brett"]Its only when I load them both together I am unable to test, as I cant connect to the 9160 interface for debugging.[/quote]

Thanks a lot for the detailed feedback! Are you possibly using P.014 and/or P0.17 in your nRF52840 application?

Regards,

Markus

RE: Thingy91: Process to flash s340 and 52840

Brett — Thu, 25 Nov 2021 11:16:31 GMT

Hey Markus,

One more comment for today, after some testing:

I tested each set of code individually and they work independently, I still have the issue of not being able to access the 9160 when I have my code on the 52840, but:

52840 : (9160 is empty/erased) - receives ANT+ messages and displays them in the log

9160 : (52840 is empty/erased) - connects to MQTT server, receives GPS and sends to MQTT

Its only when I load them both together I am unable to test, as I cant connect to the 9160 interface for debugging.

regards
-brett

RE: Thingy91: Process to flash s340 and 52840

Brett — Wed, 24 Nov 2021 19:42:21 GMT

Hi Markus,

I also noticed.

If I have the JLinkExe connected to the 9160 and then try to connect again from the nrfConnect programmer, I get the same error, `Could not fetch memory size of target devkit: Error: Error occured when get library info. Errorcode: CouldNotOpenDevice (0x4) Lowlevel error: JLINKARM_DLL_ERROR (ffffff9a)`.

Is there any way my code is doing something which has the same effect as this ? Be that, opening a port, clocking , UART or ?

All of this works on the 9160DK, is there something fundamentally different between the thingy91 and 9160DK which I have not catered for ?

regards
-brett

RE: Thingy91: Process to flash s340 and 52840

Brett — Wed, 24 Nov 2021 19:30:59 GMT

A few more debugs:

This is with my code on the 52840 and SW2 on nRF91:

JLinkExe -if SWD
SEGGER J-Link Commander V6.88a (Compiled Nov 18 2020 15:09:53)
DLL version V6.88a, compiled Nov 18 2020 15:09:35

Connecting to J-Link via USB...O.K.
Firmware: J-Link EDU Mini V1 compiled Feb 18 2021 11:25:23
Hardware version: V1.00
S/N: 801036805
License(s): FlashBP, GDB
VTref=1.788V

Type "connect" to establish a target connection, '?' for help
J-Link>connect
Please specify device / core. <Default>: CORTEX-M4
Type '?' for selection dialog
Device>?
Specify target interface speed [kHz]. <Default>: 4000 kHz
Speed>
Device "NRF9160_XXAA" selected.

Connecting to target via SWD
ConfigTargetSettings() start
---Setting ROM table---
ConfigTargetSettings() end
ConfigTargetSettings() start
---Setting ROM table---
ConfigTargetSettings() end
ConfigTargetSettings() start
---Setting ROM table---
ConfigTargetSettings() end
ConfigTargetSettings() start
---Setting ROM table---
ConfigTargetSettings() end
Cannot connect to target.

I then SW2 (nRF52) erased my code, put it back on the 9160 SW2 (nRF91) and did the same:

JLinkExe -if SWD
SEGGER J-Link Commander V6.88a (Compiled Nov 18 2020 15:09:53)
DLL version V6.88a, compiled Nov 18 2020 15:09:35

Connecting to J-Link via USB...O.K.
Firmware: J-Link EDU Mini V1 compiled Feb 18 2021 11:25:23
Hardware version: V1.00
S/N: 801036805
License(s): FlashBP, GDB
VTref=1.791V

Type "connect" to establish a target connection, '?' for help
J-Link>connect
Please specify device / core. <Default>: CORTEX-M33
Type '?' for selection dialog
Device>
Specify target interface speed [kHz]. <Default>: 4000 kHz
Speed>
Device "CORTEX-M33" selected.

Connecting to target via SWD
Found SW-DP with ID 0x6BA02477
SWD speed too high. Reduced from 4000 kHz to 2025 kHz for stability
DPIDR: 0x6BA02477
Scanning AP map to find all available APs
AP[7]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0x84770001)
AP[1]: AHB-AP (IDR: 0x24770011)
AP[2]: JTAG-AP (IDR: 0x12880000)
AP[3]: APB-AP (IDR: 0x54770002)
AP[4]: JTAG-AP (IDR: 0x12880000)
AP[5]: JTAG-AP (IDR: 0x12880000)
AP[6]: MEM-AP (IDR: 0x128800A1)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FF000
CPUID register: 0x410FD212. Implementer code: 0x41 (ARM)
Found Cortex-M33 r0p2, Little endian.
FPUnit: 8 code (BP) slots and 0 literal slots
Security extension: implemented
Secure debug: enabled
CoreSight components:
ROMTbl[0] @ E00FF000
ROMTbl[0][0]: E000E000, CID: B105900D, PID: 000BBD21 Cortex-M33
ROMTbl[0][1]: E0001000, CID: B105900D, PID: 000BBD21 DWT
ROMTbl[0][2]: E0002000, CID: B105900D, PID: 000BBD21 FPB
ROMTbl[0][3]: E0000000, CID: B105900D, PID: 000BBD21 ITM
ROMTbl[0][5]: E0041000, CID: B105900D, PID: 002BBD21 ETM
ROMTbl[0][6]: E0042000, CID: B105900D, PID: 000BBD21 CSS600-CTI
Cortex-M33 identified.

RE: Thingy91: Process to flash s340 and 52840

Brett — Wed, 24 Nov 2021 19:12:36 GMT

Yes the selector is on nRF91.

When I change the switch to nRF91, and then do a read, or close/open the device or powercycle the device I always get the error:
`2021-11-24T10:35:26.001Z ERROR Could not fetch memory size of target devkit: Error: Error occured when get library info. Errorcode: CouldNotOpenDevice (0x4) Lowlevel error: JLINKARM_DLL_ERROR (ffffff9a)`

This only happens when I have my code loaded onto the 52840.

regards
-brett

RE: Thingy91: Process to flash s340 and 52840

Albrecht Markus Schellenberger — Wed, 24 Nov 2021 11:53:12 GMT

Thanks for the valuable feedback, Brett!

[quote user="Brett"]* SW 9160 - read (fails with the error you can see a the bottom of the log)[/quote]

I’m a little bit confused here, because the log does not say nRF9160:

2021-11-24T10:35:03.512Z INFO Using nrfjprog to communicate with target
2021-11-24T10:35:04.420Z INFO Using J-Link Software version 6.88
2021-11-24T10:35:05.170Z INFO Segger serial:  801036805
2021-11-24T10:35:05.170Z INFO Segger speed:  2000  kHz
2021-11-24T10:35:05.170Z INFO Segger version:  J-Link EDU Mini V1 compiled Feb 18 2021 11:25:23
2021-11-24T10:35:05.171Z INFO Core probed: 801036805
2021-11-24T10:35:05.171Z INFO Core RAM: 256KiB
2021-11-24T10:35:05.171Z INFO Core ROM: 1024KiB in pages of 4KiB
2021-11-24T10:35:05.291Z INFO Model: NRF52840_xxAA_REV2.
2021-11-24T10:35:06.083Z INFO Core0: Reading device non-volatile memory. This may take a few seconds.
2021-11-24T10:35:15.877Z INFO Core0: Non-volatile memory has been read. 4 non-empty memory blocks identified 
2021-11-24T10:35:15.987Z INFO SoftDevice detected, id 0xCE (S340 v7.0.1)
2021-11-24T10:35:15.990Z INFO SoftDevice detected, id 0xCE (S340 v7.0.1)
2021-11-24T10:35:25.414Z INFO Using nrfjprog to communicate with target
2021-11-24T10:35:26.001Z ERROR Could not fetch memory size of target devkit: Error: Error occured when get library info. Errorcode: CouldNotOpenDevice (0x4)
Lowlevel error: JLINKARM_DLL_ERROR (ffffff9a)

2021-11-24T10:38:39.050Z ERROR Unable to open log file: Could not find file at path: /Users/bdunstan/Library/Application Support/nrfconnect/pc-nrfconnect-programmer/logs/2021-11-24T04_00_30.042Z-log.txt
2021-11-24T10:38:41.589Z ERROR Unable to open log file: Could not find file at path: /Users/bdunstan/Library/Application Support/nrfconnect/pc-nrfconnect-programmer/logs/2021-11-24T04_00_30.042Z-log.txt

2021-11-24T10:35:05.291Z INFO Model: NRF52840_xxAA_REV2.

Have you switched SWD SELECT (SW2) to nRF91?

Regards,

Markus

RE: Thingy91: Process to flash s340 and 52840

Brett — Wed, 24 Nov 2021 10:43:41 GMT

devzone.nordicsemi.com/.../2021_2D00_11_2D00_24T04_5F00_00_5F00_30.042Z_2D00_log.txt

Sorry, but wasnt sure how to add attachments...

RE: Thingy91: Process to flash s340 and 52840

Brett — Wed, 24 Nov 2021 10:41:12 GMT

Hi Markus,

[quote userid="100109" url="~/f/nordic-q-a/81291/thingy91-process-to-flash-s340-and-52840/340354#340354"]

Are you generally able to flash the Connectivity Bridge and a nRF9160 application from the firmware package mentioned in my previous post?
Which tool are you using respectively to flash your applications?
Can you once again provide me with a log showing the error you are facing while trying to flash the nRF9160?

[/quote]

* I have flashed the connectivity bridge to the 52840 - no problems and also the asset-tracker app to the 9160 - no problems

* I generally use the nrf-connect programmer to flash images to 52840 and 9160 - as well as the soft device. But, I have also used nrfjprog to flash the soft device and west to flash the other image - same issue occurs.

I have attached a log file to the case, of which it contains:

* SW 9160 - erase all (successful)
* SW 52840 - erase all (successful)
* SW 52840 - write my image (successful)
* SW 9160 - read (fails with the error you can see a the bottom of the log)

`2021-11-24T10:35:26.001Z ERROR Could not fetch memory size of target devkit: Error: Error occured when get library info. Errorcode: CouldNotOpenDevice (0x4) Lowlevel error: JLINKARM_DLL_ERROR (ffffff9a) `

I like the theory of the different tool-chains, but how to get around this - as I need ANT+ which is only supported in the old SDK (or thats what I was told).

regards
-brett

RE: Thingy91: Process to flash s340 and 52840

Albrecht Markus Schellenberger — Tue, 23 Nov 2021 13:36:36 GMT

Thanks a lot again for your detailed explanation of the issue, Brett!

[quote user="Brett"]In reading the docs, I didnt see anything about an order in which you had to flash the images, so I am sure I am doing something wrong :).[/quote]

Generally, the nRF9160 and nRF52840 should be able to operate independently from each other on the Thingy:91. So I’m a bit surprised that you are facing this issue.

However, I do not have any experience with software from two different tool chains running on the Thingy:91. And unfortunately, I do not have my Thingy:91 available for at least this week. Anyway, let us see what we can do here.

Are you generally able to flash the Connectivity Bridge and a nRF9160 application from the firmware package mentioned in my previous post?
Which tool are you using respectively to flash your applications?
Can you once again provide me with a log showing the error you are facing while trying to flash the nRF9160?

Thanks and regards,

Markus

RE: Thingy91: Process to flash s340 and 52840

Brett — Tue, 23 Nov 2021 12:09:02 GMT

Hi Markus,

More than happy to start again, there is a whole lot of stuff above.

Connection:
* I am connected the same as the picture above and I also have a j-link edu mini that I am using, both give the same outcome.

Project Objective:
Receive Bike power data via ANT+ on the 52840 (soft device 340) transfer this data over UART to the 9160, so it can then send the data (with GPS) to an MQTT receiver. All of the code works on the 9160DK, so it was now time to transfer it to the thingy 91, which is where I am stuck.

Details:
I can flash the 52840 with out a problem and the code I have appears to work. I connected via Jlink and can see the NRF_LOG messages coming to the terminal window, that all looks good. Appears to work means, I can receive ANT+ messages from my bike power meter and able to LOG them to the terminal - UART connection to the 9160 is not yet successful.

I can flash the 9160 image, as long as I dont have any code on the 52840. So, if I erase-all on the 52840, I can flash the image fine. But, if I have my image on the 52840 first, I am unable to falsh the 9160. Today, I managed to get some debug messages on the RTT-Terminal window, but have not done enough testing to confirm if its actually getting the GPS co-ordinates correctly, or connecting to the network correctly - I will test that tomorrow.

Issue:
The real issue that I am faced with at the moment is, if I have my image flashed to the 52840, I cant flash the 9160. If I flash the 9160 first, I can flash the 52840 - but have not then been able to connect back onto the 9160 - until I remove the image from the 52840. If I remove the 51840 image, I can then connect back onto the 9160 and see the image that I originally flashed.

In reading the docs, I didnt see anything about an order in which you had to flash the images, so I am sure I am doing something wrong :).

I can record a screen capture of what I am doing if that helps, or I have pushed my latest code to github if you are interested. If you would like a flow diagram of the project, I can easily draw one.

9160 : github.com/.../gps_iot_thingy
52840: github.com/.../ant_app_libUARTE

regards
-brett

RE: Thingy91: Process to flash s340 and 52840

Albrecht Markus Schellenberger — Tue, 23 Nov 2021 09:49:31 GMT

[quote user="Brett"]

Status is basically the same, whenever I load my code on the 52840, the 9160 is inaccessible.

I can confirm the 52840 code is flashed correctly, as I can get some printf() logs on the debug terminal (NRF_LOG not working yet).

[/quote]

Thanks a lot for the feedback! I honestly struggle a little bit with remembering all the details here, so I would appreciate if we could start all over again :-)

Is the Thingy:91 setup you have according to the picture below?

And are you in general able to successfully flash the nRF52840 with the Connectivity bridge and respectively the nRF9160 with one of the other applications included in this firmware package?

Regards,

Markus

RE: Thingy91: Process to flash s340 and 52840

Brett — Mon, 22 Nov 2021 19:10:34 GMT

Hi Markus,

Status is basically the same, whenever I load my code on the 52840, the 9160 is inaccessible.

I can confirm the 52840 code is flashed correctly, as I can get some printf() logs on the debug terminal (NRF_LOG not working yet).

regards
-brett

RE: Thingy91: Process to flash s340 and 52840

Albrecht Markus Schellenberger — Mon, 22 Nov 2021 12:51:56 GMT

Hello Brett,

my apologies for the delayed answer! I will take over this case from Kenneth.

[quote user="Brett"]No matter what I do, as soon as I flash anything to the 52840, I am unable to re-access the 9160. If I erase the 52840 I can see the 9160 and the image that was flashed to it.[/quote]

Is the status still the same or have you been able to make some progress?

I need to read through the whole case and dive a little into the issue. I will come back to you as soon as possible.

Regards,

Markus

RE: Thingy91: Process to flash s340 and 52840

Brett — Sat, 20 Nov 2021 05:25:49 GMT

Hi Kenneth,

I was a bit optimistic when I said I got it to work 🙂

No matter what I do, as soon as I flash anything to the 52840, I am unable to re-access the 9160. If I erase the 52840 I can see the 9160 and the image that was flashed to it.

In all cases, my code on 5280 = no access to 9160.

Can you confirm my original logic: all code was built and works fine on the 9160DK but I cant get it to work on the thingy.
* 9160 = using zephr
* 52840 = software is using ANT+ therefore, I require the s340 softdevice and am using the legacy nRF5 SDK - since its not supported in zephyr.

I have put my code on github if there is anything that will help define what I am doing wrong, I will continue to test.

9160 : github.com/.../gps_iot_thingy
52840: github.com/.../ant_app_libUARTE

regards
-brett

RE: Thingy91: Process to flash s340 and 52840

Brett — Fri, 19 Nov 2021 05:27:06 GMT

Hi Kenneth,

I got it to work, but want to confirm my logic.

If I write my code to the 52840 I am then not able to access the 9160, eg:

5280 = empty
9160 = able see and access

52840 = load my code
9160 = not able to access

52840 = erase my code
9160 = able to see and access

9160 = load my code
52840 = load my code

As long at the 52840, doenst have any code on it - I was able to access it.

regards

-brett

RE: Thingy91: Process to flash s340 and 52840

Brett — Thu, 18 Nov 2021 09:50:09 GMT

Hey Kenneth,

More details, this is leading up to current state of not working:

The thingy was working fine before I started all this, as I tested with the default tracking app

I uploaded my own code onto the 9160 via the USB with MCU Boot, and it seemed to work fine however I was unable to load my 52840 code, hence the reason for going through jlink on the 9160dk, of which that is all working but.

So before I bricked the thingy 91 (9160) it was all working.

When I did the mcu-boot, it originally didnt work due to the memory layout or something, so I followed one of the online guides to get the resolved:

essentially:

CMakeLists.txt

list(APPEND mcuboot_OVERLAY_CONFIG
 "${CMAKE_CURRENT_SOURCE_DIR}/mcuboot_overlay-thingy91.conf"
 )

mcuboot_overlay-thingy91.conf

CONFIG_BOOT_SIGNATURE_TYPE_RSA=y
CONFIG_BOOT_SIGNATURE_KEY_FILE="root-rsa-2048.pem"

Not sure it that had something to do with it ?

I managed to get access to another thingy 91 to ensure it was not my cables or machine and can see the 9160 and 52840 - so I know all my connections etc... are good, and it appears to be the 9160 ?

Therefore, back to the current issue, if I have bricked it, how do I un-brick it - or if its dead hardware, how do I confirm this ?

cheers
-brett

RE: Thingy91: Process to flash s340 and 52840

Brett — Thu, 18 Nov 2021 09:35:51 GMT

Hi Kenneth,

I have installed 6.88.a

nrfjprog --version
nrfjprog version: 10.12.2
JLinkARM.dll version: 6.88a

I am also running 3.7.1 as per your details above.

I can still see the 52840 fine, so know its all connected, but same issue with the 9160:

Error:
2021-11-18T05:45:10.886Z INFO Application data folder: /Users/bdunstan/Library/Application Support/nrfconnect/pc-nrfconnect-programmer
2021-11-18T05:45:10.978Z INFO Using nrfjprog library 10.12.1, pc-nrfjprog-js 1.7.6
2021-11-18T05:45:11.022Z DEBUG App pc-nrfconnect-programmer v1.4.11 official
2021-11-18T05:45:11.022Z DEBUG App path: /Users/bdunstan/.nrfconnect-apps/external/3.7 compatible apps/node_modules/pc-nrfconnect-programmer
2021-11-18T05:45:11.022Z DEBUG nRFConnect 3.7.1, required by the app is (^3.6.0)
2021-11-18T05:45:11.022Z DEBUG nRFConnect path: /Applications/nRF Connect.app/Contents/Resources/app.asar
2021-11-18T05:45:11.022Z DEBUG HomeDir: /Users/bdunstan
2021-11-18T05:45:11.022Z DEBUG TmpDir: /var/folders/2c/gmmw_pdn0yd3v6wc1vj0d2mm0000gn/T/
2021-11-18T05:45:11.899Z VERBOSE Could not fetch serial number for serial port at /dev/tty.Bluetooth-Incoming-Port
2021-11-18T05:45:11.899Z VERBOSE Could not fetch serial number for serial port at /dev/tty.BoseQuietComfort35-SPPD
2021-11-18T05:45:11.899Z VERBOSE Could not fetch serial number for serial port at /dev/tty.BoseMicroSoundLink-SPPD
2021-11-18T09:24:54.062Z INFO Using nrfjprog to communicate with target
2021-11-18T09:24:55.458Z INFO Using J-Link Software version 6.88
2021-11-18T09:24:56.328Z INFO Segger serial: 960048905
2021-11-18T09:24:56.328Z INFO Segger speed: 2000 kHz
2021-11-18T09:24:56.328Z INFO Segger version: J-Link OB-K22-NordicSemi compiled Apr 29 2021 15:10:52
2021-11-18T09:24:56.329Z INFO Core probed: 960048905
2021-11-18T09:24:56.329Z INFO Core RAM: 256KiB
2021-11-18T09:24:56.329Z INFO Core ROM: 1024KiB in pages of 4KiB
2021-11-18T09:24:56.450Z INFO Model: NRF52840_xxAA_REV2.
2021-11-18T09:24:57.216Z INFO Core0: Reading device non-volatile memory. This may take a few seconds.
2021-11-18T09:24:57.967Z INFO Core0: UICR has been read. Click read button to read full non-volatile memory.
2021-11-18T09:25:11.347Z INFO Using nrfjprog to communicate with target
2021-11-18T09:25:11.955Z ERROR Could not fetch memory size of target devkit: Error: Error occured when get library info. Errorcode: CouldNotOpenDevice (0x4)
Lowlevel error: JLINKARM_DLL_ERROR (ffffff9a)

I have also connected it to a j-link edu mini, I can see the 52840 - but unable to see the 9160:

Error:
2021-11-18T09:31:14.124Z INFO Application data folder: /Users/bdunstan/Library/Application Support/nrfconnect/pc-nrfconnect-programmer
2021-11-18T09:31:14.196Z INFO Using nrfjprog library 10.12.1, pc-nrfjprog-js 1.7.6
2021-11-18T09:31:14.254Z DEBUG App pc-nrfconnect-programmer v1.4.11 official
2021-11-18T09:31:14.254Z DEBUG App path: /Users/bdunstan/.nrfconnect-apps/external/3.7 compatible apps/node_modules/pc-nrfconnect-programmer
2021-11-18T09:31:14.254Z DEBUG nRFConnect 3.7.1, required by the app is (^3.6.0)
2021-11-18T09:31:14.255Z DEBUG nRFConnect path: /Applications/nRF Connect.app/Contents/Resources/app.asar
2021-11-18T09:31:14.255Z DEBUG HomeDir: /Users/bdunstan
2021-11-18T09:31:14.255Z DEBUG TmpDir: /var/folders/2c/gmmw_pdn0yd3v6wc1vj0d2mm0000gn/T/
2021-11-18T09:31:15.132Z VERBOSE Could not fetch serial number for serial port at /dev/tty.Bluetooth-Incoming-Port
2021-11-18T09:31:15.132Z VERBOSE Could not fetch serial number for serial port at /dev/tty.BoseQuietComfort35-SPPD
2021-11-18T09:31:15.132Z VERBOSE Could not fetch serial number for serial port at /dev/tty.BoseMicroSoundLink-SPPD
2021-11-18T09:31:29.251Z INFO Using nrfjprog to communicate with target
2021-11-18T09:31:29.654Z ERROR Could not fetch memory size of target devkit: Error: Error occured when get library info. Errorcode: CouldNotOpenDevice (0x4)
Lowlevel error: LOW_VOLTAGE (fffffff4)

2021-11-18T09:31:38.214Z INFO Using nrfjprog to communicate with target
2021-11-18T09:31:39.001Z INFO Using J-Link Software version 6.88
2021-11-18T09:31:39.734Z INFO Segger serial: 801036805
2021-11-18T09:31:39.734Z INFO Segger speed: 2000 kHz
2021-11-18T09:31:39.735Z INFO Segger version: J-Link EDU Mini V1 compiled Feb 18 2021 11:25:23
2021-11-18T09:31:39.738Z INFO Core probed: 801036805
2021-11-18T09:31:39.738Z INFO Core RAM: 256KiB
2021-11-18T09:31:39.738Z INFO Core ROM: 1024KiB in pages of 4KiB
2021-11-18T09:31:39.871Z INFO Model: NRF52840_xxAA_REV2.
2021-11-18T09:31:40.611Z INFO Core0: Reading device non-volatile memory. This may take a few seconds.
2021-11-18T09:31:50.357Z INFO Core0: Non-volatile memory has been read. 4 non-empty memory blocks identified
2021-11-18T09:31:50.479Z INFO SoftDevice detected, id 0xCE (S340 v7.0.1)
2021-11-18T09:32:02.244Z INFO Using nrfjprog to communicate with target
2021-11-18T09:32:02.762Z ERROR Could not fetch memory size of target devkit: Error: Error occured when get library info. Errorcode: CouldNotOpenDevice (0x4)
Lowlevel error: JLINKARM_DLL_ERROR (ffffff9a)

2021-11-18T09:33:21.963Z INFO Target device closed.
2021-11-18T09:33:26.730Z INFO Using nrfjprog to communicate with target
2021-11-18T09:33:27.222Z ERROR Could not fetch memory size of target devkit: Error: Error occured when get library info. Errorcode: CouldNotOpenDevice (0x4)
Lowlevel error: JLINKARM_DLL_ERROR (ffffff9a)

Is there something fundamental I am missing ?

I assume with the j-link or 9160DK, I dont need to press any other buttons on the thingy91 to get it to work, reset or ??

Is there an option to do a full/hardware reset ?

regards
-brett

RE: Thingy91: Process to flash s340 and 52840

Kenneth — Tue, 16 Nov 2021 08:23:10 GMT

It may seem like an issue with nrf connect v3.8/3.9 and/or jlink at the moment, from the log I can see it is not able to switch from the nRF52840 to nRF9160. Can you try to install JLink til v6.88a from https://www.segger.com/downloads/jlink (uninstall possible newer version first) and try again?

If still is no luck, then you may need to downgrade to nrf connect v3.7 and install apps that is compatible with that release.:

Download the latest 3.7 version of nRF Connect for Desktop from https://www.nordicsemi.com/Products/Development-tools/nRF-Connect-for-desktop/Download?lang=en#infotabs (for macOS this is 3.7.2, for Windows and Linux 3.7.1).
After starting nRF Connect for Desktop 3.7 a prompt will come up about the 3.8 upgrade. Click “No” on this.
In the Settings, click on “Add source”, enter the URL http://developer.nordicsemi.com/.pc-tools/nrfconnect-apps/3.7-apps/apps.json and click “Add”.
Back in the list of all apps, all apps should show up twice now, one with “official” below them and one with “3.7 compatible apps” below them. If you want to hide the incompatible versions, click on “Filter” and deselect “Official”.
Install the apps you need in the old versions and use them.

RE: Thingy91: Process to flash s340 and 52840

Brett — Thu, 11 Nov 2021 20:04:25 GMT

I also tried the original way of flashing the 9160 (on the thingy), via the USB and MCUBoot method, but I cant even get the USB to work.

* Connect USB
* Hold down SW3 whilst turning on the thingy
* I dont see the device in the pulldown of the programmer, and I dont see any usb devices in /dev (I am on a mac)

RE: Thingy91: Process to flash s340 and 52840

Brett — Thu, 11 Nov 2021 19:49:46 GMT

Hi Kenneth,

Sorry for the slow response, I was waiting for a cable to arrive to test this process...

I was able to flash the 52840 with out a problem, however, when I tried to flash the 9160 I get the following error on the programmer:

2021-11-11T19:34:37.975Z INFO Using nrfjprog to communicate with target
2021-11-11T19:34:39.005Z INFO Using J-Link Software version 6.88
2021-11-11T19:34:39.794Z INFO Segger serial: 960048905
2021-11-11T19:34:39.794Z INFO Segger speed: 2000 kHz
2021-11-11T19:34:39.794Z INFO Segger version: J-Link OB-K22-NordicSemi compiled Apr 29 2021 15:10:52
2021-11-11T19:34:39.797Z INFO Core probed: 960048905
2021-11-11T19:34:39.797Z INFO Core RAM: 256KiB
2021-11-11T19:34:39.797Z INFO Core ROM: 1024KiB in pages of 4KiB
2021-11-11T19:34:39.916Z INFO Model: NRF52840_xxAA_REV2.
2021-11-11T19:34:40.742Z INFO Core0: Reading device non-volatile memory. This may take a few seconds.
2021-11-11T19:34:41.520Z INFO Core0: UICR has been read. Click read button to read full non-volatile memory.
2021-11-11T19:34:51.571Z INFO Using nrfjprog to communicate with target
2021-11-11T19:34:52.350Z INFO Using J-Link Software version 6.88
2021-11-11T19:34:53.102Z INFO Segger serial: 960048905
2021-11-11T19:34:53.103Z INFO Segger speed: 2000 kHz
2021-11-11T19:34:53.103Z INFO Segger version: J-Link OB-K22-NordicSemi compiled Apr 29 2021 15:10:52
2021-11-11T19:34:53.103Z INFO Core probed: 960048905
2021-11-11T19:34:53.103Z INFO Core RAM: 256KiB
2021-11-11T19:34:53.103Z INFO Core ROM: 1024KiB in pages of 4KiB
2021-11-11T19:34:53.230Z INFO Model: NRF52840_xxAA_REV2.
2021-11-11T19:34:54.013Z INFO Core0: Reading device non-volatile memory. This may take a few seconds.
2021-11-11T19:35:03.590Z INFO Core0: Non-volatile memory has been read. 4 non-empty memory blocks identified
2021-11-11T19:35:03.710Z INFO SoftDevice detected, id 0xCE (S340 v7.0.1)
2021-11-11T19:36:02.413Z INFO Using nrfjprog to communicate with target
2021-11-11T19:36:02.991Z ERROR Could not fetch memory size of target devkit: Error: Error occured when get library info. Errorcode: CouldNotOpenDevice (0x4)
Lowlevel error: JLINKARM_DLL_ERROR (ffffff9a)

2021-11-11T19:36:45.354Z INFO Target device closed.
2021-11-11T19:36:50.987Z INFO Using nrfjprog to communicate with target
2021-11-11T19:36:51.549Z ERROR Could not fetch memory size of target devkit: Error: Error occured when get library info. Errorcode: CouldNotOpenDevice (0x4)
Lowlevel error: JLINKARM_DLL_ERROR (ffffff9a)

When I try from the CLI, I get:
nrfjprog --eraseall
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.

I have tried

* restarting all boards but it still doesnt seem to be able to see or write to the 9160,

* confirmed SW2 set to nrf91 (on the thingy91)

* tried the Prog/DEBUG switch on the 9160 to nrf52 and nrf91

Since I was able to update the 52840 on the thingy, I assume the cable and connection is all good, but any other thoughts ?

cheers
-brett

RE: Thingy91: Process to flash s340 and 52840

Kenneth — Tue, 02 Nov 2021 12:40:24 GMT

[quote user=""]* For the 52840, do I need to use an external connection - say the 9160dk to be able to flash it ?[/quote]

Yes, then you have full control over the firmware you program (and not limited to DFU over a serial interface that may not allow update of for instance softdevice out of the box), so please follow this setup:
https://infocenter.nordicsemi.com/topic/ug_thingy91_gsg/UG/thingy91_gsg/updating_fw_ext_probe.html

It should be possible to use an j-link programmer or nRF DK to program the nRF52840 on the thingy91. Then you can also program using nrfjprog.

Kenneth