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

How to get rid of board support package?

I want to get rid of the board support package, and write my own code to interface with the least complicated drivers for UART, BLE and SPI etc.

If I remove BSP I ifind lots of compile errors if I try use the UART driver. Can I not use some drivers without using bsp too?

Is there any guid to setting up my own project 'from the ground up' without instead trying to strip down an example project that has the BSP woven into it?

Thaks

Parents
  • No there's no guide, you just have to write the code.

    I just looked at app_uart.c, don't see anything in there which has anything to do with BSP, what code were you trying to compile, you just said "the UART driver' which could mean lots of different things? Either way it's easy, you take a copy of the code, you compile it, you find the things which don't compile and you replace them with things that do.

    All the BSP provides is a consistent interface for buttons, pins and LEDs, there's hardly anything in it so removing dependence on it is easy. What compile errors were you finding it hard to remove?

    I treat all the SDK code as example code, very useful example code, but find I can get much better power-optimized and smaller code writing my own. That's probably less-true now than it was back a few revisions of the SDK ago, but I have most everything written now so I use it.

Reply
  • No there's no guide, you just have to write the code.

    I just looked at app_uart.c, don't see anything in there which has anything to do with BSP, what code were you trying to compile, you just said "the UART driver' which could mean lots of different things? Either way it's easy, you take a copy of the code, you compile it, you find the things which don't compile and you replace them with things that do.

    All the BSP provides is a consistent interface for buttons, pins and LEDs, there's hardly anything in it so removing dependence on it is easy. What compile errors were you finding it hard to remove?

    I treat all the SDK code as example code, very useful example code, but find I can get much better power-optimized and smaller code writing my own. That's probably less-true now than it was back a few revisions of the SDK ago, but I have most everything written now so I use it.

Children
Related