LPC11E68 AND SWD

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

LPC11E68 AND SWD

2,629件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by dariush_abbasi868 on Mon Jun 22 23:55:01 MST 2015
Hi every body
I am designed a board by lpc11e68 and I am going to use LpcLink2 as debuging by Lpcexperso .
as I found lpc11e68 ( cortex m0) dosn't work by jtag debuging , so I used to use SWD , swd has 3 pins SWDIO, SWDCLK AND SW0 , I make connection for SWDIO  and CLK  but I am not sur of SWD0  . what about vcc.

flshing led1 in LpcLink2 what it mean .
ラベル(1)
0 件の賞賛
返信
14 返答(返信)

2,541件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Wed Jul 01 00:05:07 MST 2015

Quote: dariush_abbasi868
I have checked hardware several times.


Re-read the FAQ and if you still have problems then post details/schematics of your board design - in particular debug and reset.

Regards,
LPCXpresso Support
0 件の賞賛
返信

2,541件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by dariush_abbasi868 on Tue Jun 30 21:18:01 MST 2015
I tried to change and use IOCON but I can .
first of all
LPC_SYSCON->SYSAHBCLKCTRL |= (1<<16);//IOCON
is OK  , but  LPC_IOCON->   has error .

How I can use it?
0 件の賞賛
返信

2,541件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by dariush_abbasi868 on Sun Jun 28 03:15:39 MST 2015
I have checked hardware several times.
Besides I am sure that my chip ( lpc11e68) is OK because I check it by Flash Magic , I have seen something about IOCON in page 59 in user manual !
Is it necessary to define SWD pin to SWD function ? I mean that maybe I have to enable SWD .   
0 件の賞賛
返信

2,541件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Wed Jun 24 06:03:47 MST 2015
So, you have a hardware problem then. Suggest you fix that.
0 件の賞賛
返信

2,541件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by dariush_abbasi868 on Wed Jun 24 04:21:01 MST 2015

Quote: lpcxpresso-support
Please read this FAQ:
http://www.lpcware.com/content/faq/lpcxpresso/regaining-debug-access

Have you configured your project for LPC11U68?
http://www.lpcware.com/content/faq/lpcxpresso/changing-project-mcu-target

After doing that, make sure you delete your launch configuration before start another debug session:
http://www.lpcware.com/content/faq/lpcxpresso/launch-configuration-menu



Thanks alot , I saw and did all of that particulay Boot into ISP mode and Vector catch=true , but yet It Could not connect to core.
0 件の賞賛
返信

2,541件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Wed Jun 24 01:40:08 MST 2015
Please read this FAQ:
http://www.lpcware.com/content/faq/lpcxpresso/regaining-debug-access

Have you configured your project for LPC11U68?
http://www.lpcware.com/content/faq/lpcxpresso/changing-project-mcu-target

After doing that, make sure you delete your launch configuration before start another debug session:
http://www.lpcware.com/content/faq/lpcxpresso/launch-configuration-menu
0 件の賞賛
返信

2,541件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by dariush_abbasi868 on Wed Jun 24 01:20:55 MST 2015
Sorry for log text , In feuture I will do it by # .

I mean the " WireProtocol = JTAG" not "HAS JTAG" this tell me that  JATG is using  or I am  wrong ?


Quote:
- the target needs booting into ISP mode


Would you please  tell me more about it ?my core is working and I send a file by FLASH MAGIC to it and it is ok , Now I want to in later working use DEBUG  to find my mistakes and make a best application for it .
thanks for your reply
0 件の賞賛
返信

