esp32-linux-build
esp32-linux-build copied to clipboard
jcmvbkbc
Native USB board
Hi, I bought a esp32 board which has no UART connection it only works on the native USB. It gets flashed easily but when I open putty with 115200 baud rate and the correct COM port it is stuck at the very first line "ESP-ROM:esp32s3-20210327". Can someone help me out please?
it only works on the native USB
If you mean that USB serial you can assign a default console to it by placing file cmdline with the following text: earlycon=esp32s3acm,mmio32,0x60038000 console=ttyGS3 debug rw root=mtd:rootfs no_hash_pointers into build/build-buildroot-esp32s3/target/etc, running keep_buildroot=y keep_rootfs=y keep_bootloader=y keep_toolchain=y nice ./rebuild-esp32s3-linux-wifi.sh and letting it reflash the board including the etc partition.
Just to confirm I am talking about the usb connection which is directly connected to the gpio 19 and gpio 20.
Edit: i figured out the cmdline file thingy will try that and tell you how that goes.
On Sat, 1 Jun 2024, 3:45 pm Max Filippov, @.***> wrote:
it only works on the native USB
If you mean that https://www.espressif.com/sites/default/files/documentation/esp32-s3_technical_reference_manual_en.pdf#section.33 USB serial you can make it default console by placing file cmdline with the following text: earlycon=esp32s3acm,mmio32,0x60038000 console=ttyGS3 debug rw root=mtd:rootfs no_hash_pointers into build/build-buildroot-esp32s3/target/etc, running keep_buildroot=y keep_rootfs=y keep_bootloader=y keep_toolchain=y nice ./rebuild-esp32s3-linux-wifi.sh and letting it reflash the board including the etc partition.
— Reply to this email directly, view it on GitHub https://github.com/jcmvbkbc/esp32-linux-build/issues/8#issuecomment-2143392855, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVGC5FZOXIDRGF7YP5BE4LTZFGNL3AVCNFSM6AAAAABIUALKYWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBTGM4TEOBVGU . You are receiving this because you authored the thread.Message ID: @.***>
Hey If it's not much trouble could you tell me step by step on how I should do it. I did it multiple times and the outcome is the same. I am pretty sure I am doing something silly which I cannot find right now. :(
On Sat, 1 Jun 2024 at 18:08, Aaryav Behl @.***> wrote:
Just to confirm I am talking about the usb connection which is directly connected to the gpio 19 and gpio 20.
And if it's not a problem can you tell me how should I change that line because I am fairly new to it.
On Sat, 1 Jun 2024, 3:45 pm Max Filippov, @.***> wrote:
it only works on the native USB
If you mean that https://www.espressif.com/sites/default/files/documentation/esp32-s3_technical_reference_manual_en.pdf#section.33 USB serial you can make it default console by placing file cmdline with the following text: earlycon=esp32s3acm,mmio32,0x60038000 console=ttyGS3 debug rw root=mtd:rootfs no_hash_pointers into build/build-buildroot-esp32s3/target/etc, running keep_buildroot=y keep_rootfs=y keep_bootloader=y keep_toolchain=y nice ./rebuild-esp32s3-linux-wifi.sh and letting it reflash the board including the etc partition.
— Reply to this email directly, view it on GitHub https://github.com/jcmvbkbc/esp32-linux-build/issues/8#issuecomment-2143392855, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVGC5FZOXIDRGF7YP5BE4LTZFGNL3AVCNFSM6AAAAABIUALKYWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBTGM4TEOBVGU . You are receiving this because you authored the thread.Message ID: @.***>
You can do it like that with your current directory where the build scripts are:
$ echo 'earlycon=esp32s3acm,mmio32,0x60038000 console=ttyGS3 debug rw root=mtd:rootfs no_hash_pointers' > build/build-buildroot-esp32s3/target/etc/cmdline
$ keep_buildroot=y keep_rootfs=y keep_bootloader=y keep_toolchain=y nice ./rebuild-esp32s3-linux-wifi.sh
It will run part of the build, prepare new file system images and prompt you to press enter when it's ready to flash the bootloader, kernel and rootfs and again for etc.
Awesome!! Will try it as soon as possible and get back to you.
Thank you so much
On Sun, 2 Jun 2024, 5:05 am Max Filippov, @.***> wrote:
You can do it like that with your current directory where the build scripts are:
$ echo 'earlycon=esp32s3acm,mmio32,0x60038000 console=ttyGS3 debug rw root=mtd:rootfs no_hash_pointers' > build/build-buildroot-esp32s3/target/etc/cmdline $ keep_buildroot=y keep_rootfs=y keep_bootloader=y keep_toolchain=y nice ./rebuild-esp32s3-linux-wifi.sh
It will run part of the build, prepare new file system images and prompt you to press enter when it's ready to flash the rootfs and again for etc.
— Reply to this email directly, view it on GitHub https://github.com/jcmvbkbc/esp32-linux-build/issues/8#issuecomment-2143628772, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVGC5F2CDCJCWTN455URCDDZFJLCNAVCNFSM6AAAAABIUALKYWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBTGYZDQNZXGI . You are receiving this because you authored the thread.Message ID: @.***>
I did everything as instructed but it is getting stuck at a different output.
pp rom version: e7ae62f
That looks odd. I only see
pp rom version: e7ae62f
net80211 rom version: e7ae62f
on the UART. On the USB serial the default build prints the following for me:
linux ptr = 0x42120000
vectors ptr = 0x4037c000
If you don't see that there's something wrong with the bootloader. Are you able to get output from any other firmware flashed into your board? Can you point me to a spec for your board?
This was getting print when I installed without any modification to the cmdline but after that it was stuck there
On Mon, 3 Jun 2024, 8:51 am Max Filippov, @.***> wrote:
That looks odd. For me the default build prints the following on the USB serial:
linux ptr = 0x42120000 vectors ptr = 0x4037c000
If you don't see that there's something wrong with the bootloader. Are you able to get output from any other firmware flashed into your board? Can you point me to a spec for your board?
— Reply to this email directly, view it on GitHub https://github.com/jcmvbkbc/esp32-linux-build/issues/8#issuecomment-2144204531, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVGC5F55DIWYBWLJH7MI5FTZFPOMNAVCNFSM6AAAAABIUALKYWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBUGIYDINJTGE . You are receiving this because you authored the thread.Message ID: @.***>
Okay so I get this exact output "linux ptr = 0x42120000
vectors ptr = 0x4037c000" from USB serial when I don't modify any cmdline file and gets stuck at that output only. Its a custom board so it is tough to find the specs for it but I can tell you the chip info. This is the output I get when I run the esptool.py chip_id
Connecting... Detecting chip type... ESP32-S3 Chip is ESP32-S3 (QFN56) (revision v0.2) Features: WiFi, BLE, Embedded PSRAM 8MB (AP_3v3) Crystal is 40MHz MAC: f0:f5:bd:4b:f4:0c Uploading stub... Running stub... Stub running... Warning: ESP32-S3 has no Chip ID. Reading MAC instead. MAC: f0:f5:bd:4b:f4:0c Hard resetting via RTS pin...
I suspect that this is the same issue that was found here. Please rebuild your image with the updated bootloader and let me know if there's still no console output.
All right I will try it and give you update
On Thu, 13 Jun 2024, 2:27 pm Max Filippov, @.***> wrote:
I suspect that this is the same issue that was found here https://github.com/jcmvbkbc/esp32-linux-build/issues/9#issuecomment-2165040817. Please rebuild your image with the updated bootloader and let me know if there's still no console output.
— Reply to this email directly, view it on GitHub https://github.com/jcmvbkbc/esp32-linux-build/issues/8#issuecomment-2165049065, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVGC5F5MZHYQD4TO3ZPKL6TZHFNI3AVCNFSM6AAAAABIUALKYWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRVGA2DSMBWGU . You are receiving this because you authored the thread.Message ID: @.***>