Serial Wire Debug Hardware (Crossworks)

Development Boards MicroMod
1

Okay, using the bootloaders for these LPC1xxx devices is just not going to work for me. Unfortunately my FTDI based Olimex programmer doesn’t have what it takes for SWD.

I’m currently using Crossworks, and I’ve done a bit of investigation. It looks like my only option at the moment is the J-Link debugger which is $$$ for me. Googling around, it looks like Paul is planning on adding SWD support for the Luminary Micro devel kit programmer. Also, he’s planning on selling an SWD adapter for FTDI based programmers. I have no idea when these will actually come out.

I’m just looking for confirmation that what I said above is true and/or if there are any other low cost options. I haven’t done a lot of investigation into the tech specs, but it seems to me that SWD is easier to support hardware wise and there would be some nice low cost adapters becoming available soon with the introduction of all these CM3 and CM0 parts with SWD.

Paul mentioned in another post here that he would not be supporting the LPCXpresso hardware, which seems like a shame, since it’s so cheap and should work as a nice SWD programmer for hobbyists.

I’m not in any hurry for this, so I’ll probably be waiting for anything that shows up in the next few months that looks like it has a good performance/price.

2

TheDirty:
Okay, using the bootloaders for these LPC1xxx devices is just not going to work for me. Unfortunately my FTDI based Olimex programmer doesn’t have what it takes for SWD.

I’m currently using Crossworks, and I’ve done a bit of investigation. It looks like my only option at the moment is the J-Link debugger which is $$$ for me. Googling around, it looks like Paul is planning on adding SWD support for the Luminary Micro devel kit programmer. Also, he’s planning on selling an SWD adapter for FTDI based programmers. I have no idea when these will actually come out.

The first batch of devices will be delivered on 15 February.

TheDirty:
I’m just looking for confirmation that what I said above is true and/or if there are any other low cost options. I haven’t done a lot of investigation into the tech specs, but it seems to me that SWD is easier to support hardware wise and there would be some nice low cost adapters becoming available soon with the introduction of all these CM3 and CM0 parts with SWD.

Paul mentioned in another post here that he would not be supporting the LPCXpresso hardware, which seems like a shame, since it’s so cheap and should work as a nice SWD programmer for hobbyists.

There is some debate about how open or closed the LPCXpresso hardware is. I’m in direct contact with NXP about this, but whether we do anything or not is a question I cannot answer at this time. I may have a better idea after my visit to Embedded World this year.[/quote]

3

Thanks Paul. I look forward to seeing what’s available.

4

TheDirty:
Thanks Paul. I look forward to seeing what’s available.

First batch hit our office today, second coming tomorrow.
5

Sorry, I don’t know who Paul is and how he’s related to this product.

Since CrossWorks was mentioned, is this something that Rowley will be selling?

6

SodaAnt:
Sorry, I don’t know who Paul is and how he’s related to this product.

Since CrossWorks was mentioned, is this something that Rowley will be selling?

This is who I am:

http://www.rowleydownload.co.uk/blog/

The first batch of adapters that convert between FTDI-based JTAG adapters and SWD-only LPC1100s are now in our office, so you can use them with CrossWorks.

7

Paul basically is Rowley.

My understanding is yes, they will be selling these. Version 2.0.5 has the SWD option under FT2232 properties. Unfortunately there’s not much more information than that and they haven’t put anything on the website, yet.

Hopefully I will getting one and I’ll put up a review. I’m pretty optimistic about it.

EDIT: Ninja posted by Paul himself.

8

One is on its way to me. I’m designing a little LPC1111 board to try it on.

9

I was going to say that Paul is like Leon, everywhere on the internet I go that’s related to microcontrollers, they both have been there before and probably invented it.

I’ve also made up an LPC1114 and LPC1313 board, I just haven’t etched it yet. I’m assuming the adapter will be using the standard 10pin 0.05" header.

10

I checked with Paul and his adapter mates with the 10-pin Samtec header specified by ARM. There is one on the LPCXpresso board, and it can be used for debugging a different board by cutting a couple of tracks. One has to use the Code Red software, though.

11

Unfortunately the Samtec part doesn’t seem to be available anywhere in singles. I’m just using an unshrouded header for now.

12

I’ve been really sick for the last few days, but my SWD adapter came from Rowley so I etched a board and got it running.

Unfortunately I made a real mistake of ordering QFN chips for both the LPC1313 and LPC1114. I didn’t do my homework on the pinout. I really like QFN, but the only ground on these is the thermal pad underneath the chip, which means you can’t do them without putting a via right under the chip. On a single sided home made board, that’s pretty much a challenge.

