Sign In | Register |
0

Error building the LPC1788_OEM

Issue Report - Created by william on 6/13/2016 3:53:30 PM
Actions

william

Posted
4 years ago

I get this error when I try to build the CW-version of the SDK:

cannot find entry symbol reset_handler; defaulting to 00007000

Looking  through the project files, the message makes sense, the vector table is missing (file LPC177x_8x_Startup.s) .  I tried to use one from one of my projects, but I have FreeRTOS installed which has specific vector names which the linker also then complains about.  Any ideas?

Tyler

DZX Support
Posted
4 years ago

Which project is giving this error? HelloWorld? All of them?

The evaluation version does not include source code to rebuild the SDK library. Only the demo projects will build as they just link against the SDK library. The SDK library contains the file mcu_start.s, which defines the vector table.

Since we've done business before and if you're trying to build or debug the SDK library, I can email you a full source version for evaluation if you'd like?


-Tyler

william

Posted
4 years ago

Thanks Tyler,

I was having trouble with the original bootloader code from a couple of years ago.  I managed to get this going, so no  need for the SDK source.  Would there be any advantage on using the SDK bootloader over the one you wrote in 2014?  It works well on the LPC1788 chip we use.  Is the SDK bootloader interface compatible with the HID C# interface developed in 2014?  


Tyler

DZX Support
Posted
4 years ago

Bill,

The newer bootloaders that are built atop the SDK follow the device firwmare update (DFU) specification provided by the USB-IF (official spec - http://www.usb.org/developers/docs/devclass_docs/DFU_1.1.pdf). Following the standard allows us to offer developers a clear interface to the bootloader with other operating systems besides Windows, such as Linux and OSX.

The original HID bootloader (from 2014) is a homemade protocol over HID. The original C# library for this is not compatible with any of the newer USB communications within the SDK. There aren't any missing features per se, but the HID link is quite slow compared to the newer implementation.

Mostly, the latest USB device stack also allows us to expand beyond just a generic connection. The new architecture allows for implementing any type of interface (e.g. mass storage, composite etc).


Let me know if you have any further questions.

-Tyler

Reply