About issue of Flash recovery for NAC1080 device

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
lock attach
Attachments are accessible only for community members.
u-s
Level 4
Level 4
Distributor - Macnica (Japan)
50 sign-ins 25 replies posted First like received

Hello everyone,

I am evaluating with DEV_KIT_NAC1080.
https://www.infineon.com/cms/jp/product/evaluation-boards/dev_kit_nac1080/

When I was debugging with Eclipse and SEGGER J-Link debugger, the following error occurred.
- Please refer to the attached document for detailed information.

This caused me to be unable to use J-Link debugger to access the NAC1080 device.
- Including writing programs to Flash and debugging the software.

Maybe I accidentally erased the Flash of NAC1080 device while using J-Flash to write programs.

Could you tell me how to restore the device to its original state?
- How to achieve flash recovery for NAC1080 device?

Best Regards
u-s

0 Likes
14 Replies
Ajeethkumar_P
Moderator
Moderator
Moderator
50 likes received 500 replies posted 100 solutions authored

Hello,

Please answer the following:
1. Which firmware example you are using?
2. Are you able to build the project without any issues?
3. Can you share the Jlink configuration settings?

Thanks,
Ajeeth

0 Likes
lock attach
Attachments are accessible only for community members.
u-s
Level 4
Level 4
Distributor - Macnica (Japan)
50 sign-ins 25 replies posted First like received

Hello, Ajeeth

Thank you for your respons!
Let me answer your questions.

>1. Which firmware example you are using?
I am using the "Infineon-Infineon_NAC1080_Firmware_Sample_Boost_Buck_Test_Firmware-Software-v01_00-EN" provided on Infineon website.
https://www.infineon.com/dgdl/Infineon-Infineon_NAC1080_Firmware_Sample_Boost_Buck_Test_Firmware-Sof...

 

>2. Are you able to build the project without any issues?
Yes, I created and compiled the program using "Eclipse IDE for Embedded C and C++ Developers - 2022-12" as per the instructions below.
https://www.infineon.com/dgdl/Infineon-NAC1080_software_development_guide-UserManual-v01_00-EN.pdf?f...

I can use SEGGER JLink to debug programs on DEV_KIT_NAC1080.
However, when I tried to write the "Infineon NFC Lock Showcase Firmware for NAC1080" software (lock_demo_v0-1-5-2_A21004_HW3-0.hex) provided by Infineon's website into DEV_KIT_NAC1080 using SEGGER J-Flash Lite V7.86d, the above problem occurred.
In this operation, I may have clicked the "Erase Chip" button.
About the screen of SEGGER J-Flash Lite V7.86d please refer to the attached file.

>3. Can you share the Jlink configuration settings?
Of course. About my 'Eclipse IDE' settings please refer to the attached file.

Best Regards
u-s

0 Likes
Ajeethkumar_P
Moderator
Moderator
Moderator
50 likes received 500 replies posted 100 solutions authored

Hi,

Did you update the JLinkDevices.xml file with the contents mentioned in the NAC1080 Software development guide?

Please ensure the "Loader" field is the proper path with the Image file name. 

Thanks,
Ajeeth

0 Likes
lock attach
Attachments are accessible only for community members.
u-s
Level 4
Level 4
Distributor - Macnica (Japan)
50 sign-ins 25 replies posted First like received

Hello, Ajeeth

Thank you for your respons!

Yes, I updated the JLinkDevices.xml file according to the NAC080 software development guide.

I still cannot use Eclipse IDE with SEGGER J-Flash to write firmware.

When using SEGGER J-Flash, I can find the NAC1080 device when creating a new project.
After generating the project, I was able to successfully read in the ".elf" and ".hex" files. However, when I tried to connect to the device using the "Connect" option under the "Target" menu, I encountered an error as shown in the attached file, which prevented me from connecting to the device.

When using Eclipse IDE, the error message 'Device 'NAC1080' Flash bank 0x0001 0000' No loader specified' appears. 

This prevents me from writing firmware.
I have attached the output information from the 'Console' in Eclipse IDE for your review.
=========================================================

SEGGER J-Link GDB Server V7.86d Command Line Version

JLinkARM.dll V7.86d (DLL compiled Mar 15 2023 13:56:30)

