boards: antmicro: add support for the Myra SiP Baseboard
Add support for the Antmicro's Myra SiP Baseboard. The board uses Antmicro's Myra SiP which integrates STM32G491XX MCU and its SoC configuration. Signed-off-by: Jakub Wasilewski <jwasilewski@internships.antmicro.com> Signed-off-by: Filip Kokosinski <fkokosinski@antmicro.com>
This commit is contained in:
parent
1ce3898832
commit
3a8c954021
18 changed files with 717 additions and 0 deletions
5
soc/antmicro/myra/Kconfig
Normal file
5
soc/antmicro/myra/Kconfig
Normal file
|
@ -0,0 +1,5 @@
|
|||
# Copyright (c) 2024 Antmicro <www.antmicro.com>
|
||||
# SPDX-License-Identifier: Apache-2.0
|
||||
|
||||
config SOC_MYRA
|
||||
select SOC_STM32G491XX
|
18
soc/antmicro/myra/Kconfig.soc
Normal file
18
soc/antmicro/myra/Kconfig.soc
Normal file
|
@ -0,0 +1,18 @@
|
|||
# Copyright (c) 2024 Antmicro <www.antmicro.com>
|
||||
# SPDX-License-Identifier: Apache-2.0
|
||||
|
||||
# The Myra is technically a SiP (System-in-Package) that consists of
|
||||
# the STM32G491REI6 MCU and additional components like FRAM. So for
|
||||
# Antmicro Myra SiP Baseboard the STM32G491XX SoC is to be indicated as
|
||||
# the build target, but since the Myra SiP is what a user can actually
|
||||
# see on a board, using only STM32G491XX in the Zephyr build
|
||||
# infrastructure might be confusing. That's why in the top level of SoC
|
||||
# definitions (for user-configurable options in Kconfig, for example)
|
||||
# the Myra term is used and STM32G491XX underneath.
|
||||
config SOC_MYRA
|
||||
bool
|
||||
help
|
||||
Antmicro Myra System-in-Package
|
||||
|
||||
config SOC
|
||||
default "myra" if SOC_MYRA
|
2
soc/antmicro/myra/soc.yml
Normal file
2
soc/antmicro/myra/soc.yml
Normal file
|
@ -0,0 +1,2 @@
|
|||
socs:
|
||||
- name: myra
|
Loading…
Add table
Add a link
Reference in a new issue