FRDM-MCXW2 Cannot read CPUID error

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

FRDM-MCXW2 Cannot read CPUID error

992 Views
brianmohlman
Contributor II

Hello,

I have been working with two FRDM-MCXW72 boards, at first when I went to debug the app I was getting GDB timeout errors, and I went to manually erase and flash one and now it reports that the CPUID register cannot be read. Cannot erase, or flash code to it. Is this MCU now locked? Is there a way to "unlock" it? Also what cause the GDBN timeout to occur? Any thoughts/help would be appreciated.

Thanks,

Labels (1)
0 Kudos
Reply
1 Reply

885 Views
sofiaurueta
NXP Employee
NXP Employee

Hello, hope you are doing well.

 

Could you please describe how you tried to debug an application? What was the last application you tried debugging? Were you able to flash and debug the board normally prior to this issue?

 

How did you manually erase the device? You could try doing a mass-erase by using an "unlock kinetis" command in J-Link Commander, or a mass erase command through MCUXpresso (using the GUI Flash Tool).

 

Afterwards, could you please try following the steps on the Getting Started with FRDM-MCXW72 and let me know if you are able to follow the process?

 

Best regards,
Ana Sofia.

0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-2335961%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3EFRDM-MCXW2%20Cannot%20read%20CPUID%20error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2335961%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3EI%20have%20been%20working%20with%20two%20FRDM-MCXW72%20boards%2C%20at%20first%20when%20I%20went%20to%20debug%20the%20app%20I%20was%20getting%20GDB%20timeout%20errors%2C%20and%20I%20went%20to%20manually%20erase%20and%20flash%20one%20and%20now%20it%20reports%20that%20the%20CPUID%20register%20cannot%20be%20read.%20Cannot%20erase%2C%20or%20flash%20code%20to%20it.%20Is%20this%20MCU%20now%20locked%3F%20Is%20there%20a%20way%20to%20%22unlock%22%20it%3F%20Also%20what%20cause%20the%20GDBN%20timeout%20to%20occur%3F%20Any%20thoughts%2Fhelp%20would%20be%20appreciated.%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2335961%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CLINGO-LABEL%3EDevelopment%20Board%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2338711%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20FRDM-MCXW2%20Cannot%20read%20CPUID%20error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2338711%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHello%2C%20hope%20you%20are%20doing%20well.%3C%2FP%3E%0A%3CBR%20%2F%3E%0A%3CP%3ECould%20you%20please%20describe%20how%20you%20tried%20to%20debug%20an%20application%3F%20What%20was%20the%20last%20application%20you%20tried%20debugging%3F%20Were%20you%20able%20to%20flash%20and%20debug%20the%20board%20normally%20prior%20to%20this%20issue%3F%3C%2FP%3E%0A%3CBR%20%2F%3E%0A%3CP%3EHow%20did%20you%20manually%20erase%20the%20device%3F%20You%20could%20try%20doing%20a%20mass-erase%20by%20using%20an%20%22unlock%20kinetis%22%20command%20in%20J-Link%20Commander%2C%20or%20a%20mass%20erase%20command%20through%20MCUXpresso%20(using%20the%20GUI%20Flash%20Tool).%3C%2FP%3E%0A%3CBR%20%2F%3E%0A%3CP%3EAfterwards%2C%20could%20you%20please%20try%20following%20the%20steps%20on%20the%20%3CA%20href%3D%22https%3A%2F%2Fwww.nxp.com%2Fdocument%2Fguide%2Fgetting-started-with-frdm-mcxw72%3AGS-FRDM-MCXW72%3F_gl%3D1*r488dt*_ga*NzUzMTQ1MDA1LjE3NzM0MTc2MzQ.*_ga_WM5LE0KMSH*czE3NzQzNjQ2NjkkbzMwJGcxJHQxNzc0MzY4OTY0JGozMyRsMCRoMTUwMzg3NzkxMw%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3EGetting%20Started%20with%20FRDM-MCXW72%3C%2FA%3E%20and%20let%20me%20know%20if%20you%20are%20able%20to%20follow%20the%20process%3F%3C%2FP%3E%0A%3CBR%20%2F%3E%0A%3CP%3EBest%20regards%2C%3CBR%20%2F%3EAna%20Sofia.%3C%2FP%3E%3C%2FLINGO-BODY%3E