FRDM-MCXE31B

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

FRDM-MCXE31B

184 Views
Lokeshgowdas
Contributor I

 

I'm trying to debug/flash a FRDM-MCXE31B board and consistently hit a RAM initialization failure during the connect sequence, before any application code loads. I've ruled out wiring, cables, USB ports, jumpers, and probe firmware — details below.

Setup:

  • Board: FRDM-MCXE31B
  • M C U: MCXE31B
  • Tested with: M C U X Presso IDE v25.6 (Windows) and standalone Link-server v26.6.137 (Ubuntu Linux) — same failure on both
  • MCU-Link onboard probe firmware: updated to v3.172 (confirmed matching, no version mismatch reported)
  • Connect script: MCXE31x_connect.scp

What works:

  • SWD physical connection succeeds
  • Debug authentication/unlock succeeds ("application debug already enabled")
  • Chip identification succeeds — reads back correct part number:
 
SIUL2:MIDR1 @ 0x40290004 = 0x6BA02477
MCU Part Number is 0x000003A0

Where it fails — every attempt, both OSes:

 
... RAM init via eDMA: address=0x20400000 size=0x00028000
Error: Wire Ack Fault - target connected? [repeats ~46 times]
Error: RAM initialization failed (timeout)!

This leads to: Failed on connect: Ep(01). Target marked as not debuggable.

Context I found that may be relevant: I understand from the S32K3 reference manual (same architecture family) that ECC-protected RAM on these parts must be initialized via a 64-bit master write before any 32-bit access is valid after power-on-reset — so I assume this eDMA step in the connect script is performing that mandatory initialization automatically. It appears to be this automated step itself that's timing out, not a wiring/connection issue, since chip identification (steps before this) succeeds cleanly every time.

Question: Has anyone else hit this specific failure on FRDM-MCXE31B? Is there a known workaround, updated connect script, or a way to skip/adjust the automatic RAM-init step? Happy to provide full verbose logs (Link-server -l 5) if useful.

0 Kudos
Reply
1 Reply

166 Views
carlos_o
NXP TechSupport
NXP TechSupport

Hi @Lokeshgowdas 

Thank you for your post!

Is this happening only in one project? 

I see that your project is using Zephyr, could you please share which version are you using?

Please share the logs to review it. 

 

