Development for Thingy91X/nRF5340

[gocchan]

I want to develop for the nRF5340 on the Thingy91X. Are there any good sample projects that allow me to set the target board to Thingy91X/nRF5340/cpuapp?

I only need to scan using BLE and send AT commands to the nRF9151, so it doesn't need to be a Connectivity Bridge (it seems difficult to modify a Connectivity Bridge).

[gocchan]

I tried building Central BAS (NCS 3.2.4), but I'm getting an error during flashing.
I've set the board target to nrf5340dk/nrf5340/cpuapp/ns in the build conditions (because setting it to thingy91x/nrf5340/cpuapp/ns results in a build error). I haven't changed any code in prj.conf or similar files. I'm also not using an overlay.
I'm running "nrfutil device recover" before flashing. Running "nrfjprog --deviceversion" returns NRF5340_xxAA_REV1, so I think the connection to the IC is working.
The error message during flashing is as follows:

west flash -d c:\ncs\applications\central_bas_v3-2-4\build --dev-id 960033963 --erase

WARNING: Specifying runner options for multiple domains is experimental.
If problems are experienced, please specify a single domain using '--domain <domain>'
-- west flash: using runner nrfutil
-- runners.nrfutil: mass erase requested
-- runners.nrfutil: reset after flashing requested
-- runners.nrfutil: Flashing file: C:\ncs\applications\central_bas_v3-2-4\build\merged_CPUNET.hex
-- runners.nrfutil: Connecting to probe
-- runners.nrfutil: Erasing non-volatile memory (ERASEALL)
-- runners.nrfutil: Programming image
-- runners.nrfutil: Verifying image
-- runners.nrfutil: Reset
-- runners.nrfutil: Board(s) with serial number(s) 960033963 flashed successfully.
-- west flash: using runner nrfutil
-- runners.nrfutil: mass erase requested
-- runners.nrfutil: reset after flashing requested
-- runners.nrfutil: Flashing file: C:\ncs\applications\central_bas_v3-2-4\build\merged.hex
-- runners.nrfutil: Connecting to probe
Error: One or more batch tasks failed:
 * 960033963: Failed to attach to target: The Application core access port is protected (All) (NotAvailableBecauseProtection)

The operation was unavailable for some of the devices because they had readback protection enabled. These devices might be possible to unlock using the `recover` subcommand. See `nrfutil device recover --help` for more information.

ERROR: runners.nrfutil: Flashing failed because the target must be recovered.
  To fix, run "west flash --recover" instead.
  Note: your target is an nRF53; all flash memory for both the network and application cores will be erased prior to reflashing.
FATAL ERROR: command exited with status 24: nrfutil --json device --x-ext-mem-config-file C:/ncs/v3.2.4/zephyr/boards/nordic/nrf5340dk/support/nrf5340dk_qspi_nrfutil_config.json x-execute-batch --batch-path 'C:\ncs\applications\central_bas_v3-2-4\build\central_bas_v3-2-4\zephyr\generated_nrfutil_batch.json' --serial-number 960033963

[Nishant Gaurav]

Hi gocchan

you can recover manually first using nrfutil, making sure to recover the network core before the application core (this order is critical for nRF53 Series devices), use this command

• 1)  nrfutil device recover --core Network --serial-number 960033963
• 2)  nrfutil device recover --serial-number 960033963