ucb-bar / baremetal-ide-bsp Goto Github PK

https://github.com/ucb-bar/Baremetal-IDE-bsp/blob/d3d88dc6389835ebd2b4d29713d04200b50a430f/bearlyml/src/bearlyml_hal_gpio.c#L14C1-L19C4

In <chipname>.h file, the on-chip scratchpad region should be named as "#define SCRATCH_BASE" instead of "#define SRAM_BASE" to avoid confusion and be consistent with the linker script.

Currently, we are maintaining 4 chip bsp libraries, in which almost all of the contents are the same. Any bug fix or new feature needs to be synced across all bsp folders, which does not quite make sense.

Instead, the new method is proposed, where we use Python to auto generate bsp codes from a set of template library files. Considering the amount of code needed, this major change can be implemented in several stages:

1. Be able to generate HAL_ library files from a set of template files. The Python program will read library files from the template folder, create a bsp folder, and write the library files to the created bsp folder with proper formatting (e.g. rename the file to include chipname)

2. Be able to generate chip header file (chipname.h) from the chip configuration JSON file. The JSON file will be very similar to the .svd file used by the VSCode debugging environment. It will contain the memory map of the SoC, register map of each peripheral, and the bit map of each peripheral register.

3. Be able to generate the chip configuration JSON file during Chipyard compilation.