Problem flashing FRDM-MCXC242 with LinkServer (zephyr: west flash)

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

Problem flashing FRDM-MCXC242 with LinkServer (zephyr: west flash)

Jump to solution
3,674 Views
mw6
Contributor I

Hi,

I'm currently evaluating Zephyr on the FRDM-MCXC242 board.

When I tried flashing with west flash for the first time (using LinkServer) it worked. When trying to flash for a second time, west flash fails.

I can recover the board by flashing with a JLink probe (west flash -r jlink). Then flashing with LinkServer works again for the first try but at the second try it starts to fail again.

This is my output for the first try:

 

$ west -v flash
-- west flash: rebuilding
cmake version 3.30.5 is OK; minimum version is 3.13.1
Running CMake: 'C:\Program Files\CMake\bin\cmake.EXE' --build ##############################build'
ninja: no work to do.
-- west flash: using runner linkserver
runners.linkserver: 'C:\nxp\LinkServer_24.9.75\Linkserver.exe' -v
-- runners.linkserver: LinkServer: C:\nxp\LinkServer_24.9.75\Linkserver.exe, version v24.9.75
runners.linkserver: LinkServer cmd:  + ['C:\\nxp\\LinkServer_24.9.75\\Linkserver.exe', 'flash', '--probe', '#1', 'MCXC242:FRDM-MCXC242']
runners.linkserver: 'C:\nxp\LinkServer_24.9.75\Linkserver.exe' -v
runners.linkserver: flash command = ['C:\\nxp\\LinkServer_24.9.75\\Linkserver.exe', 'flash', '--probe', '#1', 'MCXC242:FRDM-MCXC242', 'load', '--addr', '0', '##############################\\zephyr.bin']
runners.linkserver: 'C:\nxp\LinkServer_24.9.75\Linkserver.exe' flash --probe '#1' MCXC242:FRDM-MCXC242 load --addr 0 '##############################\zephyr.bin'
INFO: Exact match for MCXC242:FRDM-MCXC242 found
INFO: Selected device MCXC242:FRDM-MCXC242
INFO: Getting available probes
INFO: Selecting probe by index
INFO: Selected probe #1 RJ5F0KUBKS14M (MCU-LINK FRDM-MCXC242 (r0E7) CMSIS-DAP V3.146)
INFO: MCU-Link firmware update `check`: local firmware [3.148] can be programmed on the selected probe ([RJ5F0KUBKS14M] [MCU-LINK FRDM-MCXC242 (r0E7) CMSIS-DAP V3.146])
Firmware update `check`: - the update can be performed using `auto` mode
Ns: MCUXpresso IDE RedlinkMulti Driver v24.9 (Sep 19 2024 19:34:05 - crt_emu_cm_redlink.exe build 802)
Pc: (  0) Reading remote configuration
Wc(03). No cache support.
Nc: Found generic directory XML file in ##############################\crt_directory.xml
Pc: (  5) Remote configuration complete
Nc: Reconnected to existing LinkServer process.
Wc: ============= SCRIPT: MCXC_connect.scp =============
Wc: MCXC Connect Script
Wc: Connecting to Probe Index = 1
Wc: This probe = 1
Wc: This TAP = 0
Wc: This core = 0
Wc: DpID = 0BC11477
Wc: Assert NRESET
Wc: Reset pin state: 00
Wc: Power up Debug
Wc: MDM-AP APID: 0x001C0020
Wc: MDM-AP System Reset/Hold Reset/Debug Request
Wc: MDM-AP Control: 0x0000001C
Wc: MDM-AP Status (Flash Ready) : 0x00000033
Wc: Part is not secured
Wc: MDM-AP Control: 0x00000014
Wc: Release NRESET
Wc: Reset pin state: 01
Wc: MDM-AP Control (Debug Request): 0x00000004
Wc: MDM-AP Status: 0x0001003B
Wc: MDM-AP Core Halted
Wc: ============= END SCRIPT ===========================
Nc: Probe Firmware: MCU-LINK FRDM-MCXC242 (r0E7) CMSIS-DAP V3.146 (NXP Semiconductors)
Nc: Serial Number:  RJ5F0KUBKS14M
Nc: VID:PID:  1FC9:0143
Nc: USB Path: 0001:0005:00
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 0BC11477) over SWD TAP 0
Nc: processor type            = Cortex-M0+ (CPU ID 00000C60) on DAP AP 0
Nc: number of h/w breakpoints = 2
Nc: number of flash patches   = 0
Nc: number of h/w watchpoints = 2
Nc: Probe(0): Connected&Reset. DpID: 0BC11477. CpuID: 00000C60. Info: <None>
Nc: Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.
Ns: Content of CoreSight Debug ROM(s):
Nc: RBASE F0002000: CID B105100D PID 000008E000 ROM (type 0x1)
Nc: ROM 1 F0000000: CID B105900D PID 04001BB932 CSt ARM MTB type 0x31 Trace Sink - Basic trace router
Nc: ROM 1 F0001000: CID B105900D PID 000008E000 CSt MTBDWT type 0x4 Debug Control - Other
Nc: ROM 1 E00FF000: CID B105100D PID 04000BB4C0 ROM (type 0x1)
Nc: ROM 4 E000E000: CID B105E00D PID 04000BB008 Gen SCS (type 0x0)
Nc: ROM 4 E0001000: CID B105E00D PID 04000BB00A Gen DWT (type 0x0)
Nc: ROM 4 E0002000: CID B105E00D PID 04000BB00B Gen FPB (type 0x0)
Nc: NXP: MCXC242
Nc: DAP stride is 1024 bytes (256 words)
Nc: Inspected v.2 On chip Flash memory module FTFA_1K_MCXC.cfx
Nc: Image 'SemiGeneric Sep 19 2024 18:20:26'
Nc: Opening flash driver FTFA_1K_MCXC.cfx
Nc: VECTRESET requested, but not supported on ARMv6-M CPUs. Using SOFTRESET instead.
Nc: Using SOFT reset to run the flash driver
Nc: Flash variant 'MCXC242 FTFA Generic 1K' detected (64KB = 64*1K at 0x0)
Nc: Closing flash driver FTFA_1K_MCXC.cfx
Pc: ( 65) Chip Setup Complete
Pc: ( 70) License Check Complete
Nt: Loading 'zephyr.bin' Binary 0x00000000 len 0x8FFA
Nc: Opening flash driver FTFA_1K_MCXC.cfx (already resident)
Nc: VECTRESET requested, but not supported on ARMv6-M CPUs. Using SOFTRESET instead.
Nc: Using SOFT reset to run the flash driver
Nc: Flash variant 'MCXC242 FTFA Generic 1K' detected (64KB = 64*1K at 0x0)
Pb: 1 of 1 (  0) Writing sectors 0-35 at 0x00000000 with 36860 bytes
Ps: (  0) at 00000000: 0 bytes - 0/36860
Ps: (  2) at 00000000: 1024 bytes - 1024/36860
Ps: (  5) at 00000400: 1024 bytes - 2048/36860
Nc: 00000800 done   5% (2048 out of 36860)
Ps: (100) at 00000800: 34816 bytes - 36864/36860
Nc: Sectors written: 1, unchanged: 35, total: 36
Nc: Closing flash driver FTFA_1K_MCXC.cfx
Pb: (100) Finished writing Flash successfully.
Nt: Loaded 0x8FFA bytes in 161ms (about 228kB/s)
Nt: Reset target (system)
Nc: Starting execution using system reset
Nc: state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
Nc: error closing down debug session - Nn(05). Wire ACK Fault in DAP access

 

 And this on the second try:

 