2,541件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Wed Jun 24 00:30:49 MST 2015
1. When postin long strings of text please do it between code tags (the # symbol on the toolbar)
2. SWO Trace is something that has no effect on debugging. When present, it uses an extra pin on the connector
3. "Has JTAG" means that the Debug Probe (LPC-Link2) is capable of supporting JTAG - it is nothing to do with the target
4. "Could not connect to core" could mean several things
- you have not correctly wired up your debug connection
- the target is not powered
- the target is stuck in reset
- the target needs booting into ISP mode
0 件の賞賛
返信

2,541件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by dariush_abbasi868 on Wed Jun 24 00:12:50 MST 2015

Quote:
Of course. SWD provides the same capabilities on all Cortex-Mx based MCUs



So what 's the defference between Debug with Trace and whitout.
I used Cortex-m3 ( specialy LPC1768) for Debug by JTAG , and now I want to use Cortex-m0 (Lpc11e68) for debug by SWD.
I make wiring for SWD but I am warried is it give me that benefit for debug line to line and see code like JTAG .

I checked my wiring several time but when I want to debug by SWD "no connect to core " message shows.

another message that is a bit stange for me is:
redlink>ProbeList
Index = 1
Manufacturer = NXP
Description = LPC-LINK2 REDLINK
VID = 21BD, PID=0006
Path = \\?\hid#vid_21bd&pid_0006&mi_00#7&2461c7c3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
redlink>
redlink>ProbeStatus
Index = 1
Manufacturer = NXP
Description = LPC-LINK2 REDLINK
VID = 21BD, PID=0006
Path = \\?\hid#vid_21bd&pid_0006&mi_00#7&2461c7c3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
IsOpen = FALSE
WireInitialized = FALSE
WireProtocol = JTAG
CoresConfigured = FALSE
PacketSize = 1024
Probe Reference Count = 0
HasSWV = FALSE
HasETM = FALSE
HasJTAG = TRUE
HasSWD = TRUE
Probe Type = REDLINK
redlink>
redlink>
redlink>ProbeList
Index = 1
Manufacturer = NXP
Description = LPC-LINK2 REDLINK
VID = 21BD, PID=0006
Path = \\?\hid#vid_21bd&pid_0006&mi_00#7&2461c7c3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
redlink>
redlink>ProbeStatus
Index = 1
Manufacturer = NXP
Description = LPC-LINK2 REDLINK
VID = 21BD, PID=0006
Path = \\?\hid#vid_21bd&pid_0006&mi_00#7&2461c7c3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
IsOpen = FALSE
WireInitialized = FALSE
WireProtocol = JTAG
CoresConfigured = FALSE
PacketSize = 1024
Probe Reference Count = 0
HasSWV = FALSE
HasETM = FALSE
HasJTAG = TRUE
HasSWD = TRUE
Probe Type = REDLINK
redlink>
redlink>
redlink>
redlink>ProbeStatus
Index = 1
Manufacturer = NXP
Description = LPC-LINK2 REDLINK
VID = 21BD, PID=0006
Path = \\?\hid#vid_21bd&pid_0006&mi_00#7&2461c7c3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
IsOpen = TRUE
WireInitialized = FALSE
WireProtocol = JTAG
CoresConfigured = FALSE
PacketSize = 1024
Probe Reference Count = 0
HasSWV = FALSE
HasETM = FALSE
HasJTAG = TRUE
HasSWD = TRUE
Probe Type = REDLINK
redlink>exit
[Closed]
[Started server]
[Connected on port 3025]
redlink>

I know that it has not JTAG but it shows that it is JTAG and I can not find any place to change it.
0 件の賞賛
返信

2,541件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Tue Jun 23 04:07:00 MST 2015
Of course. SWD provides the same capabilities on all Cortex-Mx based MCUs.
0 件の賞賛
返信

2,541件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by dariush_abbasi868 on Tue Jun 23 02:47:34 MST 2015

Quote:
Cortex-M0 (LPC11E6x) does not support SWO (Trace) capabilities, nor JTAG.


by the way Is it posible for to debug by SWD  and see everything and make breakpoint where I want like Cortex-M3?
0 件の賞賛
返信

2,541件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Tue Jun 23 02:29:14 MST 2015
Cortex-M0 (LPC11E6x) does not support SWO (Trace) capabilities, nor JTAG.
0 件の賞賛
返信

2,541件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by dariush_abbasi868 on Tue Jun 23 02:07:57 MST 2015
Thank you ,
I saw that link and also lpc11e68 datasheet but I can not find JTAG Test Data Output / SWV trace data output (SWO) in lpc11e68 and I am not sure of it yet.
0 件の賞賛
返信

2,541件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Tue Jun 23 00:34:34 MST 2015
Please read the FAQ:
http://www.lpcware.com/content/faq/lpcxpresso/debug-design

The flashing LED means that the LPC-Link firmware is running and responding. It does NOT mean that there is a valid target connected.
0 件の賞賛
返信