This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Serialization - porting application to another MCU

Hello,

I'm trying to use nRF51 as bluetooth communication module for LPC1769 communicating over SPI, so I use connectivity firmware in nRF51 and now I'm trying to access it from the LPC.

But porting is really tricky - I tried to remove most of the SDK sources, according to serialized ble_app_beacon Makefile, but the sources still include headers like "nrf51_soc.h", which require core_cm0.h and causes type conflicts with similiar headers from LPC.

Is there some guide on that, or can you give me a hint on what sources are really needed for serialization to work?

I looked at the SDK docs, but there is just a list of drivers that need to be rewritten. I have also found some similiar example for STM32, but it looks pretty old.

Parents
  • The documentation we have on porting a serial application can be found here that I guess you have seen already. Unfortunately, it's difficult to make a definite guide on how to port these applications as it depends on the HW implemantion on the particular application controller.

    Basically what needs to be done is to port the modules listed in the documentation, and also replace the CMSIS CORE used on the nRF51 (core_cm0.h, arm_startup_nrf51.s,etc.) with those for LPC1769.

Reply
  • The documentation we have on porting a serial application can be found here that I guess you have seen already. Unfortunately, it's difficult to make a definite guide on how to port these applications as it depends on the HW implemantion on the particular application controller.

    Basically what needs to be done is to port the modules listed in the documentation, and also replace the CMSIS CORE used on the nRF51 (core_cm0.h, arm_startup_nrf51.s,etc.) with those for LPC1769.

Children
No Data
Related