I massacred my board trying to get the bottom ground attached. I soldered and removed the chip over a half dozen times trying different ways. I was hoping to just use a lot of solder and a small via hole and heat up a wire and push it into the bottom side of the chip, but it just would not solder in. I finally just drilled a big hole under the chip. Not big enough to remove the bottom pad all together, but easily big enough to allow me to solder to the bottom of the QFN after it was put on. It worked right away and I think I can get away with this fairly easily with the other ones I have.

Here’s pictures of the Rowley SWD adapter for FT2232 JTAG devices. I have successfully connected to the chip with it and I’m just going to start with some hello world stuff. Again, I know my poor devel board I etched is in bad shape. It took a real beating with all my experiments. I even warped it some.

I’m going to have to put Crossworks on my laptop now so I can try some programming from on the couch.

http://www.higginstribe.com/lpc1xxx/swd … wd-001.jpg

http://www.higginstribe.com/lpc1xxx/swd … wd-002.jpg

http://www.higginstribe.com/lpc1xxx/swd … wd-003.jpg

http://www.higginstribe.com/lpc1xxx/swd … wd-004.jpg

13

I’ve got some of the Samtec shrouded headers on order, and cables. I should have them in about a week. They aren’t stock items at Toby Electronics, they have to order tham from Samtec in the USA.

I was going to get PCBs made for the LPC1111s I’ve got, but seeing yours I might make one. They are only available in QFN at present, I didn’t realise that Farnell had the QFP LPC1114 in stock or I’d have bought those.

14

LPC1313 and 1114 have essentially the same pinouts so I’m using the same layout for both. I just put together the 1114 board and it was much easier to do the ground this time.

15

So has anybody “fixed” the LPC13XX.h and LPC11XX.H header files given in NXP’s sample code so they compile under C? For some reason they decided to use anonymous unions in their header to limit it’s usefulness. I was just going to go in and add names to all of them, hoping I didn’t break anything further on, but maybe I’m not the first person this effects.

I know Crossworks has a nice header file of its own. I hate to say it, but I really like the way the registers are grouped in structs in the NXP delivered one; similar to the AT91SAM header files from Atmel.

16

TheDirty:
So has anybody “fixed” the LPC13XX.h and LPC11XX.H header files given in NXP’s sample code so they compile under C? For some reason they decided to use anonymous unions in their header to limit it’s usefulness. I was just going to go in and add names to all of them, hoping I didn’t break anything further on, but maybe I’m not the first person this effects.

I know Crossworks has a nice header file of its own. I hate to say it, but I really like the way the registers are grouped in structs in the NXP delivered one; similar to the AT91SAM header files from Atmel.

We’re considering doing the same. If everybody from day one had CMSIS then it would be great. However, that isn’t the case. And the struct approach doesn’t give you the bits in each of the registers. But I like the fact that it’s not all in a flat namespace.

17

GPIO works fine, but I’m having a hell of a time with the UART. It’s like it’s just not interacting with the actual hardware pins. Nothing comes out and nothing goes in, though according to the debugger everything is working. Loopback mode works correctly, interrupts are being triggered. Everything is working just fine, but I’m not getting any output on the TXD and nothing on the RXD shows up. I GPIO toggled the RXD/TXD pins to make sure they are working P1.6 and P1.7 and they work fine and toggle an LED fine, so I’m kinda lost here. If I can’t find anything by tomorrow, I’ll post the hacked up stripped down code I’m trying to get to work.

18

TheDirty:
GPIO works fine, but I’m having a hell of a time with the UART. It’s like it’s just not interacting with the actual hardware pins. Nothing comes out and nothing goes in, though according to the debugger everything is working. Loopback mode works correctly, interrupts are being triggered. Everything is working just fine, but I’m not getting any output on the TXD and nothing on the RXD shows up. I GPIO toggled the RXD/TXD pins to make sure they are working P1.6 and P1.7 and they work fine and toggle an LED fine, so I’m kinda lost here. If I can’t find anything by tomorrow, I’ll post the hacked up stripped down code I’m trying to get to work.

Did you configure the pin’s function using the appropriate alternate function register?

19

Yes, I’ve change the IOCON for the pins. Sorry, that was more of a lone rant, as I can’t expect any advice without giving more information.

