-
Notifications
You must be signed in to change notification settings - Fork 100
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
Firmware upload failing with Teensy 4.0, ROS Humble #85
Comments
It is upload problem. It is teensy-cli/platformio issue. I tested with a teensy41 (with the same MCU as teensy40) and got the same issue. The second upload will success. It is not related to linorobot2_hardware project. Building in release mode *** [upload] Error 1 |
Same here, teensy31. Strange that calibration uploaded without errors. I guess, time to move to esp32 then |
Pico2/pico will be better than esp32 to replace teensy with micro-ROS serial transport. esp32 is only good for wifi transport. It is because pico2/pico use the same USB CDC device interface, /dev/ttyACM0, as teensy. There is no need to modify the linorobot2 code. While esp32 use USB Serial bridge device, /dev/ttyUSB0 such as CP2102/CH340 bridge chips, which will be confused with Lidar serial device, /dev/ttyUSBx. We need to modify the code and use by-path device names to assign serial ports. USB CDC device driver works better than USB Serial bridge device. If you will use docker, you should not use esp32. |
Hi, calibration works fine but the firmware upload stopped working (had it previously running fine around November 2023 on the same robot). I saw the suggestions on #35 and also experimented with changing the
lib_deps
in linorobot2_hardware/firmware/platformio.ini to match the different branches (rolling, foxy and humble) but it still fails.Also, I just tried a fresh install, linorobot2_hardware is outside my workspace folder.
Any help is appreciated, thanks.
Here's my lib_deps:
And the output after running
pio run --target upload -e teensy40
:The text was updated successfully, but these errors were encountered: