boards/e180-zg120b-tb: add support #15487
Conversation
basilfx
requested review from
aabadie,
cgundogan,
fjmolinas,
jia200x,
leandrolanzieri,
MichelRottleuthner,
miri64,
MrKevinWeiss and
smlng
as code owners
basilfx
added
Area: boards
basilfx
force-pushed
the
feature/ebyte_e180
branch
3 times, most recently
from
ee73005 to
ddeb15b
Compare
There was a problem hiding this comment.
Thank you, works like a charm!
I can now confirm that it's the shoddy socket of my debug adapter that makes flashing those boards a pain (had similar issues as with the nRF52 boards from ebyte), but once I managed to flash it (wiggling the cables in the socket helped) I could flash riotboot with #15493 and flashing via riotboot works well too.
I hope we can use this to push forward the radio driver.
| select HAS_PERIPH_RTT | ||
| select HAS_PERIPH_TIMER | ||
| select HAS_PERIPH_UART | ||
| select HAS_PERIPH_UART_MODECFG |
There was a problem hiding this comment.
HAS_PERIPH_UART_MODECFG should be a CPU feature
(hm but this is the same for all efm32 boards, can also be moved in a separate cleanup PR)
There was a problem hiding this comment.
If added to the CPU features, doesn't that automatically add a dependency on the UART peripheral?
There was a problem hiding this comment.
No, it just means that the CPU implements this feature.
This way we can extend the API without having to implement it for all platforms at once.
|
Unrelated to this board, but is it normal that the RTC resets on |
Never thought about that, but yes: https://www.silabs.com/documents/public/application-notes/AN0005-EFM32-RTC.pdf |
basilfx
force-pushed
the
feature/ebyte_e180
branch
from
ddeb15b to
b62bbcf
Compare
|
Please squash. |
basilfx
force-pushed
the
feature/ebyte_e180
branch
from
b62bbcf to
777b519
Compare
basilfx
force-pushed
the
feature/ebyte_e180
branch
from
777b519 to
cb50c1a
Compare
|
Thanks! |
Contribution description
This PR adds support for the Ebyte E180-ZG120B-TB. It's a cheap board that houses a EFM32MG1B SoC with radio.
The board is very similar to the IKEA TRADFRI modules and the SLTB001A. It uses the EFM32 drivers. Mapped peripherals is limited to UART only, since the board does not 'expose' any I2C and/or SPI pins. This board features are limited, but the Radio makes it interested (but depends on #8569).
I have noticed that the board datasheet and SoC datasheet are wrong. Some of the LEDs on the board aren't even connected, and they certainly don't line up with the actual EFM32 chip. I verified this by de-lidding the SoC and probe with a multimeter.
The board has a serial-to-usb converter. It does not have a programming interface, but I just used JLink to connect it (these pins are correct on the board's silk screen).
Testing procedure
Run CI tests on the board.
Issues/PRs references
None