MIMXRT1176 flashing usink linkserver CLI

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

MIMXRT1176 flashing usink linkserver CLI

Jump to solution
860 Views
yosri_c
Contributor III

hello NXP support ,

 

i'm trying to flash a binary into my board using linkserver CLI , now i use the set of commands to start the script C:\nxp\LinkServer_24.12.21\LinkServer.exe flash MIMXRT1176:cm7 load combined_RAW_image_from_json.bin:0x60000000 

what i'm missing is command so i can choose the MIMXRT1170_FlexSPI2_A_SFDP_QSPI.cfx driver since my flash nor is on Flexspi2 addr 0x60000000 ? 

this is cmd output 

INFO: Selected device MIMXRT1176xxxxx:MIMXRT1170-EVK-CM7-ONLY
INFO: Getting available probes
INFO: Selected probe #1 RY31WJHEEL5MQ (MCU-LINK r0FF CMSIS-DAP V0.078)
INFO: MCU-Link firmware update `check`: Probe ([RY31WJHEEL5MQ] [MCU-LINK r0FF CMSIS-DAP V0.078]) is running a firmware version which is older than the included firmware version [3.153]
Firmware update `check`: recommended - auto update can be performed using: `LinkServer probe #1 update auto`
Ns: LinkServer RedlinkMulti Driver v24.12 (Dec 18 2024 18:34:07 - crt_emu_cm_redlink.exe build 869)
Pc: ( 0) Reading remote configuration
Wc(03). No cache support.
Nc: Found generic directory XML file in C:\Users\YOSRI~1.CHE\AppData\Local\Temp\tmpcuef68sz\crt_directory.xml
Pc: ( 5) Remote configuration complete
Nc: Reconnected to existing LinkServer process.
Wc: ============= SCRIPT: RT1170_connect_M7.scp =============
Wc: RT1170 Connect M7 Script
Wc: DpID = 6BA02477
Wc: APID = 0x84770001
Wc: View cores on the DAP AP
Wc: TAP 0: 6BA02477 Core 0: M7 APID: 84770001 ROM Table: E00FD003*
Wc: TAP 0: 6BA02477 Core 1: M4 APID: 24770011 ROM Table: E00FF003
Wc: ============= END SCRIPT ================================
Nc: Probe Firmware: MCU-LINK r0FF CMSIS-DAP V0.078 (NXP Semiconductors)
Nc: Serial Number: RY31WJHEEL5MQ
Nc: VID:PID: 1FC9:0143
Nc: USB Path: \\?\hid#vid_1fc9&pid_0143&mi_00#7&5c67af8&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Nc: Using memory from core 0 after searching for a good core
Pc: ( 30) Emulator Connected
Pc: ( 40) Debug Halt
Pc: ( 50) CPU ID
Nc: debug interface type = CoreSight DP (DAP DP ID 6BA02477) over SWD TAP 0
Nc: processor type = Cortex-M7 (CPU ID 00000C27) on DAP AP 0
Nc: number of h/w breakpoints = 8
Nc: number of flash patches = 0
Nc: number of h/w watchpoints = 4
Nc: Probe(0): Connected&Reset. DpID: 6BA02477. CpuID: 00000C27. Info: <None>
Nc: Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.
Ns: Content of CoreSight Debug ROM(s):
Nc: RBASE E00FD000: CID B105100D PID 000008E88C ROM (type 0x1)
Nc: ROM 1 E00FE000: CID B105100D PID 04000BB4C8 ROM (type 0x1)
Nc: ROM 2 E00FF000: CID B105100D PID 04000BB4C7 ROM (type 0x1)
Nc: ROM 3 E000E000: CID B105E00D PID 04000BB00C Gen SCS (type 0x0)
Nc: ROM 3 E0001000: CID B105E00D PID 04000BB002 Gen DWT (type 0x0)
Nc: ROM 3 E0002000: CID B105E00D PID 04000BB00E Gen (type 0x0)
Nc: ROM 3 E0000000: CID B105E00D PID 04000BB001 Gen ITM (type 0x0)
Nc: ROM 2 E0041000: CID B105900D PID 04001BB975 CSt ARM ETMv4.0 type 0x13 Trace Source - Core
Nc: ROM 2 E0042000: CID B105900D PID 04004BB906 CSt type 0x14 Debug Control - Trigger, e.g. ECT
Nc: ROM 1 E0043000: CID B105900D PID 04001BB908 CSt CSTF type 0x12 Trace Link - Trace funnel/router
Nc: NXP: MIMXRT1176xxxxx
Nc: DAP stride is 1024 bytes (256 words)
Nc: Inspected v.2 External Flash Device on SPI using SFDP JEDEC ID MIMXRT1170_SFDP_QSPI.cfx
Nc: Image 'iMXRT1170_SFDP_FlexSPI1_A_QSPI Dec 18 2024 17:31:20'
Nc: Opening flash driver MIMXRT1170_SFDP_QSPI.cfx
Nc: Sending VECTRESET to run flash driver
Ec: Flash Driver V.2 dynamic startup failed - driver Init provided no flash parameters