Command line: -if swd -device Cortex-M0 -endian little -speed 1000 -port 2331 -swoport 2332 -telnetport 2333 -vd -ir -localhostonly 1 -singlerun -strict -timeout 0 -nogui -device NAC1080 -ir -nosilent -halt -JLinkDevicesXMLPath ..\tool_config\jlink
-----GDB Server start settings-----
GDBInit file: none
GDB Server Listening port: 2331
SWO raw output listening port: 2332
Terminal I/O port: 2333
Accept remote connection: localhost only
Generate logfile: off
Verify download: on
Init regs on start: on
Silent mode: off
Single run mode: on
Target connection timeout: 0 ms
------J-Link related settings------
J-Link Host interface: USB
J-Link script: none
J-Link settings file: none
------Target related settings------
Target device: NAC1080
Target device parameters: none
Target interface: SWD
Target interface speed: 1000kHz
Target endian: little

Connecting to J-Link...
J-Link is connected.
Firmware: J-Link ARM V8 compiled Nov 28 2014 13:44:46
Hardware: V8.00
S/N: 58008567
Checking target voltage...
Target voltage: 2.50 V
Listening on TCP/IP port 2331
Connecting to target...
Halting core...
Initializing CPU registers...Connected to target
Waiting for GDB connection...Connected to 127.0.0.1
GDB client (conn. 1088) requested target.xml from GDB Server
Reading common registers: Read register 'r0' (4 bytes) from hardware: 0x00000000
Read register 'r1' (4 bytes) from hardware: 0x00000000
Read register 'r2' (4 bytes) from hardware: 0x00000000
Read register 'r3' (4 bytes) from hardware: 0x00000000
Read register 'r4' (4 bytes) from hardware: 0x00000000
Read register 'r5' (4 bytes) from hardware: 0x00000000
Read register 'r6' (4 bytes) from hardware: 0x00000000
Read register 'r7' (4 bytes) from hardware: 0x00000000
Read register 'r8' (4 bytes) from hardware: 0x00000000
Read register 'r9' (4 bytes) from hardware: 0x00000000
Read register 'r10' (4 bytes) from hardware: 0x00000000
Read register 'r11' (4 bytes) from hardware: 0x00000000
Read register 'r12' (4 bytes) from hardware: 0x00000000
Read register 'sp' (4 bytes) from hardware: 0x00000000
Read register 'lr' (4 bytes) from hardware: 0x00000000
Read register 'pc' (4 bytes) from hardware: 0x00000000
Read register 'xpsr' (4 bytes) from hardware: 0x00000001
WARNING: Failed to read memory @ address 0x00000000
Received monitor command: speed 1000
Target interface speed set to 1000 kHz
Received monitor command: clrbp
Received monitor command: reset
Resetting target
Received monitor command: halt
Halting target CPU...
...Target halted (PC = 0x0000264A)
Received monitor command: regs
R0 = 000445C0, R1 = 00000000, R2 = 00000007, R3 = E000E010
R4 = 00020750, R5 = 00020810, R6 = 00020814, R7 = 00020804
R8 = FFFFFFFF, R9 = FFFFFFFF, R10= FFFFFFFF, R11= FFFFFFFF
R12= 000206F0, R13= 00021FC8, MSP= 00021FC8, PSP= FFFFFFFC
R14(LR) = 000118A3, R15(PC) = 0000264A
XPSR 01000000, APSR 00000000, EPSR 01000000, IPSR 00000000
CFBP 00000000, CONTROL 00, FAULTMASK 00, BASEPRI 00, PRIMASK 00

Security extension regs:
MSP_S = 00000000, MSPLIM_S = 00000000
PSP_S = 00000000, PSPLIM_S = 00000000
MSP_NS = 00021FC8, MSPLIM_NS = 00000000
PSP_NS = FFFFFFFC, PSPLIM_NS = 00000000
CONTROL_S 00, FAULTMASK_S 00, BASEPRI_S 00, PRIMASK_S 00
CONTROL_NS 00, FAULTMASK_NS 00, BASEPRI_NS 00, PRIMASK_NS 00

Reading common registers: Read register 'r0' (4 bytes) from hardware: 0xC0450400
Read register 'r1' (4 bytes) from hardware: 0x00000000
Read register 'r2' (4 bytes) from hardware: 0x07000000
Read register 'r3' (4 bytes) from hardware: 0x10E000E0
Read register 'r4' (4 bytes) from hardware: 0x50070200
Read register 'r5' (4 bytes) from hardware: 0x10080200
Read register 'r6' (4 bytes) from hardware: 0x14080200
Read register 'r7' (4 bytes) from hardware: 0x04080200
Read register 'r8' (4 bytes) from hardware: 0xFFFFFFFF
Read register 'r9' (4 bytes) from hardware: 0xFFFFFFFF
Read register 'r10' (4 bytes) from hardware: 0xFFFFFFFF
Read register 'r11' (4 bytes) from hardware: 0xFFFFFFFF
Read register 'r12' (4 bytes) from hardware: 0xF0060200
Read register 'sp' (4 bytes) from hardware: 0xC81F0200
Read register 'lr' (4 bytes) from hardware: 0xA3180100
Read register 'pc' (4 bytes) from hardware: 0x4A260000
Read register 'xpsr' (4 bytes) from hardware: 0x00000001
Received monitor command: speed 1000
Target interface speed set to 1000 kHz
Received monitor command: flash breakpoints 0
Flash breakpoints disabled
Downloading 1024 bytes @ address 0x00010400 - Verified OK
Downloading 3414 bytes @ address 0x00010800 - Verified OK
Downloading 12 bytes @ address 0x00011560 - Verified OK
Downloading 8 bytes @ address 0x0001156C - Verified OK
Downloading 16364 bytes @ address 0x00011574 - Verified OK
Downloading 16368 bytes @ address 0x00015560 - Verified OK
Downloading 16368 bytes @ address 0x00019550 - Verified OK
Downloading 6836 bytes @ address 0x0001D540 - Verified OK
Downloading 12 bytes @ address 0x0001EFF4 - Verified OK
Writing register 'pc' = 0x00010B80
Comparing flash [....................] Done.
ERROR: PC of target system has unexpected value after preparing target. (PC = 0x00000000)!
---------------------------------------------------------------------- Registers -------------------------------------------------------------------------------------
PC = 00000000
Current: R0 = 00000000, R1 = 00000000, R2 = 00000000, R3 = 00000000
R4 = 00000000, R5 = 00000000, R6 = 00000000, R7 = 00000000
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Failed to perform RAMCode-sided Prepare()
Cannot read register 15 (R15) while CPU is runningCannot read register 7 (R7) while CPU is runningCannot read register 6 (R6) while CPU is runningCannot read register 5 (R5) while CPU is runningCannot read register 4 (R4) while CPU is runningCannot read register 3 (R3) while CPU is runningCannot read register 2 (R2) while CPU is runningCannot read register 1 (R1) while CPU is runningC
WARNING: Failed to read memory @ address 0x00010B80
WARNING: Failed to read memory @ address 0x00010960
WARNING: Failed to read memory @ address 0x000118A2
WARNING: Failed to read memory @ address 0x000118A2
Received monitor command: clrbp
Received monitor command: reset
Resetting target
Received monitor command: halt
Halting target CPU...
...Target halted (PC = 0x0000264A)
Read 2 bytes @ address 0x00010960 (Data = 0x2300)
Received monitor command: regs
R0 = 000445C0, R1 = 00000000, R2 = 00000007, R3 = E000E010
R4 = 00020750, R5 = 00020810, R6 = 00020814, R7 = 00020804
R8 = FFFFFFFF, R9 = FFFFFFFF, R10= FFFFFFFF, R11= FFFFFFFF
R12= 000206F0, R13= 00021FC8, MSP= 00021FC8, PSP= FFFFFFFC
R14(LR) = 000118A3, R15(PC) = 0000264A
XPSR 01000000, APSR 00000000, EPSR 01000000, IPSR 00000000
CFBP 00000000, CONTROL 00, FAULTMASK 00, BASEPRI 00, PRIMASK 00

Security extension regs:
MSP_S = 00000000, MSPLIM_S = 00000000
PSP_S = 00000000, PSPLIM_S = 00000000
MSP_NS = 00021FC8, MSPLIM_NS = 00000000
PSP_NS = FFFFFFFC, PSPLIM_NS = 00000000
CONTROL_S 00, FAULTMASK_S 00, BASEPRI_S 00, PRIMASK_S 00
CONTROL_NS 00, FAULTMASK_NS 00, BASEPRI_NS 00, PRIMASK_NS 00

