AnsweredAssumed Answered

PN7462 Debugging Issue

Question asked by Amol Borase on May 16, 2019
Latest reply on Aug 22, 2019 by Amol Borase

Dear All,

We are facing issue while Debugging PN7462 chip and we are using LPC LINK-2 to debug. MCUXpresso IDE shows following error message:

 

MCUXpresso IDE RedlinkMulti Driver v10.2 (May 10 2018 18:10:59 - crt_emu_cm_redlink build 510)
Reconnected to existing link server
Connecting to probe 1 core 0:0 (using server started externally) gave 'Ee(42). Could not connect to core.'
Connecting to probe 1 core 0:0 (using server started externally) gave 'Ee(42). Could not connect to core.'
Connecting to probe 1 core 0:0 (using server started externally) gave 'Ee(42). Could not connect to core.'
Server OK but no connection to probe 1 core 0:0 (after 3 attempts) - Ee(42). Could not connect to core.
Failed on connect: Ee(42). Could not connect to core.
No connection to chip's debug port

 

We tried to solve the problem by doing few things but can't get succeed :

 

>> Tried to debug the same board on other computer.
>> We also tried by uninstalling the LPC LINK-2 driver.
>> Tried to debug with new LPC LINK-2 and also check old one with demo board it's working as well, so there is no issue of LPC LINK-2.
>> We have also try the "mass erase".
>> Try different USB ports.
>> We also take care that things like redlinkserv, arm-none-eabi_gdb*, crt_emu_* not running behind while start with new debug session.
>> Also checked by deleting launch file

We are facing above problem frequently, It happens in 2 days or in month also that is not fix. We changed approximately 10 number of IC's till now , If we take new IC, it works fine in debug mode, So we don't get exact reason for issue. Request you to please let us know that what can be the issue.

 

Can we send some samples of faulty IC's to the NXP Laboratory so that we can get the cause of the issue.

Outcomes