Skip to content
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.

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

WIP: Add picotool compatible 'binary info' metadata #160

Closed

Conversation

jonathanpallant
Copy link
Contributor

@jonathanpallant jonathanpallant commented Oct 5, 2021

This is a WIP proof of concept. I don't suggest you merge it.

TODO:

  • Move 'binary_info' stuff into a module in the HAL (or maybe a crate of its own?)
  • Make some macros so its easier to put the metadata in your program
  • Instead of making the user create a table of entry references, get the macros to stuff a reference to every entry created into a separate section - that section is then what gets the start/end stuffed into the header.
  • Support pin descriptions

I'd like to see this get to:

binary_info! {
    program_name: "My silly program",
    program_version: env!("CRATE_VERSION"),
};

How you would get pin configuration info from the BSP and into your application is TBD.

Jonathan Pallant (42 Technology) added 3 commits October 11, 2021 11:05
There's also a default in RP2040-HAL to make the examples build.
If you build pico_blinky, picotool can tell you things about the ELF/UF2 output.
@thejpster
Copy link
Member

TIL the paste macro exists. Might be useful here.

@jannic jannic marked this pull request as draft June 13, 2022 07:44
@thejpster
Copy link
Member

Closed in favour of #824

@thejpster thejpster closed this Jul 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants