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

[gen3] fixes .particle/toolchains/gcc-arm/5.3.1/bin/objdump: not found issues in WB #1996

Merged
merged 2 commits into from
Jan 13, 2020

Conversation

avtolstoy
Copy link
Member

Problem

For some reason building things out of main with WB is broken now (at least with deviceOS@source) and fails with not being able to find objdump:

/bin/sh: 1: /home/avtolstoy/.particle/toolchains/gcc-arm/5.3.1/bin/objdump: not found
/bin/sh: 1: /home/avtolstoy/.particle/toolchains/gcc-arm/5.3.1/bin/objdump: not found

And consequently failing to link:

/home/avtolstoy/.particle/toolchains/gcc-arm/5.3.1/bin/../lib/gcc/arm-none-eabi/5.3.1/../../../../arm-none-eabi/bin/ld: Insufficient room for .data and .bss sections
/home/avtolstoy/.particle/toolchains/gcc-arm/5.3.1/bin/../lib/gcc/arm-none-eabi/5.3.1/../../../../arm-none-eabi/bin/ld: region `SRAM’ overflowed by 1196 bytes
collect2: error: ld returned 1 exit status

Solution

The makefile that generates some linker RAM definiitions in runtime for Gen 3 user modules is including invalid support makefile, which doesn't correcty define all the tools that use GCC_PREFIX.

Steps to Test

Build a simple app with deviceOS@source

Example App

N/A

References

N/A


Completeness

  • User is totes amazing for contributing!
  • Contributor has signed CLA (Info here)
  • Problem and Solution clearly stated
  • Run unit/integration/application tests on device
  • Added documentation
  • Added to CHANGELOG.md after merging (add links to docs and issues)

@avtolstoy avtolstoy added the bug label Jan 13, 2020
@avtolstoy avtolstoy added this to the 1.5.0-rc.1 milestone Jan 13, 2020
@busticated
Copy link
Contributor

looks good. i tested within workbench - here are the steps:

  1. configure workbench to use the deviceOS@source toolchain (docs)
  2. run the Particle: Create Project command and follow the prompts
  3. when your new project loads, copy simple firmware into your ./src/<project-name>.ino file:
void setup() {
    pinMode(D7, OUTPUT);
}

void loop() {
    digitalWrite(D7, HIGH);
    delay(1000);
    digitalWrite(D7, LOW);
    delay(1000);
}
  1. from VSCode's main menu, select "Terminal" > "Run Task..."
  2. from the list presented, select the Particle: Compile application (local) task

when running against the develop branch, i see the objdump: not found error. when running against this branch (fix/gen3-build-objdump-not-found), i no longer see the error 👍

@avtolstoy avtolstoy merged commit 59a125d into develop Jan 13, 2020
@avtolstoy avtolstoy deleted the fix/gen3-build-objdump-not-found branch January 13, 2020 18:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants