RE: Flashing code on I/O shield using nRF5340 DK board

akhil — Sat, 14 Sep 2024 14:45:09 GMT

Hi Susheel,

Sorry for the delay in response. Yes till now we haven't been able to communicate with the I/O shield for flashing or erasing chip data. So can nRF5340 DK give that power spike to the I/O shield? because the maximum time we are powering up the I/O shield with DK is only using P20.

on the power consumption when we are powering up the I/O shield with the external power supply we are giving the I/O shield 3v power supply as suggested in the documents and it was drawing the current around 35mA.

RE: Flashing code on I/O shield using nRF5340 DK board

Susheel Nuguru — Thu, 05 Sep 2024 07:49:28 GMT

Have you ever succeeded in flashing or erasing this chip? I am thinking maybe there is not stable power? Also we have seen such reports if the DK was not given stable power and a power spike could have fried the chip.

Based on the logs you provided, the debugger is unable to communicate in any way to the chip.

RE: Flashing code on I/O shield using nRF5340 DK board

akhil — Thu, 05 Sep 2024 07:35:16 GMT

Hi Susheel Nuguru

Yes, I have tried to recover the two cores but don't know what exactly the issue is as I have checked the connection also on the hardware side it seems fine as given in the nRF5340 DK Board Document.

following are the commands I have used and their error logs:

[error] [ Client] - Encountered error -102: Command enable_coprocessor executed for 154 milliseconds with result -102
Failed to enable coprocessor with unknown error.
[error] [ Worker] - An unknown error.
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.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.
PS C:\nordic-dfu-main\nordic-dfu-main\blinky> nrfjprog --recover -f NRF53 --snr 1050083709 --coprocessor CP_APPLICATION --speed 1000
>>
ERROR: An invalid argument was provided. Use --help for a list of valid
ERROR: arguments.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.
PS C:\nordic-dfu-main\nordic-dfu-main\blinky> nrfjprog --recover -f NRF53 --snr 1050083709
>>
Recovering device. This operation might take 30s.
[error] [ Client] - Encountered error -21: Command recover executed for 139 milliseconds with result -21
[error] [ Worker] - An unknown error.
ERROR: Recover failed. Please make sure that the correct device family is given
ERROR: and try again.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.
PS C:\nordic-dfu-main\nordic-dfu-main\blinky> nrfjprog --recover -f NRF53 --snr 1050083709
>>
Recovering device. This operation might take 30s.
Erasing user code and UICR flash areas.
Writing image to disable ap protect.
PS C:\nordic-dfu-main\nordic-dfu-main\blinky> nrfjprog --recover -f NRF53 --snr 1050083709
>>
Recovering device. This operation might take 30s.
[error] [ Worker] - An unknown error.
[error] [ Client] - Encountered error -21: Command recover executed for 140 milliseconds with result -21
ERROR: Recover failed. Please make sure that the correct device family is given
ERROR: and try again.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.
PS C:\nordic-dfu-main\nordic-dfu-main\blinky> nrfjprog --recover -f NRF53 --snr 1050083709
>>
Recovering device. This operation might take 30s.
Erasing user code and UICR flash areas.
Writing image to disable ap protect.
PS C:\nordic-dfu-main\nordic-dfu-main\blinky> nrfjprog --recover -f nrf53 --coprocessor cp_network
[error] [ Client] - Encountered error -102: Command enable_coprocessor executed for 155 milliseconds with result -102
Failed to enable coprocessor with unknown error.
[error] [ Worker] - An unknown error.
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.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.
PS C:\nordic-dfu-main\nordic-dfu-main\blinky> :loop
>> nrfjprog --recover -f nrf52
>> goto loop
:loop : The term ':loop' is not recognized as the name of a cmdlet, function, script file, or operable program. 
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ :loop
+ ~~~~~
    + CategoryInfo          : ObjectNotFound: (:loop:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

Recovering device. This operation might take 30s.
[error] [ Client] - Encountered error -21: Command recover executed for 137 milliseconds with result -21
[error] [ Worker] - An unknown error.
ERROR: Recover failed. Please make sure that the correct device family is given
ERROR: and try again.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.
goto : The term 'goto' is not recognized as the name of a cmdlet, function, script file, or operable program. 
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:3 char:1
+ goto loop
+ ~~~~
    + CategoryInfo          : ObjectNotFound: (goto:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

PS C:\nordic-dfu-main\nordic-dfu-main\blinky> :loop
>> nrfjprog --recover -f nrf53
>> goto loop
:loop : The term ':loop' is not recognized as the name of a cmdlet, function, script file, or operable program. 
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ :loop
+ ~~~~~
    + CategoryInfo          : ObjectNotFound: (:loop:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

Recovering device. This operation might take 30s.
[error] [ Client] - Encountered error -21: Command recover executed for 137 milliseconds with result -21
[error] [ Worker] - An unknown error.
ERROR: Recover failed. Please make sure that the correct device family is given
ERROR: and try again.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.
goto : The term 'goto' is not recognized as the name of a cmdlet, function, script file, or operable program. 
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:3 char:1
+ goto loop
+ ~~~~
    + CategoryInfo          : ObjectNotFound: (goto:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

PS C:\nordic-dfu-main\nordic-dfu-main\blinky>
 *  History restored 

PS C:\nordic-dfu-main\nordic-dfu-main\blinky>

RE: Flashing code on I/O shield using nRF5340 DK board

Susheel Nuguru — Thu, 05 Sep 2024 06:32:22 GMT

try to recover the chip first. It seems like there is no communication happening with the chip and the debugger. Not sure what the issue is but try recovering two cores

nrfjprog --recover -f nrf53 --coprocessor CP_APPLICATION
nrfjprog --recover -f nrf53 --coprocessor CP_NETWORK

RE: Flashing code on I/O shield using nRF5340 DK board

akhil — Tue, 03 Sep 2024 07:45:10 GMT

Also, note that we are giving power to the I/O shield by the nRF5340 DK board only as suggested in the documentation.