LPCopen for ngx lpc1857 Header Board

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

LPCopen for ngx lpc1857 Header Board

764 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by dsidlauskas on Wed Feb 19 19:52:52 MST 2014
Is there a version of LPCopen planned that will support the NGX lpc1857 header board?

Thanks,

Dave
Labels (1)
0 Kudos
Reply
4 Replies

757 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by dsidlauskas on Wed Feb 26 11:59:23 MST 2014
Kevin,

Thanks for the response.

Dave
0 Kudos
Reply

757 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by wellsk on Wed Feb 26 10:44:48 MST 2014
Hi Dsidlauskas,

Trying to support all different variants of boards takes a lot of time, so we tend to focus on a specific set of boards. When the original NGX board was released - it was the NGX1830 and NGX4330 boards, so the board layer code for those were developed for the NGX1830 and NGX4330 boards. From what I understand now, there are also 1857 and 4357 versions of this board with internal FLASH (and likely different sized internal RAM).

At this moment, there are no plans to port LPCopen to the 1857 and 4357 variants of the NGX boards. But depending on the number of users, that may change in the future.

For now, we can offer the board porting guide which gives an overview of the porting steps for the board layer code (http://www.lpcware.com/content/faq/how-do-i-port-lpcopen-new-baord).
If the changes between the 1830 and 1857 variants are small (just using a different LPC chip) and most of the used pins are the same, the port should be fairly easy. It might be as simple as setting up the FLASH timing to the existing code.

If you want to use existing projects for the 1830 with the 1857, you'll have to tweak the selected device in the project settings (which should automatically adjust the memory maps) and you might also have to select a different programming algorithm (internal FLASH instead of SPI FLASH).
0 Kudos
Reply

757 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by dsidlauskas on Thu Feb 20 10:53:29 MST 2014
Thanks for taking the time to respond to my post.

I guess I wasn't very clear in posting my question. The only expectation I have for NXP is that they provide good customer service. I don't expect them to provide board support for any particular vendors board, and to expect boards.c from NXP for a custom board is ridiculous on its face.

However, since lpcopen has supported a similar NGX board in the past, I thought it was a fair question.

Thanks again for your response.

NXP TECH SUPPORT: Do you have an answer for my original post?

0 Kudos
Reply

757 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by TheFallGuy on Thu Feb 20 01:48:10 MST 2014
The whole point of LPCOpen is that it is meant to be easily ported across different boards. It says:


Quote:

The core library is divided up into three sections:
    Chip Driver Layer - Drivers that are tailored and optimized for a specific device or family
    Board Layer - Board specific functions and low level setup code
    Examples - Chip familiy specific examples for peripherals, interfaces, libraries, etc.


So you should just need to change the "Board layer" for your board.

You can't expect NXP to support every board on the market, including any custom boards that you may develop.
0 Kudos
Reply