LPCXpresso IDEのトピックRe: Source for toolchain?

Source for toolchain?

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

Content originally posted in LPCWare by Lucretia on Mon Mar 14 11:15:26 MST 2011
Hi,

We have started a project and are looking at using the LPC1769 Xpresso board as an ARM target. I know I can use GCC to target the board, but need to know if the the relevant patches are in the GDB source trees for the USB link.

We are in the process of designing an OS kernel in Ada so will require a custom toolchain; I have already built an ARM targeted GNAT which can target cortex-m3 no problem.

Is there anything I need to know before committing and buying a board?

We are developing under Linux.

Thanks,
Luke.

Re: Source for toolchain?

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

Content originally posted in LPCWare by igorsk on Mon Mar 14 12:00:55 MST 2011
CodeRed use a custom GDB server and it's not under GPL. It also seems NXP doesn't plan to open the LPC-Link for third party debuggers.
However, I expect you should be able to use standard GDB to connect to CodeRed's server.

Re: Source for toolchain?

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

Content originally posted in LPCWare by Lucretia on Mon Mar 14 12:07:39 MST 2011

Quote: igorsk
CodeRed use a custom GDB server and it's not under GPL. It also seems NXP doesn't plan to open the LPC-Link for third party debuggers.
However, I expect you should be able to use standard GDB to connect to CodeRed's server.

I take it the server is a object file you can link with?

Re: Source for toolchain?

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

Content originally posted in LPCWare by CodeRedSupport on Tue Mar 15 00:31:10 MST 2011

Quote: Lucretia
I take it the server is a object file you can link with?

No. The server is a standalone executable, that implements the GDB Remote protocol. This is a standard interface, defined by GDB that allows GDB to connect a very wide range of debug targets, and is how (just about) every vendor provides an interface to GDB.

Re: Source for toolchain?

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

Content originally posted in LPCWare by Lucretia on Tue Mar 15 07:52:03 MST 2011

Quote: CodeRedSupport
No. The server is a standalone executable, that implements the GDB Remote protocol. This is a standard interface, defined by GDB that allows GDB to connect a very wide range of debug targets, and is how (just about) every vendor provides an interface to GDB.

Ok, that's fine.

Another question, I have ordered the board, but I have just had a thought: Can we develop and upload outside of the IDE?

Thanks,
Luke.

Re: Source for toolchain?

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

Content originally posted in LPCWare by CodeRedSupport on Tue Mar 15 08:37:19 MST 2011

Quote: Lucretia

Another question, I have ordered the board, but I have just had a thought: Can we develop and upload outside of the IDE?

Yes. All the standard command line tools are provided. We also provide a FAQ on debugging from the command line, using GDB:
http://support.code-red-tech.com/CodeRedWiki/UsingGDB

Re: Source for toolchain?

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

Content originally posted in LPCWare by jharwood on Tue Mar 15 10:18:45 MST 2011

Quote: CodeRedSupport
Yes. All the standard command line tools are provided. We also provide a FAQ on debugging from the command line, using GDB:
http://support.code-red-tech.com/CodeRedWiki/UsingGDB

Found a typo in the that Wiki page too

where [I]debug driver[/I] is one of: 
[B]crt_emu_lpc11_13[/B] (for LPC11xx or LPC13xx parts)

should be:

where [I]debug driver[/I] is one of: 
 [B]crt_emu_lpc11_13_nxp[/B] (for LPC11xx or LPC13xx parts)

Re: Source for toolchain?

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

Content originally posted in LPCWare by CodeRedSupport on Wed Mar 16 08:35:15 MST 2011

Quote: jharwood
Found a typo in the that Wiki page too

where [I]debug driver[/I] is one of: 
[B]crt_emu_lpc11_13[/B] (for LPC11xx or LPC13xx parts)

should be:

where [I]debug driver[/I] is one of: 
 [B]crt_emu_lpc11_13_nxp[/B] (for LPC11xx or LPC13xx parts)

Thanks for reporting. Now fixed.

Regards,
CodeRedSupport