Reading common registers: Read register 'r0' (4 bytes) from hardware: 0xC0450400
Read register 'r1' (4 bytes) from hardware: 0x00000000
Read register 'r2' (4 bytes) from hardware: 0x07000000
Read register 'r3' (4 bytes) from hardware: 0x10E000E0
Read register 'r4' (4 bytes) from hardware: 0x50070200
Read register 'r5' (4 bytes) from hardware: 0x10080200
Read register 'r6' (4 bytes) from hardware: 0x14080200
Read register 'r7' (4 bytes) from hardware: 0x04080200
Read register 'r8' (4 bytes) from hardware: 0xFFFFFFFF
Read register 'r9' (4 bytes) from hardware: 0xFFFFFFFF
Read register 'r10' (4 bytes) from hardware: 0xFFFFFFFF
Read register 'r11' (4 bytes) from hardware: 0xFFFFFFFF
Read register 'r12' (4 bytes) from hardware: 0xF0060200
Read register 'sp' (4 bytes) from hardware: 0xC81F0200
Read register 'lr' (4 bytes) from hardware: 0xA3180100
Read register 'pc' (4 bytes) from hardware: 0x4A260000
Read register 'xpsr' (4 bytes) from hardware: 0x00000001
Read 4 bytes @ address 0x0000264A (Data = 0x601A3A03)
Read 2 bytes @ address 0x0000264A (Data = 0x3A03)
WARNING: Failed to read memory @ address 0x000118A2
WARNING: Failed to read memory @ address 0x000118A2

=========================================================

Can you tell me how to recover the device?

Best Regards
u-s

0 Likes
Ajeethkumar_P
Moderator
Moderator
Moderator
50 likes received 500 replies posted 100 solutions authored

Hi,

In the device entries, there is an item Loader that specifies an ELF file that acts as a driver for the Flash memory inside the device. Copy the ELF files listed for the NAC1080 (e.g., image_ram.elf) from the SDK directory tool_config\jlink to the proper path, e.g., the location of the JLinkDevices.xml file.

Did you do the above step as mentioned in the NAC1080 Software development Guide?

Thanks,
Ajeeth

0 Likes
u-s
Level 4
Level 4
Distributor - Macnica (Japan)
50 sign-ins 25 replies posted First like received

Hello, Ajeeth

Thank you for your respons!
The above result is what I obtained by following the software development guide.
I have copied imageram.elf to the [tool_config\jlink] directory under the SDK, and also imported the JLinkDevices.xml file into SEGGER's installation directory.

Best Regards
u-s

 

0 Likes
Ajeethkumar_P
Moderator
Moderator
Moderator
50 likes received 500 replies posted 100 solutions authored

Hi,

Can you try to download the original file from the website to program the IC(rather than copying the image_ram.elf from your project) to return to the initial state?

Thanks,
Ajeeth

0 Likes
u-s
Level 4
Level 4
Distributor - Macnica (Japan)
50 sign-ins 25 replies posted First like received

Hello, Ajeeth

Thank you for your respons!
Sorry for the tardy response.
I downloaded the original sample code 'Firmware sample - Stand-alone motor control' from the URL below.
https://www.infineon.com/dgdl/Infineon-Firmware_sample_Stand_alone_motor_control-Software-v01_00-EN....

Then I imported this sample into Eclipse for compilation, generating an 'image_ram.elf' file.
I attempted to use SEGGER to write this file into NAC1080.
However obtained the same result as before, I can not restore my evaluation board.

Can you tell me where to download the original file? And how to write the 'image_ram.elf' file into the IC?
For example using Eclipse...

Best Regards
u-s

0 Likes
lock attach
Attachments are accessible only for community members.
Ajeethkumar_P
Moderator
Moderator
Moderator
50 likes received 500 replies posted 100 solutions authored

Hi,

I am attaching the smack_sl project launch configuration here. Please use the same and let me know if you can load the flash contents.

