Replies: 1 comment 2 replies
-
Excellent question, we don't seem to have good examples in the codebase yet. Most modules under platforms/*/bsp/ seem to either implement C functions or they exist for one platform only. We should certainly try to use common interfaces in BSP modules though, some examples will be added soon. We're currently working on adding IEepromDriver implementations for both platforms, for instance. Meanwhile, please take a look at the AbstractCANTransceiver implementations (CanFlex2Transceiver for S32, SocketCanTransceiver for POSIX). They aren't implementing a BSP interface literally (the interface isn't located under libs/bsw/bsp/), but the basic idea is the same. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, I’ve been exploring the project and looking into the NXP S32K1 port (specifically this BSP implementation). From what I can see, it seems like each platform’s BSP defines its own set of low-level driver APIs for peripherals.
I’m wondering if there’s any plan to define a set of generic BSP low level interfaces for common peripheral drivers, with the goal of improving application portability across platforms. Essentially, something like consolidating the APIs into a common libs/bsp structure that could be implemented per platform.
Is my understanding correct that the current approach is platform-specific per BSP, or is there an intention to evolve toward a more unified interface in the future?
Thanks
Beta Was this translation helpful? Give feedback.
All reactions