You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since zephyr also uses device-tree, albeit during compile time. I think making this repo behave more like the linux repo in terms of generating dts will make it easier to add more peripheral configs and board support.
Once make.py spits out both the bitstream and dts we can have the zephyr source use that to generate the firmware. Zephyr can then just have a generic vexriscv target instead of the arty specific one (It is pretty generic already, apart from the dts) .
This just makes adding more custom interfaces easy since that seems to be the main use-case, like adding 6 spi interface to tinyfpga_bx and sacrificing all i2c and all but one uart interface.
The text was updated successfully, but these errors were encountered:
Hi all, this is an enhancement request:
Since zephyr also uses device-tree, albeit during compile time. I think making this repo behave more like the linux repo in terms of generating dts will make it easier to add more peripheral configs and board support.
Once make.py spits out both the bitstream and dts we can have the zephyr source use that to generate the firmware. Zephyr can then just have a generic vexriscv target instead of the arty specific one (It is pretty generic already, apart from the dts) .
This just makes adding more custom interfaces easy since that seems to be the main use-case, like adding 6 spi interface to tinyfpga_bx and sacrificing all i2c and all but one uart interface.
The text was updated successfully, but these errors were encountered: