Having a look at the actual commands being used by PlatformIO is pretty easy:
Instead of clicking Build or Upload, open the Advanced folder and select Verbose Build or Verbose Upload.
This will show you all raw commands such as esptool.py commands that are being run.
When trying to connect to a USB device, you see an error like
[Errno 13] Permission denied: '/dev/ttyUSB0'
and the USB connection can’t be established.
On Debian & Ubuntu, the /dev/ttyUSBx and /dev/ttyACMx devices are owned by the dialout group. Therefore, the solution is to add your user to the dialout group:
sudo usermod -a -G dialout $USER
After that, you need to logout completely and login again (if in doubt, reboot your computer)!
While you can sometimes quickly solve this issue by running whatever command you want to use as root using sudo, this is not a recommended solution since it will allow the program you’re calling full access to the entire computer – not just access restricted to the USB device. Therefore, this approach poses a significant security risk and additionally, some programs don’t work properly when called using sudo.
The recommended way is to install the current version using pip since the version installed using apt might be out of date:
sudo pip install esptool
After that, you can use esptool.py – note that you need to call it as esptool.py, not just as esptool!
In case you are missing pip , install python3-dev using apt:
sudo apt -y install python3-pip
If you want to connect an USB device such as a 3D printer mainboard to your Raspberry Pi 4 using the USB-C connector as opposed to the larger USB-A connector, you need to first configure the Raspberry Pi kernel to use host mode for the USB-C connector.
sudo modprobe -r dwc2 && sudo dtoverlay dwc2 dr_mode=host && sudo modprobe dwc2
This method has the advantage of not requiring a reboot.
Edit /boot/config.txt and add
dtoverlay=dwc2,dr_mode=host
at the end of the file (in the [all] section). Then
reboot
The best way to flash Marlin via PlatformIO onto the LPC1768 MCU on a BTT SKR v1.4 board is to insert an SD card into it, connect the computer via USB and use the mbed as upload_protocol.
In order to do this, edit ini/lpc176x.ini from within Visual Studio Code and add the following new code to [env:LPC1768]:
upload_protocol = mbed upload_port=/media/uli/A87B-A154/
with upload_port being the directory where the SD card is mounted (while you can do this using an SD card reader, it is so much easier by just connecting the BTT SKR v1.4 via USB directly to your computer, allowing both serial port and SD card access at the same time).
Full example of the [env:LPC1768] section:
[env:LPC1768]
platform = ${common_LPC.platform}
extends = common_LPC
board = nxp_lpc1768
upload_protocol = mbed
upload_port=/media/uli/A87B-A154/In the PlatformIO menu, choose LPC1768/Upload. There is no special configuration for the BTT SKR v1.4 but of course you need to configure Configuration.h etc correctly – see https://www.makenprint.uk/3d-printing/3d-printing-guides/skr-v1-4-configuration-h-marlin-2-setup-part-2/
After uploading, press the reset button on the Board to apply the firmware update. You can use picocom to connect to your printer, see How to connect to your 3D printer using picocom, e.g.:
picocom -b 115200 /dev/ttyACM0 --imap lfcrlf --ech
Enter M115 to check if you have correctly updated the fiwa
You might need to manually re-mount the SD card using your file manager after a firmware update in order to enabled PlaformIO doing another update.
In order to instal tailscale, on any Ubuntu version, you can use the official tailscale install command:
sudo apt -y install curl apt-transport-https curl -fsSL https://tailscale.com/install.sh | sh
libcamera-vid --width 1920 --height 1080 -f -t 10000000000
-t 10000000000 means to run for 10000000000 milliseconds (almost 4 months)
While trying to capture an image using raspistill, you see the following error message
ERROR: the system should be configured for the legacy camera stack
and no image is being produced
libcameraRecent versions of Raspbian use libcamera instead of the broadcom legacy camera API. You can capture an image using libcamera-still similarly to raspistill:
libcamera-still -o test.jpg
If you absolutely need raspistill specifically to work, you can still enable the legacy camera API using rpi-config:
sudo raspi-config
Go to:
and choose Yes to enable the legacy camera API.
On the Pi, run
libcamera-vid -t 0 --width 1920 --height 1080 --codec h264 --inline --listen -o tcp://0.0.0.0:8888
On the client, run
vlc tcp/h264://192.168.1.185:8888/
where 192.168.1.185 is the IP address of the Raspberry Pi.
The ESP32S2 has two 8-bit DACs.
The CHIP_PU (Chip PowerUp) pin on ESP32 family processors such as the ESP32S2 is equivalent to the EN (enable) or ~RST pin on other microcontrollers.
When CHIP_PU is pulled high (i.e. to 3.3V), the ESP32 is enabled and will run the firmware.
When CHIP_PU is pulled low (i.e. to GND), the ESP32 is disabled and shut down and will not run the firmware.
In other words, in most applications you want to connect a 10kOhm resistor from CHIP_PU to 3.3V and – if needed – a reset button from the CHIP_PU pin to GND. You can not operate the ESP32S2 without a pullup resistor . This is clearly stated in the ESP32S2 datasheet, section 2.2:
Note: Do not leave the CHIP_PU pin floating.
On the ESP32S2-WROOM-I module, the CHIP_PU is directly connected to the module’s EN pin wut
Source: ESP32-S2 datasheet
Source: ESP32-C3 datasheet
The ESP32-C3 has 400 kBytes of integrated SRAM (16 kbytes cache).
Source: ESP32-C3 datasheet
void myTimerInterrupt() {
// TODO Your code goes here
// The following functions may be useful here:
// Timer3.start(); // Start counting & clear counter
// Timer3.stop(); // => stop counting but do not clear counter
// Timer3.restart(); // => clear counter
// Timer3.resume(); // => Start, without clearing counter
}
void setup()
{
Timer3.initialize(20000);
Timer3.attachInterrupt(myTimerInterrupt);
Timer3.start();
}
You can use attachInterupt() with CHANGE to trigger on both RISING and FALLING flanks.
#define INTERRUPT_PIN 13 // Choose any pin with interrupt functionality here.
void myInterrupt() {
// TODO Your code goes here.
}
void setup() {
attachInterrupt(digitalPinToInterrupt(INTERRUPT_PIN), myInterrupt, CHANGE);
}
In setup(), use
attachInterrupt(digitalPinToInterrupt(23), myInterrupt, RISING);
to configure the interrupt on Teensy Pin 23 on the RISING edge.
Add this function, which will be called during the interrupt:
void myInterrupt() {
// Your code goes here
}
While flashing an STM32 using st-flash using a command like
st-flash write build/firmware.bin 0x8000000
you see an error message like
2022-02-12T01:31:34 ERROR flash_loader.c: flash loader run error 2022-02-12T01:31:34 ERROR common.c: stlink_flash_loader_run(0x8000000) failed! == -1
See below for a full error log
Most likely your STM32 is locked (readout protection). Use OpenOCD to unlock it, see How to unlock STM32F0x using OpenOCD for an example. Adjust to your STM32 family as needed.
st-flash logst-flash 1.6.1 2022-02-12T01:31:34 INFO common.c: F0xx small: 4 KiB SRAM, 16 KiB flash in at least 1 KiB pages. file build/mom.bin md5 checksum: da211df7131de9de15f3b6c7a96176dd, stlink checksum: 0x000d0d03 2022-02-12T01:31:34 INFO common.c: Attempting to write 11108 (0x2b64) bytes to stm32 address: 134217728 (0x8000000) 2022-02-12T01:31:34 INFO common.c: Flash page at addr: 0x08000000 erased 2022-02-12T01:31:34 INFO common.c: Flash page at addr: 0x08000400 erased 2022-02-12T01:31:34 INFO common.c: Flash page at addr: 0x08000800 erased 2022-02-12T01:31:34 INFO common.c: Flash page at addr: 0x08000c00 erased 2022-02-12T01:31:34 INFO common.c: Flash page at addr: 0x08001000 erased 2022-02-12T01:31:34 INFO common.c: Flash page at addr: 0x08001400 erased 2022-02-12T01:31:34 INFO common.c: Flash page at addr: 0x08001800 erased 2022-02-12T01:31:34 INFO common.c: Flash page at addr: 0x08001c00 erased 2022-02-12T01:31:34 INFO common.c: Flash page at addr: 0x08002000 erased 2022-02-12T01:31:34 INFO common.c: Flash page at addr: 0x08002400 erased 2022-02-12T01:31:34 INFO common.c: Flash page at addr: 0x08002800 erased 2022-02-12T01:31:34 INFO common.c: Finished erasing 11 pages of 1024 (0x400) bytes 2022-02-12T01:31:34 INFO common.c: Starting Flash write for VL/F0/F3/F1_XL core id 2022-02-12T01:31:34 INFO flash_loader.c: Successfully loaded flash loader in sram 2022-02-12T01:31:34 ERROR flash_loader.c: flash loader run error 2022-02-12T01:31:34 ERROR common.c: stlink_flash_loader_run(0x8000000) failed! == -1 stlink_fwrite_flash() == -1
You can use st-flash like this to flash a firmware file to the STM32:
st-flash write build/firmware.bin 0x8000000
openocd -f interface/stlink-v2.cfg -f target/stm32f0x.cfg -c "init" -c "halt" -c "stm32f1x lock 0" -c "reset halt" -c "exit"
This will activate flash readout protection level 1 which means you won’t be able to readout or re-write the flash. You can still perform a chip erase which will clear the readout protection – for example to flash a new firmware.