0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-2408846%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3EFRDM-MCXE31B%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2408846%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CBR%20%2F%3E%3CP%3EI'm%20trying%20to%20debug%2Fflash%20a%20FRDM-MCXE31B%20board%20and%20consistently%20hit%20a%20RAM%20initialization%20failure%20during%20the%20connect%20sequence%2C%20before%20any%20application%20code%20loads.%20I've%20ruled%20out%20wiring%2C%20cables%2C%20USB%20ports%2C%20jumpers%2C%20and%20probe%20firmware%20%E2%80%94%20details%20below.%3C%2FP%3E%3CP%3E%3CSTRONG%3ESetup%3A%3C%2FSTRONG%3E%3C%2FP%3E%3CUL%3E%3CLI%3EBoard%3A%20FRDM-MCXE31B%3C%2FLI%3E%3CLI%3EM%20C%20U%3A%20MCXE31B%3C%2FLI%3E%3CLI%3ETested%20with%3A%20M%20C%20U%20X%20Presso%20IDE%20v25.6%20(Windows)%20and%20standalone%20Link-server%20v26.6.137%20(Ubuntu%20Linux)%20%E2%80%94%20same%20failure%20on%20both%3C%2FLI%3E%3CLI%3EMCU-Link%20onboard%20probe%20firmware%3A%20updated%20to%20v3.172%20(confirmed%20matching%2C%20no%20version%20mismatch%20reported)%3C%2FLI%3E%3CLI%3EConnect%20script%3A%20MCXE31x_connect.scp%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%3CSTRONG%3EWhat%20works%3A%3C%2FSTRONG%3E%3C%2FP%3E%3CUL%3E%3CLI%3ESWD%20physical%20connection%20succeeds%3C%2FLI%3E%3CLI%3EDebug%20authentication%2Funlock%20succeeds%20(%22application%20debug%20already%20enabled%22)%3C%2FLI%3E%3CLI%3EChip%20identification%20succeeds%20%E2%80%94%20reads%20back%20correct%20part%20number%3A%3C%2FLI%3E%3C%2FUL%3E%3CDIV%3E%3CDIV%3E%3CDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FDIV%3E%3CDIV%3E%3CPRE%3ESIUL2%3AMIDR1%20%40%200x40290004%20%3D%200x6BA02477%0AMCU%20Part%20Number%20is%200x000003A0%3C%2FPRE%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3CP%3E%3CSTRONG%3EWhere%20it%20fails%20%E2%80%94%20every%20attempt%2C%20both%20OSes%3A%3C%2FSTRONG%3E%3C%2FP%3E%3CDIV%3E%3CDIV%3E%3CDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FDIV%3E%3CDIV%3E%3CPRE%3E...%20RAM%20init%20via%20eDMA%3A%20address%3D0x20400000%20size%3D0x00028000%0AError%3A%20Wire%20Ack%20Fault%20-%20target%20connected%3F%20%5Brepeats%20~46%20times%5D%0AError%3A%20RAM%20initialization%20failed%20(timeout)!%3C%2FPRE%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3CP%3EThis%20leads%20to%3A%20Failed%20on%20connect%3A%20Ep(01).%20Target%20marked%20as%20not%20debuggable.%3C%2FP%3E%3CP%3E%3CSTRONG%3EContext%20I%20found%20that%20may%20be%20relevant%3A%3C%2FSTRONG%3E%20I%20understand%20from%20the%20S32K3%20reference%20manual%20(same%20architecture%20family)%20that%20ECC-protected%20RAM%20on%20these%20parts%20must%20be%20initialized%20via%20a%2064-bit%20master%20write%20before%20any%2032-bit%20access%20is%20valid%20after%20power-on-reset%20%E2%80%94%20so%20I%20assume%20this%20eDMA%20step%20in%20the%20connect%20script%20is%20performing%20that%20mandatory%20initialization%20automatically.%20It%20appears%20to%20be%20this%20automated%20step%20itself%20that's%20timing%20out%2C%20not%20a%20wiring%2Fconnection%20issue%2C%20since%20chip%20identification%20(steps%20before%20this)%20succeeds%20cleanly%20every%20time.%3C%2FP%3E%3CP%3E%3CSTRONG%3EQuestion%3A%3C%2FSTRONG%3E%20Has%20anyone%20else%20hit%20this%20specific%20failure%20on%20FRDM-MCXE31B%3F%20Is%20there%20a%20known%20workaround%2C%20updated%20connect%20script%2C%20or%20a%20way%20to%20skip%2Fadjust%20the%20automatic%20RAM-init%20step%3F%20Happy%20to%20provide%20full%20verbose%20logs%20(Link-server%20-l%205)%20if%20useful.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2408846%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CLINGO-LABEL%3ECommunication%20%26amp%3B%20Control(I3C%20%7C%20I2C%20%7C%20SPI%20%7C%20FlexCAN%20%7C%20Ethernet%20%7C%20FlexIO)%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2408991%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20FRDM-MCXE31B%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2408991%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%2F265994%22%20target%3D%22_blank%22%3E%40Lokeshgowdas%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThank%20you%20for%20your%20post!%3C%2FP%3E%0A%3CP%3EIs%20this%20happening%20only%20in%20one%20project%3F%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20see%20that%20your%20project%20is%20using%20Zephyr%2C%20could%20you%20please%20share%20which%20version%20are%20you%20using%3F%3C%2FP%3E%0A%3CP%3EPlease%20share%20the%20logs%20to%20review%20it.%26nbsp%3B%3C%2FP%3E%0A%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E