Failed on connect: Ee(36). Could not connect to core. using LPC1768 and Red Probe +

cancel
Showing results for 
Search instead for 
Did you mean: 

Failed on connect: Ee(36). Could not connect to core. using LPC1768 and Red Probe +

Jump to solution
610 Views
Contributor II

I am getting the following error.

Ni: LPCXpresso RedlinkMulti Driver v8.2 (Sep 5 2016 10:12:38 - crt_emu_cm_redlink.exe build 725)
Pc: ( 0) Reading remote configuration
Pc: ( 5) Remote configuration complete
Nc: connecting to core 0 with handle 0x0 (using server PID -1) gave rc 'Ee(36). Could not connect to core.'
Nc: connecting to core 0 with handle 0x0 (using server PID -1) gave rc 'Ee(36). Could not connect to core.'
Nc: connecting to core 0 with handle 0x0 (using server PID -1) gave rc 'Ee(36). Could not connect to core.'
Nc: probe unbooted? no core 0?
Ed:02: Failed on connect: Ee(36). Could not connect to core.
Et:31: No connection to emulator device
Pc: (100) Target Connection Failed

Please advise how to troubleshoot.

Also when I start the flash programming, I do not see a drive for LPC176x in the flash driver option.

pastedImage_3.png

Thanks

Labels (1)
Tags (2)
1 Solution
44 Views
Contributor II

Hello Alice,

I was able to program the flash memory. It was because the axf file generated wasn't the correct one. After fixing the compilation errors, I was able to get a working axf file and was able to program with no issues.

Thanks

View solution in original post

4 Replies
45 Views
Contributor II

Hello Alice,

I was able to program the flash memory. It was because the axf file generated wasn't the correct one. After fixing the compilation errors, I was able to get a working axf file and was able to program with no issues.

Thanks

View solution in original post

44 Views
Contributor II

I tried to program it again, now I am getting this error

Ni: LPCXpresso RedlinkMulti Driver v8.2 (Sep 5 2016 10:12:38 - crt_emu_cm_redlink.exe build 725)
Pc: ( 0) Reading remote configuration
Pc: ( 5) Remote configuration complete
Wc: ============= SCRIPT: flashconnect.scp =============
Wc: Simple flash connect script
Wc: Index = 1
Wc: Manufacturer = Code Red - Red Probe+
Wc: Description = Red Probe+ A
Wc: Serial Number = FTXDPY22A
Wc: VID:PID = 21BD:0003
Wc: Path = Not Available
Wc: 1
Wc: Server error: #0xB2 (report to NXP)
Wc: DpID = 2BA01477
Wc: ============= END SCRIPT ===========================
Xe:
Nc: Probe Firmware: Red Probe+ A (Code Red - Red Probe+)
Nc: Serial Number: FTXDPY22A
Nc: VID:PID: 21BD:0003
Nc: USB Path:
Pc: ( 30) Emulator Connected
Xc:
Pc: ( 40) Debug Halt
Pc: ( 50) CPU ID
Nc: Emu(0): Connected&Reset. DpID: 2BA01477. CpuID: 410FC230. Info: <None>
Nc: Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.
Nc: inspected v.2 On-chip Flash Memory LPC175x_6x_512.cfx
Nc: image 'LPC175x_6x (512K) Jun 21 2016 11:53:23'
Nc: NXP: LPC1768 Part ID: 0x00000000
Pc: ( 65) Chip Setup Complete
Nt: Connected: was_reset=false. was_stopped=true
Cf:v LPCXpressoPro Full License - Unlimited
Pc: ( 70) License Check Complete
Et:57: ELF file has no initialized code/data: 'C:\Users\rjakati\Desktop\2I-Main-MultiLanguage_V4.1\2I-Main-MultiLanguage_V4.1\LCD_4.3\Release\LCD_4.3.axf'
Pc: (100) Target Connection Failed

0 Kudos
44 Views
NXP TechSupport
NXP TechSupport

Hello Ravitej Jakati,

How about download a simple project ?

And what about the whole part number of your chip.

BR

Alice

0 Kudos
44 Views
Contributor II

Hi Alice,

it's an LPC1768ADC

Thank you

0 Kudos