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

Unable to find size and start point in file eboot.elf ? #7602

Closed
5 of 6 tasks
dominikheinz opened this issue Sep 17, 2020 · 3 comments
Closed
5 of 6 tasks

Unable to find size and start point in file eboot.elf ? #7602

dominikheinz opened this issue Sep 17, 2020 · 3 comments

Comments

@dominikheinz
Copy link

dominikheinz commented Sep 17, 2020

Basic Infos

  • This issue complies with the issue POLICY doc.
  • I have read the documentation at readthedocs and the issue is not addressed there.
  • I have tested that the issue is present in current master branch (aka latest git).
  • I have searched the issue tracker for a similar issue.
  • If there is a stack dump, I have decoded it.
  • I have filled out all fields below.

Additional Information

This issue is related to the version used by EspHome under the hood.
I like to cross reference this issue, as it seems to be an Arduino problem, rather than an EspHome one.
Please see: esphome/issues#1476

Platform

  • Hardware: ESP8266
  • Core Version: Latest of EspHome
  • Development Env: EspHome
  • Operating System: HassOS (Linux)

Settings in IDE

  • Module: Generic ESP8266 Module
  • Flash Mode: Unknown/Default
  • Flash Size: Unknown/Default of Generic ESP8266
  • lwip Variant: Unknown
  • Reset Method: Unknown
  • Flash Frequency: Unknown
  • CPU Frequency: Unknown
  • Upload Using: Irrelevant, process fails during linking (Doesn't reach upload stage)
  • Upload Speed: Irrelevant, process fails during linking (Doesn't reach upload stage)

Problem Description

Generating a binary for Generic ESP8266 in EspHome causes a crash during linking (Unable to find size and start point in file eboot.elf)
See this screenshot for more information as well as the issue I linked above:

err

MCVE Sketch

This is the sketch used in EspHome. The sketch is valid, linking of the binary fails, as shown in the screenshot.

esphome:
  name: smartplug1
  platform: ESP8266
  board: esp01_1m

wifi:
  ssid: censored
  password: censored
  
  manual_ip:
    static_ip: 192.168.1.195
    gateway: 192.168.1.1
    subnet: 255.255.255.0

  ap:
    ssid: censored
    password: censored

api:

logger:

ota:

web_server:
  port: 80

binary_sensor:
  - platform: gpio
    pin:
      number: GPIO0
      mode: INPUT_PULLUP
      inverted: True
    name: "Sonoff S20 Button"
  - platform: status
    name: "Sonoff S20 Status"


switch:
  - platform: gpio
    name: "Sonoff S20 Relay"
    pin: GPIO12

output:
  # Register the green LED as a dimmable output ....
  - platform: esp8266_pwm
    id: s20_green_led
    pin:
      number: GPIO13
      inverted: True

light:
  # ... and then make a light out of it.
  - platform: monochromatic
    name: "Sonoff S20 Green LED"
    output: s20_green_led

Steps to reproduce:

  1. Install HassOS
  2. Install EspHome plugin
  3. Try to compile the yaml script linked above
  4. Observe the crash

Debug Messages

Not available

@earlephilhower
Copy link
Collaborator

You have a shared library installation as shown in your log, see the "Error loading shared libraries..." message. That means you're not actually completing any compiles so you're not going to have a valid ELF to convert to BIN in. I suggest working with the PlatformIO repo/gitter or the HassOS (I assume it's some minimal custom Linux so might not have many needed .SOs to do lots of things like compiling, etc.).

@panakos
Copy link

panakos commented Dec 21, 2022

I have the same issue but without shared library installation error

@panakos
Copy link

panakos commented Dec 24, 2022

Citrix Workspace was causing the issue. I updated Citrix and problem gone!

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

No branches or pull requests

3 participants