LPC55S69-EVK : "0 available SWD Devices detected"

cancel
Showing results for 
Search instead for 
Did you mean: 

LPC55S69-EVK : "0 available SWD Devices detected"

668 Views
Senior Contributor I

Hello !

After week of usage I have got dead board effect : LPC55S69-evk "0 available SWD Devices detected" 

Mass erase with jumper J10 dosn't help. Board Revision A1.

What else is possible to try ?

Logs :

"

Executing flash operation 'Erase' (Erase flash) - Fri Oct 25 16:52:16 EEST 2019
Checking MCU info...
Scanning for targets...
Executing flash action...
MCUXpresso IDE RedlinkMulti Driver v11.0 (Aug 27 2019 16:46:33 - crt_emu_cm_redlink.exe build 22)
( 0) Reading remote configuration
Wc(03). No cache support.
Found chip XML file in C:/MyProjectsLPC55S69/_test_sdk_examples/lpcxpresso55s69_rtc_example/Debug\LPC55S69.xml
( 5) Remote configuration complete
Reconnected to existing LinkServer process.
connection failed - Em(01). Cannot find MEM-AP selected by core index (check target power).. Retrying
Failed on connect: Em(01). Cannot find MEM-AP selected by core index (check target power)
Connected&Reset. Was: NotConnected. DpID: 6BA02477. CpuID: 00000000. Info: <None>
Last stub error 0: OK
Last sticky error: 0x0 AIndex: 0
No debug bus (MemAp) selected
DAP Speed test unexecuted or failed
Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.
(100) Target Connection Failed
Unable to perform operation!
Command failed with exit code 1

"

I have also tru to replace debugger wit internal  Internal and External Debug Options for the NXP LPC55S69-EVK Board | MCU on Eclipse 

and external J-Link box and those are is also can't see any MCU core.

Now I revert to LPC-Link2/CMSIS-DAP again but something wrong with board.

Can it be repaired some how ?

Regards,

Eugene

0 Kudos
5 Replies

165 Views
NXP Employee
NXP Employee

In the first place, please see : https://community.nxp.com/community/mcuxpresso/mcuxpresso-ide/blog/2019/10/30/mcuxpresso-ide-v1101-l... 

Regards,

MCUXpresso IDE Support

0 Kudos

165 Views
NXP TechSupport
NXP TechSupport

Hello Eugene,

 

Probably you need to select the appropriate flash driver reset handling value. You can set this by doing the following:

 

1. Right click on the project in the Project Explorer view.

 

2. Select "Launch Configurations" -> Edit current launch configuration.

 

3. Click on the "Debugger" tab, then switch "Flash driver reset handling" from SYSRESETREQ to VECTRESET or vice versa depending on the failing configuration.

 

You can check the following community thread for more information regarding this issue.

https://community.nxp.com/message/1217974 

 

Hope it helps!

 

Have a great day,
Felipe

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

0 Kudos

165 Views
Senior Contributor I

Hi Felipe !

Can be something different ?

pastedImage_1.png

or some other fields should have some value ?

In my case all problems starts when I erase sector after that one what is used in flashiap1 SDK example

original line :

destAdrss = pflashBlockBase + (pflashTotalSize - (PAGE_INDEX_FROM_END * PflashPageSize));

// and I add

destAdrss += 512;

Can I erase some important info ?

Regards,

Eugene

0 Kudos

165 Views
NXP TechSupport
NXP TechSupport

Hi Eugene,

 

There is a section in Protected Flash Region and it is used as the persistent storage for the secure boot and the SoC specific parameters. It starts at fixed address 0x3DE00.

 

Please check the flash regions you erased in your program because maybe it affected the chip permanently.

 

Best regards,

Felipe

0 Kudos

165 Views
Senior Contributor I

Hi Felipe !

Does this error fixed in latest chip revision ( romcode 1B ?) ?

It shouldn't be so easy to erase protected flash areas.

By the way, I found today my misundestanding about how-to individual GPIO can be shared between cores :

https://community.nxp.com/thread/516798  

It is very urgent and important for our design.

Does it possible to anwer it with some prioprity ?

Thank you !

Regards,

Eugene

0 Kudos