LPCXpresso IDE中的主题 Re: Debug interfaces for custom hardware

Debug interfaces for custom hardware

lpcware — Thu, 16 Jun 2016 02:26:57 GMT

Content originally posted in LPCWare by DiBosco on Sun Jun 24 13:21:08 MST 2012
Folks,

LPC-Link now works on my flavour of Linux, which is good news, but if I decide to use the LPC1000 device, what JTAG interfaces can I use for my own target hardware please?

Thanks.

Re: Debug interfaces for custom hardware

lpcware — Thu, 16 Jun 2016 02:26:58 GMT

Content originally posted in LPCWare by Ex-Zero on Sun Jun 24 13:45:12 MST 2012
Would suggest to use SWD with LPC-Link :)

It's working with all my own LPC11xx, LPC13xx, LPC17xx target boards :rolleyes:

Re: Debug interfaces for custom hardware

lpcware — Thu, 16 Jun 2016 02:26:59 GMT

Content originally posted in LPCWare by DiBosco on Sun Jun 24 14:04:08 MST 2012
SWID? I don't want to use LPC-Link, I want a boxed, robust solution that will cope with being slung in a bag and taken out on site.

Re: Debug interfaces for custom hardware

lpcware — Thu, 16 Jun 2016 02:26:59 GMT

Content originally posted in LPCWare by MikeSimmonds on Sun Jun 24 18:37:58 MST 2012
[FONT=Tahoma][SIZE=2]Check [/SIZE][/FONT][FONT=Tahoma][SIZE=2]the Code-Red site for their Red-Probe+ which works with the LPCXpresso IDE.
In the U.K. it costs about 100 squids (GBP).

Alternatively, buy a plastic (ABS) box from RS or Farnell to protect your LPC-Link.
Less than £3!
[/SIZE][/FONT]

Re: Debug interfaces for custom hardware

lpcware — Thu, 16 Jun 2016 02:27:00 GMT

Content originally posted in LPCWare by DiBosco on Mon Jun 25 01:18:17 MST 2012
Thanks, Mike, that looks more like it. It's more about having something robust than pfaffing around trying to save a few quid housing flimsy, cheap interfaces. I'd rather have one that lasts me ages than keep having to replace it.

Re: Debug interfaces for custom hardware

lpcware — Thu, 16 Jun 2016 02:27:01 GMT

Content originally posted in LPCWare by ktownsend on Fri Jun 29 17:14:19 MST 2012

Quote: DiBosco
Folks,

LPC-Link now works on my flavour of Linux, which is good news, but if I decide to use the LPC1000 device, what JTAG interfaces can I use for my own target hardware please?

Thanks.

For starters, it really depends on which LPC1000 since you can't use JTAG with the LPC1100, LPC1200 or LPC1300 chips ... they only include SWD support to keep the core as small as possible and the price tag down. The LPC1700 and LPC1800 chips include both SWD and JTAG support. Honestly, though, SWD is a much more robust choice, and I haven't used JTAG since I stopped using ARM7 chips years back.

If you are using LPCXpresso, CodeRed's own debugger is really the only realistic option for you if you want something in an enclosure, etc. It's pretty reasonably priced as well.

If you are working from the command-line with GDB Server or with other toolchains/IDEs (but then you probably wouldn't be on the LPCXpresso forum?), I'd recommend Segger's J-Link, which supports both SWD and JTAG and comes in a variety of flavours and price tags ... but it doesn't work with the LPCXpresso IDE (it DOES work with Keil uVision, IAR and Crossworks for ARM, as well as GDB on both Linux and Windows).

Re: Debug interfaces for custom hardware

lpcware — Thu, 16 Jun 2016 02:27:02 GMT

Content originally posted in LPCWare by DiBosco on Mon Jul 02 08:46:07 MST 2012
Thanks for the info.

I'm using the LPC11U which, according to the datasheet, has full JTAG. I've used various cut down version of debuggers over the years, Atmel One Wire, Microchip's utterly dire efforts, TI's MSP430 one wire and they are all really poor compared to JTAG. There's just no way a one or two wire inteface can possibly be as good as full JTAG.

I use the really excellent Crossworks and Crossconnect normally, partially because it works on Linux and partly because it's just so damn easy to use. lightweight and fast. However, as I want to use these USB libraries I'll probably be stuck with the slooooooow xpresso Java bloat fest. At least it works on Linux.

If there's no full JTAG, I might well use an STM32 - I have a lot of code for it and even a FreeRTOS port. You can waste so much time with bad tools that you'll never recover with the cheaper price of a micro.

Quote: KTownsend
For starters, it really depends on which LPC1000 since you can't use JTAG with the LPC1100, LPC1200 or LPC1300 chips ... they only include SWD support to keep the core as small as possible and the price tag down. The LPC1700 and LPC1800 chips include both SWD and JTAG support. Honestly, though, SWD is a much more robust choice, and I haven't used JTAG since I stopped using ARM7 chips years back.

If you are using LPCXpresso, CodeRed's own debugger is really the only realistic option for you if you want something in an enclosure, etc. It's pretty reasonably priced as well.

If you are working from the command-line with GDB Server or with other toolchains/IDEs (but then you probably wouldn't be on the LPCXpresso forum?), I'd recommend Segger's J-Link, which supports both SWD and JTAG and comes in a variety of flavours and price tags ... but it doesn't work with the LPCXpresso IDE (it DOES work with Keil uVision, IAR and Crossworks for ARM, as well as GDB on both Linux and Windows).

Re: Debug interfaces for custom hardware

lpcware — Thu, 16 Jun 2016 02:27:02 GMT

Content originally posted in LPCWare by DiBosco on Mon Jul 02 09:42:29 MST 2012
Ach, just been back to read the datasheet. Although the block diagram shows JTAG, this is only boundary scan, not for debugging (it says this in the small print further down.). Good job you pointed this out. Thanks.

Re: Debug interfaces for custom hardware

lpcware — Thu, 16 Jun 2016 02:27:03 GMT

Content originally posted in LPCWare by OXO on Wed Jul 04 07:36:17 MST 2012

Quote: DiBosco
Ach, just been back to read the datasheet. Although the block diagram shows JTAG, this is only boundary scan, not for debugging (it says this in the small print further down.). Good job you pointed this out. Thanks.

Don't worry, the SWD on the 11x is very good.