Nc: Flash Driver V.2 startup failed - rc Ef(55): Dynamic flash driver startup failed to provide flash parameters.
Ec: op Terminate (0x0, 0x0, 0x0) status 0x40 - driver reports init failure - EXTSPIJ driver rc 20107 (0x4E8B)

Ec: vendor chip initialization failed - Ef(55): Dynamic flash driver startup failed to provide flash parameters.
Wc: failed to initialize flash driver MIMXRT1170_SFDP_QSPI.cfx
Pc: ( 65) Chip Setup Complete
Pc: (100) Target Operation Failed

 

 

0 Kudos
Reply
1 Solution
841 Views
diego_charles
NXP TechSupport
NXP TechSupport

Hi @yosri_c 

Could you try to modify the .json for the MCU?

diego_charles_0-1747935593021.png

diego_charles_1-1747935611469.png

I took the idea from this Erich Styger's post 

https://mcuoneclipse.com/2023/07/30/using-legacy-devices-with-linkserver/

Or you could create your own device.

Please let me know your results. 

Diego

 

View solution in original post

0 Kudos
Reply
5 Replies
822 Views
yosri_c
Contributor III

hi diego , 

Thanks for the response , how do i specify the JSON file in the script because i tried that Modification and it still defaults ! is there a command i put to use json or it's by default ?

0 Kudos
Reply
843 Views
yosri_c
Contributor III

i then tried with -o , this time i was able to change the flash driver but then it defaults to   MIMXRT1170_SFDP_QSPI.cfx

i'm missing something else i  presume ?

 