$ west -v flash
-- west flash: rebuilding
cmake version 3.30.5 is OK; minimum version is 3.13.1
Running CMake: 'C:\Program Files\CMake\bin\cmake.EXE' --build '##############################\build'
ninja: no work to do.
-- west flash: using runner linkserver
runners.linkserver: 'C:\nxp\LinkServer_24.9.75\Linkserver.exe' -v
-- runners.linkserver: LinkServer: C:\nxp\LinkServer_24.9.75\Linkserver.exe, version v24.9.75
runners.linkserver: LinkServer cmd:  + ['C:\\nxp\\LinkServer_24.9.75\\Linkserver.exe', 'flash', '--probe', '#1', 'MCXC242:FRDM-MCXC242']
runners.linkserver: 'C:\nxp\LinkServer_24.9.75\Linkserver.exe' -v
runners.linkserver: flash command = ['C:\\nxp\\LinkServer_24.9.75\\Linkserver.exe', 'flash', '--probe', '#1', 'MCXC242:FRDM-MCXC242', 'load', '--addr', '0', '##############################\\zephyr.bin']
runners.linkserver: 'C:\nxp\LinkServer_24.9.75\Linkserver.exe' flash --probe '#1' MCXC242:FRDM-MCXC242 load --addr 0 '##############################\zephyr.bin'
INFO: Exact match for MCXC242:FRDM-MCXC242 found
INFO: Selected device MCXC242:FRDM-MCXC242
INFO: Getting available probes
INFO: Selecting probe by index
INFO: Selected probe #1 RJ5F0KUBKS14M (MCU-LINK FRDM-MCXC242 (r0E7) CMSIS-DAP V3.146)
INFO: MCU-Link firmware update `check`: local firmware [3.148] can be programmed on the selected probe ([RJ5F0KUBKS14M] [MCU-LINK FRDM-MCXC242 (r0E7) CMSIS-DAP V3.146])
Firmware update `check`: - the update can be performed using `auto` mode
Ns: MCUXpresso IDE RedlinkMulti Driver v24.9 (Sep 19 2024 19:34:05 - crt_emu_cm_redlink.exe build 802)
Pc: (  0) Reading remote configuration
Wc(03). No cache support.
Nc: Found generic directory XML file in ##############################\crt_directory.xml
Pc: (  5) Remote configuration complete
Nc: Reconnected to existing LinkServer process.
Wc: ============= SCRIPT: MCXC_connect.scp =============
Wc: MCXC Connect Script
Wc: Connecting to Probe Index = 1
Wc: This probe = 1
Wc: This TAP = 0
Wc: This core = 0
Wc: DpID = 0BC11477
Wc: Assert NRESET
Wc: Reset pin state: 00
Wc: Power up Debug
Wc: MDM-AP APID: 0x001C0020
Wc: MDM-AP System Reset/Hold Reset/Debug Request
Wc: MDM-AP Control: 0x00000008
Wc: MDM-AP Status (Flash Ready) : 0x00000036
Wc: Part is secured
Wc: Mass Erase Required
Wc: ============= END SCRIPT ===========================
Nc: Probe Firmware: MCU-LINK FRDM-MCXC242 (r0E7) CMSIS-DAP V3.146 (NXP Semiconductors)
Nc: Serial Number:  RJ5F0KUBKS14M
Nc: VID:PID:  1FC9:0143
Nc: USB Path: 0001:0015:00
Nc: Using memory from core 0 after searching for a good core
Ns: redlink server client - failed to receive response (to op 62) from server after 2000ms - timed out (rc 138)
Nc: connection failed - EE(47): Debug Mailbox Request Failed... Retrying
Ns: redlink server client - failed to receive response (to op 12) from server after 2000ms - timed out (rc 138)
Nc: probe 1 TAP 0 failed to read TAP ID - Ee(FF). Redlink interface error 255.
Ed:02: Failed on connect: Ee(FF). Redlink interface error 255.
Et: Probe(0): Connected&Reset. Was: NotConnected. DpID: 0BC11477. CpuID: 00000000. Info: <None>
Nc:   Last stub error 0: OK
Nc:   Last sticky error: 0x0 AIndex: 0
Nc:   Debug bus selected: MemAp 0
Nc:   DAP Speed test unexecuted or failed
Nc: Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.
Pc: (100) Target Operation Failed
Ns: redlink server client - warning - 28 bytes of unexpected data from the server
Nc: error closing down debug session - Nn(05). Wire ACK Fault in DAP access
CRITICAL: Critical error
ERRMSG: Exception: Flash operation exited with code 1
FATAL ERROR: command exited with status 4294967295: 'C:\nxp\LinkServer_24.9.75\Linkserver.exe' flash --probe '#1' MCXC242:FRDM-MCXC242 load --addr 0 '##############################\zephyr.bin'

 