Steps to follow to set up the NAC1080 project debugging:
1. Import the smack_sl project into Eclipse(Don't copy project into workspace)
2. Make sure smack_lib, smack_rom, tool_config and tools folders available to paralllel to smack_sl folder.
3. Build the smack_sl project. For more details refer to, section 3.1 of the NAC1080 Software Development guide
4. Make sure to power EVAL_NAC1080 in active mode. i.e., Connect 3.3 V for VCC and 3V3 in J18 and J18 respectively
5. Import the Launch configurations attached. If you want to create your configurations, please go through Section 4.2.2 of the NAC1080 Software development guide. Please update all the configurations including other options in the debugger tab, GDB Client setup Executable name, Set breakpoint in the startup tab, etc.
6. Click on Apply and then debug.

For the Command line, please refer to section 4.2.4 of the NAC1080 Software development guide.

Thanks,
Ajeeth

0 Likes
u-s
Level 4
Level 4
Distributor - Macnica (Japan)
50 sign-ins 25 replies posted First like received

Hello, Ajeeth

Thank you for your respons.
I have used the configuration file that you shared with me and followed your instructions.
However, I still haven't been able to restore the board to its initial state.
Below is the log from my Eclipse output. Please confirm it.
=================================================================
SEGGER J-Link GDB Server V7.86d Command Line Version

JLinkARM.dll V7.86d (DLL compiled Mar 15 2023 13:56:30)

Command line: -if swd -device Cortex-M0 -endian little -speed 1000 -port 2331 -swoport 2332 -telnetport 2333 -vd -ir -localhostonly 1 -singlerun -strict -timeout 10000 -nogui -device NAC1080 -ir -nosilent -halt -JLinkDevicesXMLPath ..\tool_config\jlink
-----GDB Server start settings-----
GDBInit file: none
GDB Server Listening port: 2331
SWO raw output listening port: 2332
Terminal I/O port: 2333
Accept remote connection: localhost only
Generate logfile: off
Verify download: on
Init regs on start: on
Silent mode: off
Single run mode: on
Target connection timeout: 10000 ms
------J-Link related settings------
J-Link Host interface: USB
J-Link script: none
J-Link settings file: none
------Target related settings------
Target device: NAC1080
Target device parameters: none
Target interface: SWD
Target interface speed: 1000kHz
Target endian: little

Connecting to J-Link...
J-Link is connected.
Firmware: J-Link ARM V8 compiled Nov 28 2014 13:44:46
Hardware: V8.00
S/N: 58008567
Checking target voltage...
Target voltage: 2.36 V
Listening on TCP/IP port 2331
Connecting to target...
Halting core...
Initializing CPU registers...Connected to target
Waiting for GDB connection...Connected to 127.0.0.1
GDB client (conn. 1084) requested target.xml from GDB Server
Reading common registers: Read register 'r0' (4 bytes) from hardware: 0x00000000
Read register 'r1' (4 bytes) from hardware: 0x00000000
Read register 'r2' (4 bytes) from hardware: 0x00000000
Read register 'r3' (4 bytes) from hardware: 0x00000000
Read register 'r4' (4 bytes) from hardware: 0x00000000
Read register 'r5' (4 bytes) from hardware: 0x00000000
Read register 'r6' (4 bytes) from hardware: 0x00000000
Read register 'r7' (4 bytes) from hardware: 0x00000000
Read register 'r8' (4 bytes) from hardware: 0x00000000
Read register 'r9' (4 bytes) from hardware: 0x00000000
Read register 'r10' (4 bytes) from hardware: 0x00000000
Read register 'r11' (4 bytes) from hardware: 0x00000000
Read register 'r12' (4 bytes) from hardware: 0x00000000
Read register 'sp' (4 bytes) from hardware: 0x00000000
Read register 'lr' (4 bytes) from hardware: 0x00000000
Read register 'pc' (4 bytes) from hardware: 0x00000000
Read register 'xpsr' (4 bytes) from hardware: 0x00000001
WARNING: Failed to read memory @ address 0x00000000
Received monitor command: speed 1000
Target interface speed set to 1000 kHz
Received monitor command: clrbp
Received monitor command: reset
Resetting target
Received monitor command: halt
Halting target CPU...
...Target halted (PC = 0x0000264A)
Received monitor command: regs
R0 = 000445C0, R1 = 00000000, R2 = 00000007, R3 = E000E010
R4 = 00020750, R5 = 00020810, R6 = 00020814, R7 = 00020804
R8 = FFFFFFFF, R9 = FFFFFFFF, R10= FFFFFFFF, R11= FFFFFFFF
R12= 000206F0, R13= 00021FC8, MSP= 00021FC8, PSP= FFFFFFFC
R14(LR) = 000118A3, R15(PC) = 0000264A
XPSR 01000000, APSR 00000000, EPSR 01000000, IPSR 00000000
CFBP 00000000, CONTROL 00, FAULTMASK 00, BASEPRI 00, PRIMASK 00

Security extension regs:
MSP_S = 00000000, MSPLIM_S = 00000000
PSP_S = 00000000, PSPLIM_S = 00000000
MSP_NS = 00021FC8, MSPLIM_NS = 00000000
PSP_NS = FFFFFFFC, PSPLIM_NS = 00000000
CONTROL_S 00, FAULTMASK_S 00, BASEPRI_S 00, PRIMASK_S 00
CONTROL_NS 00, FAULTMASK_NS 00, BASEPRI_NS 00, PRIMASK_NS 00

Reading common registers: Read register 'r0' (4 bytes) from hardware: 0xC0450400
Read register 'r1' (4 bytes) from hardware: 0x00000000
Read register 'r2' (4 bytes) from hardware: 0x07000000
Read register 'r3' (4 bytes) from hardware: 0x10E000E0
Read register 'r4' (4 bytes) from hardware: 0x50070200
Read register 'r5' (4 bytes) from hardware: 0x10080200
Read register 'r6' (4 bytes) from hardware: 0x14080200
Read register 'r7' (4 bytes) from hardware: 0x04080200
Read register 'r8' (4 bytes) from hardware: 0xFFFFFFFF
Read register 'r9' (4 bytes) from hardware: 0xFFFFFFFF
Read register 'r10' (4 bytes) from hardware: 0xFFFFFFFF
Read register 'r11' (4 bytes) from hardware: 0xFFFFFFFF
Read register 'r12' (4 bytes) from hardware: 0xF0060200
Read register 'sp' (4 bytes) from hardware: 0xC81F0200
Read register 'lr' (4 bytes) from hardware: 0xA3180100
Read register 'pc' (4 bytes) from hardware: 0x4A260000
Read register 'xpsr' (4 bytes) from hardware: 0x00000001
Received monitor command: speed 1000
Target interface speed set to 1000 kHz
Received monitor command: flash breakpoints 0
Flash breakpoints disabled
Downloading 1024 bytes @ address 0x00010400 - Verified OK
Downloading 3320 bytes @ address 0x00010800 - Verified OK
Downloading 12 bytes @ address 0x00011500 - Verified OK
Downloading 8 bytes @ address 0x0001150C - Verified OK
Downloading 16364 bytes @ address 0x00011514 - Verified OK
Downloading 16368 bytes @ address 0x00015500 - Verified OK
Downloading 16368 bytes @ address 0x000194F0 - Verified OK
Downloading 6932 bytes @ address 0x0001D4E0 - Verified OK
Downloading 12 bytes @ address 0x0001EFF4 - Verified OK
Writing register 'pc' = 0x00010A64
ERROR: Failed to preserve target RAM @ 0x00020800-0x00020FFF.
Failed to prepare for programming.
WARNING: Failed to read memory @ address 0x00010A64
WARNING: Failed to read memory @ address 0x00010960
Received monitor command: clrbp
Received monitor command: reset
Resetting target
Received monitor command: halt
Halting target CPU...
...Target halted (PC = 0x0000264A)
Read 2 bytes @ address 0x00010960 (Data = 0x2300)
Received monitor command: regs
R0 = 000445C0, R1 = 00000000, R2 = 00000007, R3 = E000E010
R4 = 00020750, R5 = 00020810, R6 = 00020814, R7 = 00020804
R8 = FFFFFFFF, R9 = FFFFFFFF, R10= FFFFFFFF, R11= FFFFFFFF
R12= 000206F0, R13= 00021FC8, MSP= 00021FC8, PSP= FFFFFFFC
R14(LR) = 000118A3, R15(PC) = 0000264A
XPSR 01000000, APSR 00000000, EPSR 01000000, IPSR 00000000
CFBP 00000000, CONTROL 00, FAULTMASK 00, BASEPRI 00, PRIMASK 00

Security extension regs:
MSP_S = 00000000, MSPLIM_S = 00000000
PSP_S = 00000000, PSPLIM_S = 00000000
MSP_NS = 00021FC8, MSPLIM_NS = 00000000
PSP_NS = FFFFFFFC, PSPLIM_NS = 00000000
CONTROL_S 00, FAULTMASK_S 00, BASEPRI_S 00, PRIMASK_S 00
CONTROL_NS 00, FAULTMASK_NS 00, BASEPRI_NS 00, PRIMASK_NS 00

Reading common registers: Read register 'r0' (4 bytes) from hardware: 0xC0450400
Read register 'r1' (4 bytes) from hardware: 0x00000000
Read register 'r2' (4 bytes) from hardware: 0x07000000
Read register 'r3' (4 bytes) from hardware: 0x10E000E0
Read register 'r4' (4 bytes) from hardware: 0x50070200
Read register 'r5' (4 bytes) from hardware: 0x10080200
Read register 'r6' (4 bytes) from hardware: 0x14080200
Read register 'r7' (4 bytes) from hardware: 0x04080200
Read register 'r8' (4 bytes) from hardware: 0xFFFFFFFF
Read register 'r9' (4 bytes) from hardware: 0xFFFFFFFF
Read register 'r10' (4 bytes) from hardware: 0xFFFFFFFF
Read register 'r11' (4 bytes) from hardware: 0xFFFFFFFF
Read register 'r12' (4 bytes) from hardware: 0xF0060200
Read register 'sp' (4 bytes) from hardware: 0xC81F0200
Read register 'lr' (4 bytes) from hardware: 0xA3180100
Read register 'pc' (4 bytes) from hardware: 0x4A260000
Read register 'xpsr' (4 bytes) from hardware: 0x00000001
Read 4 bytes @ address 0x0000264A (Data = 0x601A3A03)
Read 2 bytes @ address 0x0000264A (Data = 0x3A03)
=================================================================

Best Regards
u-s

0 Likes
Ajeethkumar_P
Moderator
Moderator
Moderator
50 likes received 500 replies posted 100 solutions authored

Hi,

From the above log, downloading the NVM image seems to be successful according to the "Downloading" lines just above the error message.
However, there are two or three things you may check:
1. In your message from April 5th, you mentioned a file "image_ram.elf", however, the built file should be named "image_nvm.elf". The command line to build this is "make all", the build target in Eclipse shall be set to "all" (see figures 6 and 7 in the SDK guide).
2. The J-Link reports a target voltage of 2.36V, this should be around 2.5V. Probably the power supply to the NAC1080 or the debugger part is a bit low.
3. Change the Debugger and test
4. Check the connections

Background to the RAM area: The flash driver is provided by us (tool_config\jlink\image_ram.elf), the memory range where to load it to is given in tool_config\jlink\JLinkDevices.xml and cannot be changed.

Thanks,
Ajeeth

0 Likes
lock attach
Attachments are accessible only for community members.
u-s
Level 4
Level 4
Distributor - Macnica (Japan)
50 sign-ins 25 replies posted First like received

Hello, Ajeeth

Thank you for your respons!
Sorry for the tardy response.

According to your response, I adjusted the debugger, I can confim that target voltage to be 2.49V.
However, I still cannot restore my device.
Please refer to the Log file in the attachment for details.

In the log file, I confirm the following Warnings and Errors.
line 59 -> WARNING: Failed to read memory @ address 0x00000000
line 116 -> ERROR: Failed to preserve target RAM @ 0x00020800-0x00020FFF.
line 117 -> Failed to prepare for programming.
line 118 -> WARNING: Failed to read memory @ address 0x00010A64
line 119 -> WARNING: Failed to read memory @ address 0x00010960
line 167 -> WARNING: Target connection lost.

Can you tell me if the issue of being unable to restore the device is related to the above warnings and errors?
If so, can you please tell me how to resolve these issues?

Best Regards
u-s

0 Likes
Ajeethkumar_P
Moderator
Moderator
Moderator
50 likes received 500 replies posted 100 solutions authored

Hi,

Can you create a Techsupport case at mycases.infineon.com regarding this issue?

Thanks,
Ajeeth

0 Likes
u-s
Level 4
Level 4
Distributor - Macnica (Japan)
50 sign-ins 25 replies posted First like received

Hi, Ajeeth

Thank you for your answer.
I will create a techsupport case.
Please close this thread.

Best Regards
u-s

0 Likes