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

Automatically generate .uf2 files anytime we generate a .hex file for nrf52 #4370

Merged
merged 3 commits into from
Aug 2, 2024

Commits on Aug 2, 2024

  1. Automatically generate .uf2 files anytime we generate a .hex file for…

    … nrf52
    
    * Automatically generate .uf2 files (which are often used by nrf52 bootloaders for installing
    app loads) anytime we generate a new hex file.  This tool takes very little time to run and it is handy
    for development
    
    * Remove an old custom target I had tried to add to autogen uf2 files (that never worked)
    
    Build output now looks like:
    
    $ pio run --environment tracker-t1000-e
    Processing tracker-t1000-e (board: tracker-t1000-e; platform: platformio/nordicnrf52@^10.5.0; framework: arduino)
    ...
    Generating UF2 file
    Converting to uf2, output size: 1395200, start address: 0x27000
    Wrote 1395200 bytes to /home/kevinh/development/meshtastic/firmware/.pio/build/tracker-t1000-e/firmware.uf2
    Building .pio/build/tracker-t1000-e/firmware.zip
    Zip created at .pio/build/tracker-t1000-e/firmware.zip
    =================================================================================== [SUCCESS] Took 9.33 seconds ===================================================================================
    
    Environment      Status    Duration
    ---------------  --------  ------------
    tracker-t1000-e  SUCCESS   00:00:09.327
    =================================================================================== 1 succeeded in 00:00:09.327 ===================================================================================
    geeksville committed Aug 2, 2024
    Configuration menu
    Copy the full SHA
    35b653f View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    f970c46 View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    1c77f7f View commit details
    Browse the repository at this point in the history