I have no idea why this would happen. Can you help me?

Thanks,

Max

Labels (2)
0 Kudos
Reply
1 Solution
3,389 Views
dereksnell
NXP Employee
NXP Employee

Hi @mw6 and @Alice_Yang ,

Thank for raising this issue.  This was caused by the Flash Security setting in the FSEC location in flash.  We have an upstream Pull Request to resolve this at https://github.com/zephyrproject-rtos/zephyr/pull/82947.

Best regards

View solution in original post

4 Replies
3,390 Views
dereksnell
NXP Employee
NXP Employee

Hi @mw6 and @Alice_Yang ,

Thank for raising this issue.  This was caused by the Flash Security setting in the FSEC location in flash.  We have an upstream Pull Request to resolve this at https://github.com/zephyrproject-rtos/zephyr/pull/82947.

Best regards

3,268 Views
mw6
Contributor I
Hi @dereksnell, thanks for resolving this issue. It works now on my desk!
0 Kudos
Reply
3,370 Views
Alice_Yang
NXP TechSupport
NXP TechSupport

Hello @dereksnell 

Thanks for your kindly help.

 

BR

Alice

0 Kudos
Reply
3,535 Views
Alice_Yang
NXP TechSupport
NXP TechSupport

Hello @mw6 

I have reproduce your issue on my side. I'm still finding the root cause. I will send to you with any update. Thanks for your patience.

 

BR

Alice

