[riot-notifications] [RIOT-OS/RIOT] Renode improvements (#15427)
notifications at github.com
Mon Nov 16 23:54:00 CET 2020
> > Are you already done or still working on it?
> I don't think I need to change much to 'improve' the Renode integration. My main goal was to have the EFM32 working again. There are still some issues in the emulation code, but that is out of scope of the PR.
> I haven't decided yet if I want to move all CPU and board files (*.repl) files to `dist/tools/renode`, or keep them in `board/<name>/dist/renode` and `cpu/<name>/dist/renode`. What do you think?
That is also an issue I ran into. Still not completely sure. If you take a look into `boards/stm32f4discovery/dist/board.repl`, the pattern `board` and `cpu` pattern has its limitations. It fits better into the RIOT structure though. It also makes more sense to have everything for the board at one place and for the cpu at one place. My problem is just that RIOTs stm32_common code doesn't fit into the model of Renodes. I guess `board/<name>/dist/renode` and `cpu/<name>/dist/renode` makese more sense, even though that means more work in restructuring the .repl files.
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the notifications