Reply by then...@rocketmail.com●January 7, 20142014-01-07
Since Code Red was acquired by NXP, these proprietary restrictions seem to be
disappearing. For example, LPCXpresso now supports CMSIS-DAP, so can be used
with any probe that uses that open interface.
> On Mon, Jan 6, 2014 at 3:52 AM,
wrote:
>
> > Why don't use user LPCXpresso from NXP? The IDE is free (based on
> > Eclipse and GCC) and comes with lots of examples. The debug probe
> > (LPC-Link or
> > LPC-Link2) are cheap (about €20)
>
> Last I checked, LPC-Link2 was closed source proprietary and supported only
> Code-Red.
The original LPC-Link was closed. LPC-Link 2 can run CMSIS-DAP and is,
therefore, completely open.
> However, the link does seem to indicate that the
firmware can now be
> reflashed to use the Segger J-link and CMSIS-DAP protocols, both of which
> seem to support gdbserver.
>
> Does anyone have any experience doing this?
Reply by Peter Johansson●January 7, 20142014-01-07
On Mon, Jan 6, 2014 at 3:52 AM, wrote:
> Why don't use user LPCXpresso from NXP? The IDE
is free (based on Eclipse
> and GCC) and comes with lots of examples. The debug probe (LPC-Link or
> LPC-Link2) are cheap (about 20)
Last I checked, LPC-Link2 was closed source proprietary and supported
only Code-Red.
However, the link does seem to indicate that the firmware can now be
reflashed to use the Segger J-link and CMSIS-DAP protocols, both of
which seem to support gdbserver.
Reply by then...@rocketmail.com●January 6, 20142014-01-06
Why don't use user LPCXpresso from NXP? The IDE is free (based on Eclipse
and GCC) and comes with lots of examples. The debug probe (LPC-Link or
LPC-Link2) are cheap (about €20)
Reply by paco...@yahoo.com●January 3, 20142014-01-03
Ok i am going to try that velocity.
I check the jlink there are very expensive . Are you using open ocd?
I was looking for the arm-usb-ocd from olimex in linux no success.
I also found that pirate bus has swd.
At the end I think is more easy try something like stm32f because has usb.
I have maple board and is easy and good. But is big and expensive for small
proyects.
So I miss attiny23 with assambler for small proyects. So I try lpc1313 with a
homemade barebone but looks very hard to run a simple hello world.
Reply by kjoehass●January 3, 20142014-01-03
--- In l..., wrote: > And yes swd but no supported by linux.
Not true, I use a JLink to run SWD in linux all of the time.
By the way, if the LPC1313 shares its clocking with the LPC1343 then the normal
system clock frequency is 72MHz, not 70MHz. The internal RC oscillator runs at
12MHz but the CMSIS system initialization uses the PLL to multiply that up.
Reply by paco...@yahoo.com●January 3, 20142014-01-03
Yes I pull up the reset and p0.1 when I disconect the serial cable and attach
the voltage to restart. Unfortunally this is a lpc1313 no usb and no jtag.
And yes swd but no supported by linux.
I am looking for another hello world to compare the clock configuration.
Reply by rtstofer●January 3, 20142014-01-03
--- In l..., wrote: >
> Yes I install all the toolchain and no error in compilation or dowload to the
chip.
> But does not work. I believe that was a mistake starting with lpc1313 because
does not have jtag. So is hard to know what is happen inside.
> lpc21isp has a good comunication with the lpc1313 so I believe that the chip
is ok.
> But after finish dowload and reset there is no blinking.
>
> I check inside the memory map from manual agains the includes and the linker
is ok. the register io structure are ok.
>
> So the only posibility is an error at the clock configuration. I am new in
cortex m3. I am migrating from avr. So the clock configuration is hard for me. I
do not touch the clock configuration at "hello world" example so I believe that
the clock is 70mhz.
> So I download with the command:
>
> lpc21isp -control -verify -bin blink.bin /dev/serial 115200 70000
>
> finish with no error.
>
> but I believe that the last number 70000 is changing someting at clock
configuration.
> Or the chip was unable to find a valid program at the flash.
>
So, you held P0.1 and P0.3 at 0V during reset to get into the UART version of
the boot loader. Did you have both of these lines high when you reset to run?
I noticed the Olimex board has pull-up resistors on these lines.
You could also try the USB version of the bootloader by pulling P0.1 low during
reset with P0.3 high. The chip will implement a mass storage device and all you
do is drop the .bin file onto the virtual drive. That's pretty slick!
Assuming, of course, that your board has the USB connector. The User Manual
discusses a fairly big problem with the USB bootloader and Windows. I
didn't see a discussion about using this approach with Linux.
The Olimex board for the LPC1343 has a JTAG header (shared with SWD) but not
many IDEs support it. According to Olimex, Rowley is about the only one. But
that may be old information.
Reply by paco...@yahoo.com●January 2, 20142014-01-02
Yes I install all the toolchain and no error in compilation or dowload to the
chip.
But does not work. I believe that was a mistake starting with lpc1313 because
does not have jtag. So is hard to know what is happen inside.
lpc21isp has a good comunication with the lpc1313 so I believe that the chip is
ok.
But after finish dowload and reset there is no blinking.
I check inside the memory map from manual agains the includes and the linker is
ok. the register io structure are ok.
So the only posibility is an error at the clock configuration. I am new in
cortex m3. I am migrating from avr. So the clock configuration is hard for me. I
do not touch the clock configuration at "hello world" example so I believe that
the clock is 70mhz.
So I download with the command:
but I believe that the last number 70000 is changing someting at clock
configuration.
Or the chip was unable to find a valid program at the flash.
Reply by rtstofer●January 2, 20142014-01-02
--- In l..., wrote: >
> Hi
> Is there some blinking hello world for lpc1313?
>
> I try http://vsdev.me/notes/cortex_cmsis/
> and download with lcp21isp.
>
> But there is no blinking. So I try to compare with another.
>
> I am using gnu tools
>
> Thank you in advance for your help.
>
Did you install the Linux version of the toolchain? When using command-line
tools, I prefer Linux. If the toolchain includes an IDE like Rowley or Keil, I
prefer Windows. I can use Eclipse on either platform.
Anyway, I installed the Linux version, git'd the templates and built the
included file (main.c) using the given Makefile. In other words, I didn't
do ANYTHING except follow the yellow brick road from vsdev.me.
The program compiled without error, the .map file looks right and I'm
hoping that the given code is correct because I don't have an LPC13xx to
work with.