0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-1992738%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3EProblem%20flashing%20FRDM-MCXC242%20with%20LinkServer%20(zephyr%3A%20west%20flash)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1992738%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3EI'm%20currently%20evaluating%20Zephyr%20on%20the%20FRDM-MCXC242%20board.%3C%2FP%3E%3CP%3EWhen%20I%20tried%20flashing%20with%20%3CFONT%20face%3D%22courier%20new%2Ccourier%22%3Ewest%20flash%3C%2FFONT%3E%20for%20the%20first%20time%20(using%20LinkServer)%20it%20worked.%20When%20trying%20to%20flash%20for%20a%20second%20time%2C%20%3CFONT%20face%3D%22courier%20new%2Ccourier%22%3Ewest%20flash%3C%2FFONT%3E%20fails.%3C%2FP%3E%3CP%3EI%20can%20recover%20the%20board%20by%20flashing%20with%20a%20JLink%20probe%20(%3CFONT%20face%3D%22courier%20new%2Ccourier%22%3Ewest%20flash%20-r%20jlink%3C%2FFONT%3E).%20Then%20flashing%20with%20LinkServer%20works%20again%20for%20the%20first%20try%20but%20at%20the%20second%20try%20it%20starts%20to%20fail%20again.%3C%2FP%3E%3CP%3EThis%20is%20my%20output%20for%20the%20first%20try%3A%3C%2FP%3E%3CBR%20%2F%3E%3CPRE%20class%3D%22lia-code-sample%20language-c%22%3E%3CCODE%3E%24%20west%20-v%20flash%0A--%20west%20flash%3A%20rebuilding%0Acmake%20version%203.30.5%20is%20OK%3B%20minimum%20version%20is%203.13.1%0ARunning%20CMake%3A%20'C%3A%5CProgram%20Files%5CCMake%5Cbin%5Ccmake.EXE'%20--build%20%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23build'%0Aninja%3A%20no%20work%20to%20do.%0A--%20west%20flash%3A%20using%20runner%20linkserver%0Arunners.linkserver%3A%20'C%3A%5Cnxp%5CLinkServer_24.9.75%5CLinkserver.exe'%20-v%0A--%20runners.linkserver%3A%20LinkServer%3A%20C%3A%5Cnxp%5CLinkServer_24.9.75%5CLinkserver.exe%2C%20version%20v24.9.75%0Arunners.linkserver%3A%20LinkServer%20cmd%3A%20%20%2B%20%5B'C%3A%5C%5Cnxp%5C%5CLinkServer_24.9.75%5C%5CLinkserver.exe'%2C%20'flash'%2C%20'--probe'%2C%20'%231'%2C%20'MCXC242%3AFRDM-MCXC242'%5D%0Arunners.linkserver%3A%20'C%3A%5Cnxp%5CLinkServer_24.9.75%5CLinkserver.exe'%20-v%0Arunners.linkserver%3A%20flash%20command%20%3D%20%5B'C%3A%5C%5Cnxp%5C%5CLinkServer_24.9.75%5C%5CLinkserver.exe'%2C%20'flash'%2C%20'--probe'%2C%20'%231'%2C%20'MCXC242%3AFRDM-MCXC242'%2C%20'load'%2C%20'--addr'%2C%20'0'%2C%20'%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%5C%5Czephyr.bin'%5D%0Arunners.linkserver%3A%20'C%3A%5Cnxp%5CLinkServer_24.9.75%5CLinkserver.exe'%20flash%20--probe%20'%231'%20MCXC242%3AFRDM-MCXC242%20load%20--addr%200%20'%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%5Czephyr.bin'%0AINFO%3A%20Exact%20match%20for%20MCXC242%3AFRDM-MCXC242%20found%0AINFO%3A%20Selected%20device%20MCXC242%3AFRDM-MCXC242%0AINFO%3A%20Getting%20available%20probes%0AINFO%3A%20Selecting%20probe%20by%20index%0AINFO%3A%20Selected%20probe%20%231%20RJ5F0KUBKS14M%20(MCU-LINK%20FRDM-MCXC242%20(r0E7)%20CMSIS-DAP%20V3.146)%0AINFO%3A%20MCU-Link%20firmware%20update%20%60check%60%3A%20local%20firmware%20%5B3.148%5D%20can%20be%20programmed%20on%20the%20selected%20probe%20(%5BRJ5F0KUBKS14M%5D%20%5BMCU-LINK%20FRDM-MCXC242%20(r0E7)%20CMSIS-DAP%20V3.146%5D)%0AFirmware%20update%20%60check%60%3A%20-%20the%20update%20can%20be%20performed%20using%20%60auto%60%20mode%0ANs%3A%20MCUXpresso%20IDE%20RedlinkMulti%20Driver%20v24.9%20(Sep%2019%202024%2019%3A34%3A05%20-%20crt_emu_cm_redlink.exe%20build%20802)%0APc%3A%20(%20%200)%20Reading%20remote%20configuration%0AWc(03).%20No%20cache%20support.%0ANc%3A%20Found%20generic%20directory%20XML%20file%20in%20%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%5Ccrt_directory.xml%0APc%3A%20(%20%205)%20Remote%20configuration%20complete%0ANc%3A%20Reconnected%20to%20existing%20LinkServer%20process.%0AWc%3A%20%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%20SCRIPT%3A%20MCXC_connect.scp%20%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%0AWc%3A%20MCXC%20Connect%20Script%0AWc%3A%20Connecting%20to%20Probe%20Index%20%3D%201%0AWc%3A%20This%20probe%20%3D%201%0AWc%3A%20This%20TAP%20%3D%200%0AWc%3A%20This%20core%20%3D%200%0AWc%3A%20DpID%20%3D%200BC11477%0AWc%3A%20Assert%20NRESET%0AWc%3A%20Reset%20pin%20state%3A%2000%0AWc%3A%20Power%20up%20Debug%0AWc%3A%20MDM-AP%20APID%3A%200x001C0020%0AWc%3A%20MDM-AP%20System%20Reset%2FHold%20Reset%2FDebug%20Request%0AWc%3A%20MDM-AP%20Control%3A%200x0000001C%0AWc%3A%20MDM-AP%20Status%20(Flash%20Ready)%20%3A%200x00000033%0AWc%3A%20Part%20is%20not%20secured%0AWc%3A%20MDM-AP%20Control%3A%200x00000014%0AWc%3A%20Release%20NRESET%0AWc%3A%20Reset%20pin%20state%3A%2001%0AWc%3A%20MDM-AP%20Control%20(Debug%20Request)%3A%200x00000004%0AWc%3A%20MDM-AP%20Status%3A%200x0001003B%0AWc%3A%20MDM-AP%20Core%20Halted%0AWc%3A%20%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%20END%20SCRIPT%20%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%0ANc%3A%20Probe%20Firmware%3A%20MCU-LINK%20FRDM-MCXC242%20(r0E7)%20CMSIS-DAP%20V3.146%20(NXP%20Semiconductors)%0ANc%3A%20Serial%20Number%3A%20%20RJ5F0KUBKS14M%0ANc%3A%20VID%3APID%3A%20%201FC9%3A0143%0ANc%3A%20USB%20Path%3A%200001%3A0005%3A00%0ANc%3A%20Using%20memory%20from%20core%200%20after%20searching%20for%20a%20good%20core%0APc%3A%20(%2030)%20Emulator%20Connected%0APc%3A%20(%2040)%20Debug%20Halt%0APc%3A%20(%2050)%20CPU%20ID%0ANc%3A%20debug%20interface%20type%20%20%20%20%20%20%3D%20CoreSight%20DP%20(DAP%20DP%20ID%200BC11477)%20over%20SWD%20TAP%200%0ANc%3A%20processor%20type%20%20%20%20%20%20%20%20%20%20%20%20%3D%20Cortex-M0%2B%20(CPU%20ID%2000000C60)%20on%20DAP%20AP%200%0ANc%3A%20number%20of%20h%2Fw%20breakpoints%20%3D%202%0ANc%3A%20number%20of%20flash%20patches%20%20%20%3D%200%0ANc%3A%20number%20of%20h%2Fw%20watchpoints%20%3D%202%0ANc%3A%20Probe(0)%3A%20Connected%26amp%3BReset.%20DpID%3A%200BC11477.%20CpuID%3A%2000000C60.%20Info%3A%20%3CNONE%3E%0ANc%3A%20Debug%20protocol%3A%20SWD.%20RTCK%3A%20Disabled.%20Vector%20catch%3A%20Disabled.%0ANs%3A%20Content%20of%20CoreSight%20Debug%20ROM(s)%3A%0ANc%3A%20RBASE%20F0002000%3A%20CID%20B105100D%20PID%20000008E000%20ROM%20(type%200x1)%0ANc%3A%20ROM%201%20F0000000%3A%20CID%20B105900D%20PID%2004001BB932%20CSt%20ARM%20MTB%20type%200x31%20Trace%20Sink%20-%20Basic%20trace%20router%0ANc%3A%20ROM%201%20F0001000%3A%20CID%20B105900D%20PID%20000008E000%20CSt%20MTBDWT%20type%200x4%20Debug%20Control%20-%20Other%0ANc%3A%20ROM%201%20E00FF000%3A%20CID%20B105100D%20PID%2004000BB4C0%20ROM%20(type%200x1)%0ANc%3A%20ROM%204%20E000E000%3A%20CID%20B105E00D%20PID%2004000BB008%20Gen%20SCS%20(type%200x0)%0ANc%3A%20ROM%204%20E0001000%3A%20CID%20B105E00D%20PID%2004000BB00A%20Gen%20DWT%20(type%200x0)%0ANc%3A%20ROM%204%20E0002000%3A%20CID%20B105E00D%20PID%2004000BB00B%20Gen%20FPB%20(type%200x0)%0ANc%3A%20NXP%3A%20MCXC242%0ANc%3A%20DAP%20stride%20is%201024%20bytes%20(256%20words)%0ANc%3A%20Inspected%20v.2%20On%20chip%20Flash%20memory%20module%20FTFA_1K_MCXC.cfx%0ANc%3A%20Image%20'SemiGeneric%20Sep%2019%202024%2018%3A20%3A26'%0ANc%3A%20Opening%20flash%20driver%20FTFA_1K_MCXC.cfx%0ANc%3A%20VECTRESET%20requested%2C%20but%20not%20supported%20on%20ARMv6-M%20CPUs.%20Using%20SOFTRESET%20instead.%0ANc%3A%20Using%20SOFT%20reset%20to%20run%20the%20flash%20driver%0ANc%3A%20Flash%20variant%20'MCXC242%20FTFA%20Generic%201K'%20detected%20(64KB%20%3D%2064*1K%20at%200x0)%0ANc%3A%20Closing%20flash%20driver%20FTFA_1K_MCXC.cfx%0APc%3A%20(%2065)%20Chip%20Setup%20Complete%0APc%3A%20(%2070)%20License%20Check%20Complete%0ANt%3A%20Loading%20'zephyr.bin'%20Binary%200x00000000%20len%200x8FFA%0ANc%3A%20Opening%20flash%20driver%20FTFA_1K_MCXC.cfx%20(already%20resident)%0ANc%3A%20VECTRESET%20requested%2C%20but%20not%20supported%20on%20ARMv6-M%20CPUs.%20Using%20SOFTRESET%20instead.%0ANc%3A%20Using%20SOFT%20reset%20to%20run%20the%20flash%20driver%0ANc%3A%20Flash%20variant%20'MCXC242%20FTFA%20Generic%201K'%20detected%20(64KB%20%3D%2064*1K%20at%200x0)%0APb%3A%201%20of%201%20(%20%200)%20Writing%20sectors%200-35%20at%200x00000000%20with%2036860%20bytes%0APs%3A%20(%20%200)%20at%2000000000%3A%200%20bytes%20-%200%2F36860%0APs%3A%20(%20%202)%20at%2000000000%3A%201024%20bytes%20-%201024%2F36860%0APs%3A%20(%20%205)%20at%2000000400%3A%201024%20bytes%20-%202048%2F36860%0ANc%3A%2000000800%20done%20%20%205%25%20(2048%20out%20of%2036860)%0APs%3A%20(100)%20at%2000000800%3A%2034816%20bytes%20-%2036864%2F36860%0ANc%3A%20Sectors%20written%3A%201%2C%20unchanged%3A%2035%2C%20total%3A%2036%0ANc%3A%20Closing%20flash%20driver%20FTFA_1K_MCXC.cfx%0APb%3A%20(100)%20Finished%20writing%20Flash%20successfully.%0ANt%3A%20Loaded%200x8FFA%20bytes%20in%20161ms%20(about%20228kB%2Fs)%0ANt%3A%20Reset%20target%20(system)%0ANc%3A%20Starting%20execution%20using%20system%20reset%0ANc%3A%20state%20-%20running%20or%20following%20reset%20request%20-%20re-read%20of%20state%20failed%20-%20rc%20Nn(05).%20Wire%20ACK%20Fault%20in%20DAP%20access%0ANc%3A%20error%20closing%20down%20debug%20session%20-%20Nn(05).%20Wire%20ACK%20Fault%20in%20DAP%20access%3C%2FNONE%3E%3C%2FCODE%3E%3C%2FPRE%3E%3CBR%20%2F%3E%3CP%3E%26nbsp%3BAnd%20this%20on%20the%20second%20try%3A%3C%2FP%3E%3CBR%20%2F%3E%3CPRE%20class%3D%22lia-code-sample%20language-c%22%3E%3CCODE%3E%24%20west%20-v%20flash%0A--%20west%20flash%3A%20rebuilding%0Acmake%20version%203.30.5%20is%20OK%3B%20minimum%20version%20is%203.13.1%0ARunning%20CMake%3A%20'C%3A%5CProgram%20Files%5CCMake%5Cbin%5Ccmake.EXE'%20--build%20'%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%5Cbuild'%0Aninja%3A%20no%20work%20to%20do.%0A--%20west%20flash%3A%20using%20runner%20linkserver%0Arunners.linkserver%3A%20'C%3A%5Cnxp%5CLinkServer_24.9.75%5CLinkserver.exe'%20-v%0A--%20runners.linkserver%3A%20LinkServer%3A%20C%3A%5Cnxp%5CLinkServer_24.9.75%5CLinkserver.exe%2C%20version%20v24.9.75%0Arunners.linkserver%3A%20LinkServer%20cmd%3A%20%20%2B%20%5B'C%3A%5C%5Cnxp%5C%5CLinkServer_24.9.75%5C%5CLinkserver.exe'%2C%20'flash'%2C%20'--probe'%2C%20'%231'%2C%20'MCXC242%3AFRDM-MCXC242'%5D%0Arunners.linkserver%3A%20'C%3A%5Cnxp%5CLinkServer_24.9.75%5CLinkserver.exe'%20-v%0Arunners.linkserver%3A%20flash%20command%20%3D%20%5B'C%3A%5C%5Cnxp%5C%5CLinkServer_24.9.75%5C%5CLinkserver.exe'%2C%20'flash'%2C%20'--probe'%2C%20'%231'%2C%20'MCXC242%3AFRDM-MCXC242'%2C%20'load'%2C%20'--addr'%2C%20'0'%2C%20'%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%5C%5Czephyr.bin'%5D%0Arunners.linkserver%3A%20'C%3A%5Cnxp%5CLinkServer_24.9.75%5CLinkserver.exe'%20flash%20--probe%20'%231'%20MCXC242%3AFRDM-MCXC242%20load%20--addr%200%20'%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%5Czephyr.bin'%0AINFO%3A%20Exact%20match%20for%20MCXC242%3AFRDM-MCXC242%20found%0AINFO%3A%20Selected%20device%20MCXC242%3AFRDM-MCXC242%0AINFO%3A%20Getting%20available%20probes%0AINFO%3A%20Selecting%20probe%20by%20index%0AINFO%3A%20Selected%20probe%20%231%20RJ5F0KUBKS14M%20(MCU-LINK%20FRDM-MCXC242%20(r0E7)%20CMSIS-DAP%20V3.146)%0AINFO%3A%20MCU-Link%20firmware%20update%20%60check%60%3A%20local%20firmware%20%5B3.148%5D%20can%20be%20programmed%20on%20the%20selected%20probe%20(%5BRJ5F0KUBKS14M%5D%20%5BMCU-LINK%20FRDM-MCXC242%20(r0E7)%20CMSIS-DAP%20V3.146%5D)%0AFirmware%20update%20%60check%60%3A%20-%20the%20update%20can%20be%20performed%20using%20%60auto%60%20mode%0ANs%3A%20MCUXpresso%20IDE%20RedlinkMulti%20Driver%20v24.9%20(Sep%2019%202024%2019%3A34%3A05%20-%20crt_emu_cm_redlink.exe%20build%20802)%0APc%3A%20(%20%200)%20Reading%20remote%20configuration%0AWc(03).%20No%20cache%20support.%0ANc%3A%20Found%20generic%20directory%20XML%20file%20in%20%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%5Ccrt_directory.xml%0APc%3A%20(%20%205)%20Remote%20configuration%20complete%0ANc%3A%20Reconnected%20to%20existing%20LinkServer%20process.%0AWc%3A%20%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%20SCRIPT%3A%20MCXC_connect.scp%20%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%0AWc%3A%20MCXC%20Connect%20Script%0AWc%3A%20Connecting%20to%20Probe%20Index%20%3D%201%0AWc%3A%20This%20probe%20%3D%201%0AWc%3A%20This%20TAP%20%3D%200%0AWc%3A%20This%20core%20%3D%200%0AWc%3A%20DpID%20%3D%200BC11477%0AWc%3A%20Assert%20NRESET%0AWc%3A%20Reset%20pin%20state%3A%2000%0AWc%3A%20Power%20up%20Debug%0AWc%3A%20MDM-AP%20APID%3A%200x001C0020%0AWc%3A%20MDM-AP%20System%20Reset%2FHold%20Reset%2FDebug%20Request%0AWc%3A%20MDM-AP%20Control%3A%200x00000008%0AWc%3A%20MDM-AP%20Status%20(Flash%20Ready)%20%3A%200x00000036%0AWc%3A%20Part%20is%20secured%0AWc%3A%20Mass%20Erase%20Required%0AWc%3A%20%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%20END%20SCRIPT%20%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%0ANc%3A%20Probe%20Firmware%3A%20MCU-LINK%20FRDM-MCXC242%20(r0E7)%20CMSIS-DAP%20V3.146%20(NXP%20Semiconductors)%0ANc%3A%20Serial%20Number%3A%20%20RJ5F0KUBKS14M%0ANc%3A%20VID%3APID%3A%20%201FC9%3A0143%0ANc%3A%20USB%20Path%3A%200001%3A0015%3A00%0ANc%3A%20Using%20memory%20from%20core%200%20after%20searching%20for%20a%20good%20core%0ANs%3A%20redlink%20server%20client%20-%20failed%20to%20receive%20response%20(to%20op%2062)%20from%20server%20after%202000ms%20-%20timed%20out%20(rc%20138)%0ANc%3A%20connection%20failed%20-%20EE(47)%3A%20Debug%20Mailbox%20Request%20Failed...%20Retrying%0ANs%3A%20redlink%20server%20client%20-%20failed%20to%20receive%20response%20(to%20op%2012)%20from%20server%20after%202000ms%20-%20timed%20out%20(rc%20138)%0ANc%3A%20probe%201%20TAP%200%20failed%20to%20read%20TAP%20ID%20-%20Ee(FF).%20Redlink%20interface%20error%20255.%0AEd%3A02%3A%20Failed%20on%20connect%3A%20Ee(FF).%20Redlink%20interface%20error%20255.%0AEt%3A%20Probe(0)%3A%20Connected%26amp%3BReset.%20Was%3A%20NotConnected.%20DpID%3A%200BC11477.%20CpuID%3A%2000000000.%20Info%3A%20%3CNONE%3E%0ANc%3A%20%20%20Last%20stub%20error%200%3A%20OK%0ANc%3A%20%20%20Last%20sticky%20error%3A%200x0%20AIndex%3A%200%0ANc%3A%20%20%20Debug%20bus%20selected%3A%20MemAp%200%0ANc%3A%20%20%20DAP%20Speed%20test%20unexecuted%20or%20failed%0ANc%3A%20Debug%20protocol%3A%20SWD.%20RTCK%3A%20Disabled.%20Vector%20catch%3A%20Disabled.%0APc%3A%20(100)%20Target%20Operation%20Failed%0ANs%3A%20redlink%20server%20client%20-%20warning%20-%2028%20bytes%20of%20unexpected%20data%20from%20the%20server%0ANc%3A%20error%20closing%20down%20debug%20session%20-%20Nn(05).%20Wire%20ACK%20Fault%20in%20DAP%20access%0ACRITICAL%3A%20Critical%20error%0AERRMSG%3A%20Exception%3A%20Flash%20operation%20exited%20with%20code%201%0AFATAL%20ERROR%3A%20command%20exited%20with%20status%204294967295%3A%20'C%3A%5Cnxp%5CLinkServer_24.9.75%5CLinkserver.exe'%20flash%20--probe%20'%231'%20MCXC242%3AFRDM-MCXC242%20load%20--addr%200%20'%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%5Czephyr.bin'%3C%2FNONE%3E%3C%2FCODE%3E%3C%2FPRE%3E%3CBR%20%2F%3E%3CP%3EI%20have%20no%20idea%20why%20this%20would%20happen.%20Can%20you%20help%20me%3F%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3EMax%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1992738%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CLINGO-LABEL%3EDevelopment%20Board%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMCXC%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2023207%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3ERe%3A%20Problem%20flashing%20FRDM-MCXC242%20with%20LinkServer%20(zephyr%3A%20west%20flash)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2023207%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3EHi%20%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F30672%22%20target%3D%22_blank%22%3E%40dereksnell%3C%2FA%3E%2C%20thanks%20for%20resolving%20this%20issue.%20It%20works%20now%20on%20my%20desk!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2014000%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3ERe%3A%20Problem%20flashing%20FRDM-MCXC242%20with%20LinkServer%20(zephyr%3A%20west%20flash)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2014000%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHello%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F30672%22%20target%3D%22_blank%22%3E%40dereksnell%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%20for%20your%20kindly%20help.%3C%2FP%3E%0A%3CBR%20%2F%3E%0A%3CP%3EBR%3C%2FP%3E%0A%3CP%3EAlice%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2013708%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3ERe%3A%20Problem%20flashing%20FRDM-MCXC242%20with%20LinkServer%20(zephyr%3A%20west%20flash)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2013708%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F206611%22%20target%3D%22_blank%22%3E%40mw6%3C%2FA%3E%26nbsp%3Band%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F27788%22%20target%3D%22_blank%22%3E%40Alice_Yang%3C%2FA%3E%26nbsp%3B%2C%3C%2FP%3E%0A%3CP%3EThank%20for%20raising%20this%20issue.%26nbsp%3B%20This%20was%20caused%20by%20the%20Flash%20Security%20setting%20in%20the%20FSEC%20location%20in%20flash.%26nbsp%3B%20We%20have%20an%20upstream%20Pull%20Request%20to%20resolve%20this%20at%20%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2Fzephyrproject-rtos%2Fzephyr%2Fpull%2F82947%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2Fzephyrproject-rtos%2Fzephyr%2Fpull%2F82947%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3EBest%20regards%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2006578%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3ERe%3A%20Problem%20flashing%20FRDM-MCXC242%20with%20LinkServer%20(zephyr%3A%20west%20flash)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2006578%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHello%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F206611%22%20target%3D%22_blank%22%3E%40mw6%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20have%20reproduce%20your%20issue%20on%20my%20side.%20I'm%20still%20finding%20the%20root%20cause.%20I%20will%20send%20to%20you%20with%20any%20update.%20Thanks%20for%20your%20patience.%3C%2FP%3E%0A%3CBR%20%2F%3E%0A%3CP%3EBR%3C%2FP%3E%0A%3CP%3EAlice%3C%2FP%3E%3C%2FLINGO-BODY%3E