• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 286 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

bsp_cfg.h and bsp_cfg.inc, are they supposed to hold the same values pinmux registers??

siddharth.k53961
Prodigy 160 points
Other Parts Discussed in Thread: OMAPL138

Hi,

I have modified the bsp_cfg.h file to enable the pin-mux which would suit our custom made OMAPL138 based board. But lately i have realized that there is another file bsp_cfg.inc which has something to do with the boot loader settings.how do I modify the values in this so that I customise the BSP for our board.

  1. I have used the pin-mux utility to modfiy the bsp_cfg.h file.
  2. I do not know if I would have to modify the bsp_cfg.inc also.
  3. I have noticed that the valuesof the "BSP_SYSCONF_PINMUX#" registers in the bsp_cfg.inc are not exactly equal to the ones corresponding to the bsp_cfg.h ,even in the BSP provided along with the board.

Queries:-

  1. Are the values in the bsp_cfg.inc ,loaded first (along with the primary boot loader) before the whole OS loads.(NK.bin loads) and sets the values corresponding to the bsp_cfg.h??
  2. If possible can you please exactly explain the implications of changes in each of the files (.h and .inc) on the bootloader(.nbo) and image(NK.bin) of the WINCE??

 

Regards,

Siddharth

  • 0
    Genius 5470 points

    The inc files are used by assembly files whereas the h files are used by C files. In general they should be in sync but you will have to search, on an individual basis,  to see if they are actually referenced anywhere. Most of the the pin multiplxing is done by the C startup code so the defines in the H file will be used for the most part even for the bootloader.