I’m just going to cut and paste the code that I’m working with. It’s a complete mess, because I just started grabbing code out of examples willy-nilly hoping to find out what I missed with my own code. It just send ‘b’ over and over again and toggles a status LED. I can turn on the loopback mode and the different interrupt enables. The 'tempname’s are because I haven’t really decided what to do with the nameless unions in the header file, yet.

#include "LPC13xx.h"                        /* LPC13xx definitions */

#define IER_RBR		0x01
#define IER_THRE 	0x02
#define IER_RLS		0x04

#define IIR_PEND	0x01
#define IIR_RLS		0x03
#define IIR_RDA		0x02
#define IIR_CTI		0x06
#define IIR_THRE	0x01

#define LSR_RDR		0x01
#define LSR_OE		0x02
#define LSR_PE		0x04
#define LSR_FE		0x08
#define LSR_BI		0x10
#define LSR_THRE	0x20
#define LSR_TEMT	0x40
#define LSR_RXFE	0x80

void main( void)
{
  uint32_t Fdiv;
  uint32_t regVal;
  uint32_t dll;
  volatile unsigned int x, y;

  LPC_SYSCON->SYSAHBCLKCTRL |= (1 << 6);  //Enable AHB clock for GPIO
  LPC_GPIO2->DIR |= (0x01 << 0);  // PORT 2 pin 0 set to output
 
  NVIC_DisableIRQ(UART_IRQn);

  LPC_IOCON->PIO1_6 &= ~0x07;    /*  UART I/O config */
  LPC_IOCON->PIO1_6 |= 0x01;     /* UART RXD */
  LPC_IOCON->PIO1_7 &= ~0x07;	
  LPC_IOCON->PIO1_7 |= 0x01;     /* UART TXD */
  /* Enable UART clock */
  LPC_SYSCON->SYSAHBCLKCTRL |= (1<<12);
  LPC_SYSCON->UARTCLKDIV = 0x1;     /* divided by 1 */

  Fdiv = LPC_SYSCON->UARTCLKDIV;
  dll = (((72000000/LPC_SYSCON->SYSAHBCLKDIV)/Fdiv)/16)/9600 ;	/*baud rate */
  LPC_UART->FDR = 0;                             // Fractional divider not used
  LPC_UART->LCR = 0x83;
  LPC_UART->tempname3.DLL = dll;                           // Baud Rate depending on PCLK
  LPC_UART->tempname4.DLM = (dll >> 8);                    // High divisor latch

  LPC_UART->LCR = 0x03;		/* DLAB = 0 */
  LPC_UART->tempname5.FCR = 0x07;		/* Enable and reset TX and RX FIFO. */

//  LPC_UART->MCR |= (0x01<<4);		/* Loopback mode */

  NVIC_EnableIRQ(UART_IRQn);

  LPC_UART->tempname4.IER =  IER_RBR;	/* Enable UART interrupt */
//  LPC_UART->IER = IER_THRE | IER_RLS | IER_RBR;

  while( 1)
  {
    delay_ms( 1000);
    LPC_GPIO2->DATA |= 0x01;
    while ( !(LPC_UART->LSR & LSR_THRE) );
    LPC_UART->tempname3.THR = 'b';
    delay_ms( 1000);
    LPC_GPIO2->DATA &= ~(0x01);
  }
}

void UART_IRQHandler(void)
{
  uint8_t IIRValue, LSRValue;
  uint8_t Dummy = Dummy;

  IIRValue = LPC_UART->tempname5.IIR;
    
  IIRValue >>= 1;			/* skip pending bit in IIR */
  IIRValue &= 0x07;			/* check bit 1~3, interrupt identification */
  if (IIRValue == IIR_RLS)		/* Receive Line Status */
  {
    if (LSRValue & LSR_RDR)	/* Receive Data Ready */			
    {
      Dummy = LPC_UART->tempname3.RBR;
    }
  }
  else if (IIRValue == IIR_RDA)	/* Receive Data Available */
  {
    /* Receive Data Available */
    Dummy = LPC_UART->tempname3.RBR;
  }
  else if (IIRValue == IIR_CTI)	/* Character timeout indicator */
  {
  }
  else if (IIRValue == IIR_THRE)	/* THRE, transmit holding register empty */
  {
  }
  return;
}
20

Okay, I figured it out. You have to turn on the clock for the IO configuration block or some of the IO hardware blocks don’t work.

Now I can toss this crappy code and implement a decent buffered UART lib.

LPC_SYSCON->SYSAHBCLKCTRL |= (1 << 16); //Enable clock for IO configuration block

Also got my LPC1114 working as well.

http://higginstribe.com/uc/lpc1xxx/swd/