cederom commented on PR #14267:
URL: https://github.com/apache/nuttx/pull/14267#issuecomment-2411804907

   Thank you @fdcavalcanti !! Works fine :-)
   
   Two minor tweaks to consider:
   1. Put interpreter string on the first line.
   2. Add expected version to error message, see review comment, example 
provided.
   
   Testing on FreeBSD with esptool 4.7.0:
   
   ```
   % ./tools/configure.sh -B esp32-devkitc:nsh
   % gmake -j8
   Create version.h
   LN: platform/board to /XXX/nuttx-apps.git/platform/dummy
   Cloning Espressif HAL for 3rd Party Platforms
   Clone: chip/esp-hal-3rdparty Register: nsh
   Register: sh
   Espressif HAL for 3rd Party Platforms: 
b4c723a119344b4b71d69819019d55637fb570fd
   LD: nuttx
   CP: nuttx.hex
   MKIMAGE: ESP32 binary
   Unsupported esptool version: 4.7.0
   Upgrade using: 'pip install --upgrade esptool' and run 'make' again
   gmake: *** [tools/Unix.mk:558: nuttx] Error 1
   ```
   
   With my suggestion on expected version added:
   ```
   % gmake -j8
   Create version.h
   LD: nuttx
   CP: nuttx.hex
   MKIMAGE: ESP32 binary
   Unsupported esptool version 4.7.0 expected >= 4.8
   Upgrade using: 'pip install --upgrade esptool' and run 'make' again
   gmake: *** [tools/Unix.mk:558: nuttx] Error 1
   ```
   
   With esptool 4.8.1 from venv works fine:
   
   ```
   (venv3.9embedded) gmake -j8
   LD: nuttx
   CP: nuttx.hex
   MKIMAGE: ESP32 binary
   esptool.py -c esp32 elf2image --ram-only-header -fs 4MB -fm dio -ff 40m -o 
nuttx.bin nuttx
   esptool.py v4.8.1
   Creating esp32 image...
   Image has only RAM segments visible. ROM segments are hidden and SHA256 
digest is not appended.
   Merged 1 ELF section
   Successfully created esp32 image.
   Generated: nuttx.bin
   
   (venv3.9embedded) gmake flash
   LD: nuttx
   CP: nuttx.hex
   MKIMAGE: ESP32 binary
   esptool.py -c esp32 elf2image --ram-only-header -fs 4MB -fm dio -ff 40m -o 
nuttx.bin nuttx
   esptool.py v4.8.1
   Creating esp32 image...
   Image has only RAM segments visible. ROM segments are hidden and SHA256 
digest is not appended.
   Merged 1 ELF section
   Successfully created esp32 image.
   Generated: nuttx.bin
   esptool.py -c esp32 -p /dev/cuaU0 -b 115200  write_flash -fs detect -fm dio 
-ff 40m 0x1000 nuttx.bin
   esptool.py v4.8.1
   Serial port /dev/cuaU0
   Connecting..........
   Chip is ESP32-D0WD-V3 (revision v3.0)
   Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding 
Scheme None
   Crystal is 40MHz
   MAC: XXX
   Uploading stub...
   Running stub...
   Stub running...
   Configuring flash size...
   Auto-detected Flash size: 4MB
   Flash will be erased from 0x00001000 to 0x00032fff...
   Compressed 203204 bytes to 74440...
   Wrote 203204 bytes (74440 compressed) at 0x00001000 in 7.0 seconds 
(effective 232.4 kbit/s)...
   Hash of data verified.
   
   Leaving...
   Hard resetting via RTS pin...
   
   (venv3.9embedded) cu -l /dev/cuaU0 -s 115200
   Connected
   ts Jul 29 2019 12:21:46
   
   rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
   configsip: 0, SPIWP:0xee
   clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
   mode:DIO, clock div:2
   load:0x3ffb1f50,len:1004
   ho 0 tail 12 room 4
   load:0x40080000,len:20708
   entry 0x40082610
   *** Booting NuttX ***
   dram: lma 0x00001020 vma 0x3ffb1f50 len 0x3ec    (1004)
   iram: lma 0x00001414 vma 0x40080000 len 0x50e4   (20708)
   padd: lma 0x00006508 vma 0x00000000 len 0x9af0   (39664)
   imap: lma 0x00010000 vma 0x400e0000 len 0x11598  (71064)
   padd: lma 0x000215a0 vma 0x00000000 len 0xea78   (60024)
   dmap: lma 0x00030020 vma 0x3f400020 len 0x29a4   (10660)
   total segments stored 6
   
   NuttShell (NSH) NuttX-12.7.0-RC0
   nsh> uname -a
   NuttX 12.7.0-RC0 cfba4e334a-dirty Oct 14 2024 19:00:57 xtensa esp32-devkitc
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to