Skip to content

Test all board kconfig models for hello-world #17349

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
wants to merge 9 commits into from
Closed

Test all board kconfig models for hello-world #17349

wants to merge 9 commits into from

Conversation

MrKevinWeiss
Copy link
Contributor

Contribution description

Just a test...

Testing procedure

Issues/PRs references

@github-actions github-actions bot added Area: CI Area: Continuous Integration of RIOT components Area: examples Area: Example Applications labels Dec 7, 2021
@MrKevinWeiss MrKevinWeiss added CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR and removed Area: CI Area: Continuous Integration of RIOT components Area: examples Area: Example Applications labels Dec 7, 2021
@github-actions github-actions bot added Area: CI Area: Continuous Integration of RIOT components Area: examples Area: Example Applications labels Dec 7, 2021
@github-actions github-actions bot added Area: boards Area: Board ports Area: cpu Area: CPU/MCU ports Area: Kconfig Area: Kconfig integration Platform: ARM Platform: This PR/issue effects ARM-based platforms and removed Area: examples Area: Example Applications labels Dec 8, 2021
@leandrolanzieri leandrolanzieri mentioned this pull request Dec 8, 2021
Merged
@github-actions github-actions bot added Area: drivers Area: Device drivers Area: SAUL Area: Sensor/Actuator Uber Layer Area: tests Area: tests and testing framework labels Dec 8, 2021
@MrKevinWeiss
Copy link
Contributor Author

Hmmm,
still working on things (using the CI to show the errors)

It seems

  • pyboard - has the same binary size but different hashes
  • nucleo-wl55jc - has different a binary size, probably clock
  • lora-e5-dev - also different sizes but same modules

nucleo-l011k4 requires using picolibc (although I don't really like how that is done...) so I need a way to force the board to select it instead of the default nanolibc.

@MrKevinWeiss MrKevinWeiss force-pushed the test/kconfig/testallboards branch from 6a510ff to fed3175 Compare December 9, 2021 11:12
@fjmolinas
Copy link
Contributor

nucleo-l011k4 requires using picolibc (although I don't really like how that is done...) so I need a way to force the board to select it instead of the default nanolibc.

What do you mean?

@fjmolinas
Copy link
Contributor

Maybe @aabadie can take a look at 804ff50? I know he had worked on the initial wl port as well, maybe he has this somewhere in a branch?

@MrKevinWeiss
Copy link
Contributor Author

nucleo-l011k4 requires using picolibc (although I don't really like how that is done...) so I need a way to force the board to select it instead of the default nanolibc.

What do you mean?

This

@MrKevinWeiss
Copy link
Contributor Author

OK probably I should be splitting this out into other PRs.

The issues with nucleo-wl55jc, lora-e5-dev and stm32mp157c-dk2 are the kconfig clock model, this must be done first and I will take a look at @aabadie work before progressing.

The nucleo-l011k4 and stm32f030f4-demo should be easy, just needs to force picolib (maybe in a nicer way)

The stm32f723e-disco has some obvious issues, though I haven't looked into it too much.

The stm32f429i-disco is probably just missing the stdio_usb_cdc_acm thing.

As I am out of time for now I will be picking up the work later. If anyone fixes this stuff before I get to it please ping me :)

@MrKevinWeiss
Copy link
Contributor Author

MrKevinWeiss commented Dec 10, 2021 •
edited
Loading

The following boards are still not passing:

  • stm32mp157c-dk2 (clocks)
  • stm32f3discovery (? size diff)
  • stm32f030f4-demo (? size diff)
  • pyboard (? size the same)
  • nucleo-l011k4 (picolib)
  • lora-e5-dev (clocks)
  • nucleo-wl55jc(clocks)

@leandrolanzieri leandrolanzieri mentioned this pull request Dec 10, 2021
Merged
@MrKevinWeiss MrKevinWeiss force-pushed the test/kconfig/testallboards branch from fabd4c3 to a68f53b Compare December 10, 2021 15:18
@fjmolinas
Copy link
Contributor

Needs a rebase now!

@MrKevinWeiss
Copy link
Contributor Author

closing as the test did its job!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@kaspar030 kaspar030 Awaiting requested review from kaspar030 kaspar030 is a code owner

@cgundogan cgundogan Awaiting requested review from cgundogan

@jia200x jia200x Awaiting requested review from jia200x jia200x is a code owner

@leandrolanzieri leandrolanzieri Awaiting requested review from leandrolanzieri leandrolanzieri is a code owner

@aabadie aabadie Awaiting requested review from aabadie aabadie is a code owner

@fjmolinas fjmolinas Awaiting requested review from fjmolinas

@MichelRottleuthner MichelRottleuthner Awaiting requested review from MichelRottleuthner MichelRottleuthner is a code owner

@smlng smlng Awaiting requested review from smlng

@DipSwitch DipSwitch Awaiting requested review from DipSwitch

@vincent-d vincent-d Awaiting requested review from vincent-d

Assignees
No one assigned
Labels
Area: boards Area: Board ports Area: CI Area: Continuous Integration of RIOT components Area: cpu Area: CPU/MCU ports Area: drivers Area: Device drivers Area: Kconfig Area: Kconfig integration Area: SAUL Area: Sensor/Actuator Uber Layer Area: tests Area: tests and testing framework CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR Platform: ARM Platform: This PR/issue effects ARM-based platforms
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@MrKevinWeiss @fjmolinas