C:\nxp\LinkServer_24.12.21>LinkServer.exe flash --override "/device/memory/0/flash-driver=MIMXRT1170_FlexSPI2_A_SFDP_QSPI.cfx" MIMXRT1176:cm7 load combined_RAW_image_from_json.bin:0x60000000
INFO: Selected device MIMXRT1176xxxxx:MIMXRT1170-EVK-CM7-ONLY
INFO: Getting available probes
INFO: Selected probe #1 RY31WJHEEL5MQ (MCU-LINK r0FF CMSIS-DAP V0.078)
INFO: MCU-Link firmware update `check`: Probe ([RY31WJHEEL5MQ] [MCU-LINK r0FF CMSIS-DAP V0.078]) is running a firmware version which is older than the included firmware version [3.153]
Firmware update `check`: recommended - auto update can be performed using: `LinkServer probe #1 update auto`
Ns: LinkServer RedlinkMulti Driver v24.12 (Dec 18 2024 18:34:07 - crt_emu_cm_redlink.exe build 869)
Pc: ( 0) Reading remote configuration
Wc(03). No cache support.
Nc: Found generic directory XML file in C:\Users\YOSRI~1.CHE\AppData\Local\Temp\tmpl6648hjr\crt_directory.xml
Pc: ( 5) Remote configuration complete
Nc: Reconnected to existing LinkServer process.
Wc: ============= SCRIPT: RT1170_connect_M7.scp =============
Wc: RT1170 Connect M7 Script
Wc: DpID = 6BA02477
Wc: APID = 0x84770001
Wc: View cores on the DAP AP
Wc: TAP 0: 6BA02477 Core 0: M7 APID: 84770001 ROM Table: E00FD003*
Wc: TAP 0: 6BA02477 Core 1: M4 APID: 24770011 ROM Table: E00FF003
Wc: ============= END SCRIPT ================================
Nc: Probe Firmware: MCU-LINK r0FF CMSIS-DAP V0.078 (NXP Semiconductors)
Nc: Serial Number: RY31WJHEEL5MQ
Nc: VID:PID: 1FC9:0143
Nc: USB Path: \\?\hid#vid_1fc9&pid_0143&mi_00#7&5c67af8&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Nc: Using memory from core 0 after searching for a good core
Pc: ( 30) Emulator Connected
Pc: ( 40) Debug Halt
Pc: ( 50) CPU ID
Nc: debug interface type = CoreSight DP (DAP DP ID 6BA02477) over SWD TAP 0
Nc: processor type = Cortex-M7 (CPU ID 00000C27) on DAP AP 0
Nc: number of h/w breakpoints = 8
Nc: number of flash patches = 0
Nc: number of h/w watchpoints = 4
Nc: Probe(0): Connected&Reset. DpID: 6BA02477. CpuID: 00000C27. Info: <None>
Nc: Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.
Ns: Content of CoreSight Debug ROM(s):
Nc: RBASE E00FD000: CID B105100D PID 000008E88C ROM (type 0x1)
Nc: ROM 1 E00FE000: CID B105100D PID 04000BB4C8 ROM (type 0x1)
Nc: ROM 2 E00FF000: CID B105100D PID 04000BB4C7 ROM (type 0x1)
Nc: ROM 3 E000E000: CID B105E00D PID 04000BB00C Gen SCS (type 0x0)
Nc: ROM 3 E0001000: CID B105E00D PID 04000BB002 Gen DWT (type 0x0)
Nc: ROM 3 E0002000: CID B105E00D PID 04000BB00E Gen (type 0x0)
Nc: ROM 3 E0000000: CID B105E00D PID 04000BB001 Gen ITM (type 0x0)
Nc: ROM 2 E0041000: CID B105900D PID 04001BB975 CSt ARM ETMv4.0 type 0x13 Trace Source - Core
Nc: ROM 2 E0042000: CID B105900D PID 04004BB906 CSt type 0x14 Debug Control - Trigger, e.g. ECT
Nc: ROM 1 E0043000: CID B105900D PID 04001BB908 CSt CSTF type 0x12 Trace Link - Trace funnel/router
Nc: NXP: MIMXRT1176xxxxx
Nc: DAP stride is 1024 bytes (256 words)
Nc: Inspected v.2 External Flash Device on SPI using SFDP JEDEC ID MIMXRT1170_FlexSPI2_A_SFDP_QSPI.cfx
Nc: Image 'iMXRT1170_SFDP_FlexSPI2_A_QSPI Dec 18 2024 17:31:09'
Nc: Opening flash driver MIMXRT1170_FlexSPI2_A_SFDP_QSPI.cfx
Nc: Sending VECTRESET to run flash driver
Nc: Flash variant 'iMXRT1170_SFDP_FlexSPI2_A_QSPI Dec 18 2024 17:31:09' detected (16MB = 256*64K at 0x60000000)
Nc: Closing flash driver MIMXRT1170_FlexSPI2_A_SFDP_QSPI.cfx
Nc: Inspected v.2 External Flash Device on SPI using SFDP JEDEC ID MIMXRT1170_SFDP_QSPI.cfx
Nc: Image 'iMXRT1170_SFDP_FlexSPI1_A_QSPI Dec 18 2024 17:31:20'
Nc: Opening flash driver MIMXRT1170_SFDP_QSPI.cfx
Nc: Sending VECTRESET to run flash driver
Ec: Flash Driver V.2 dynamic startup failed - driver Init provided no flash parameters

Nc: Flash Driver V.2 startup failed - rc Ef(55): Dynamic flash driver startup failed to provide flash parameters.
Ec: op Terminate (0x0, 0x0, 0x0) status 0x40 - driver reports init failure - EXTSPIJ driver rc 20107 (0x4E8B)

Ec: vendor chip initialization failed - Ef(55): Dynamic flash driver startup failed to provide flash parameters.
Wc: failed to initialize flash driver MIMXRT1170_SFDP_QSPI.cfx
Pc: ( 65) Chip Setup Complete
Pc: (100) Target Operation Failed
CRITICAL: Critical error
ERRMSG: Exception: Flash operation exited with code 1

0 Kudos
Reply
842 Views
diego_charles
NXP TechSupport
NXP TechSupport

Hi @yosri_c 

Could you try to modify the .json for the MCU?

diego_charles_0-1747935593021.png

diego_charles_1-1747935611469.png

I took the idea from this Erich Styger's post 

https://mcuoneclipse.com/2023/07/30/using-legacy-devices-with-linkserver/

Or you could create your own device.

Please let me know your results. 

Diego

 

0 Kudos
Reply
649 Views
yosri_c
Contributor III
Thank you diago for your support .
apologies for the late reply . it's flashing after i created my own json and removed the override option
0 Kudos
Reply
648 Views
diego_charles
NXP TechSupport
NXP TechSupport

Hi @yosri_c 

No worries at all,  thank you for letting me know the outcome! 

Diego

0 Kudos
Reply