Most recent activity
-
- 12 comments
- 7,963 views
-
I realised I had an old-ish esptool so I updated, no change.
I tried qio and that resulted in it rebooting constantly, eg
rst:0x10 (RTCWDT_RTC_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:QIO, clock div:3 load:0x3fff0018,len:4 load:0xd532060c,len:642933257 1162 mmu set 00010000, pos 00010000 1162 mmu set 00020000, pos 00020000 1162 mmu set 00030000, pos 00030000 1162 mmu set 00040000, pos 00040000 1162 mmu set 00050000, pos 00050000 1162 mmu set 00060000, pos 00060000 1162 mmu set 00070000, pos 00070000 1162 mmu set 00080000, pos 00080000 1162 mmu set 00090000, pos 00090000 ets Jun 8 2016 00:22:57 rst:0x10 (RTCWDT_RTC_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:QIO, clock div:3 load:0x3fff0018,len:4 load:0xd532060c,len:642933257 1162 mmu set 00010000, pos 00010000 1162 mmu set 00020000, pos 00020000 1162 mmu set 00030000, pos 00030000 1162 mmu set 00040000, pos 00040000 1162 mmu set 00050000, pos 00050000 1162 mmu set 00060000, pos 00060000 1162 mmu set 00070000, pos 00070000 1162 mmu set 00080000, pos 00080000 ~1162 mmu set 00090000, pos 00090000 ets Jun 8 2016 00:22:57
I also tried lowering the SPI clock to 26MHz and doing and erase & reprogram but no dice.
-
OK I used dio, like so..
/Users/oconnd1/Documents/Arduino/hardware/espressif/esp32/tools/esptool.py --chip esp32 \ --port /dev/cu.usbserial-DN02MPA4 \ --baud 921600 \ --after hard_reset write_flash \ -z \ --flash_mode dio \ --flash_freq 40m \ --flash_size detect \ 0x1000 bootloader.bin \ 0x8000 partitions_espruino.bin \ 0x10000 espruino_1v99_esp32.bin
Although I flashed MicroPython with..
/Users/oconnd1/Documents/Arduino/hardware/espressif/esp32/tools/esptool.py --chip esp32 \ --port /dev/cu.usbserial-DN02MPA4 \ --baud 921600 \ --after hard_reset write_flash \ -z \ --flash_mode dio \ --flash_freq 40m \ --flash_size detect \ 0x1000 ~/Downloads/esp32-20180808-v1.9.4-443-gc1c798fbc.bin
and that worked.
I'll try qio tomorrow for Espruino tomorrow and see how I go, thanks.
-
Hi,
I flashed a SparkFun ESP32 Thing with Espruino (specifically espruino_1v99_esp32.bin) however I just get junk out of it.If I reset I see the bootloader (I assume) print some stuff then I get junk eg..
[Maelstrom 16:47] ~ >cu -l /dev/cu.usbserial-DN02MPA4 -s 115200 Connected. ets Jun 8 2016 00:22:57 rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) ets Jun 8 2016 00:22:57 rst:0x10 (RTCWDT_RTC_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:0x3fff0018,len:4 load:0x3fff001c,len:2364 load:0x40078000,len:0 load:0x40078000,len:10880 entry 0x40078c4c ���1Il���
I tried a few different baud rates (9600, 19200, 38400, 57600, 115200, 230400, 921600) and none of them produced anything sensible except for the boot loader at 115200.
Any help appreciated, thanks.
BTW I flashed this board with MicroPython and it worked so I think the board is OK.
-
OK, I was wrong, if I power it off for long enough I get..
[auxxoconnd1m1 10:40] ~/projects/Espruino >python scripts/stm32loader.py -p /dev/cu.usbserial -Vevw ./espruino_1v70_hystm32_24_ve.bin Open port /dev/cu.usbserial, baud 115200 Reading data from ./espruino_1v70_hystm32_24_ve.bin *** Get command Bootloader version: 0x22 Available commands: ['0x0', '0x1', '0x2', '0x11', '0x21', '0x31', '0x43', '0x63', '0x73', '0x82', '0x92'] Bootloader version 0x22 *** GetID command Chip id 0x414, STM32F1, performance, high-density Traceback (most recent call last): File "scripts/stm32loader.py", line 579, in <module> cmd.cmdEraseMemory() File "scripts/stm32loader.py", line 242, in cmdEraseMemory if self.cmdGeneric(0x43): File "scripts/stm32loader.py", line 137, in cmdGeneric return self._wait_for_ack(hex(cmd)) File "scripts/stm32loader.py", line 98, in _wait_for_ack raise CmdException("Chip replied with a NACK during %s" % info) __main__.CmdException: Chip replied with a NACK during 0x43
-
Also, I just noticed that it says NACK during 0x2 but when I first ran it (without verbose) I got
[auxxoconnd1m1 10:35] ~/projects/Espruino >python scripts/stm32loader.py -p /dev/cu.usbserial -evw ./espruino_1v70_hystm32_24_ve.bin Reading data from ./espruino_1v70_hystm32_24_ve.bin Bootloader version 0x22 Chip id 0x414, STM32F1, performance, high-density Traceback (most recent call last): File "scripts/stm32loader.py", line 579, in <module> cmd.cmdEraseMemory() File "scripts/stm32loader.py", line 242, in cmdEraseMemory if self.cmdGeneric(0x43): File "scripts/stm32loader.py", line 137, in cmdGeneric return self._wait_for_ack(hex(cmd)) File "scripts/stm32loader.py", line 98, in _wait_for_ack raise CmdException("Chip replied with a NACK during %s" % info) __main__.CmdException: Chip replied with a NACK during 0x43
I can't reproduce it though.
-
Yes, I followed those instructions but I get..
[auxxoconnd1m1 10:36] ~/projects/Espruino >python scripts/stm32loader.py -p /dev/cu.usbserial -Vevw ./espruino_1v70_hystm32_24_ve.bin Open port /dev/cu.usbserial, baud 115200 Reading data from ./espruino_1v70_hystm32_24_ve.bin *** Get command Bootloader version: 0x22 Available commands: ['0x0', '0x1', '0x2', '0x11', '0x21', '0x31', '0x43', '0x63', '0x73', '0x82', '0x92'] Bootloader version 0x22 Traceback (most recent call last): File "scripts/stm32loader.py", line 561, in <module> chip_id = cmd.cmdGetID() File "scripts/stm32loader.py", line 164, in cmdGetID if self.cmdGeneric(0x02): File "scripts/stm32loader.py", line 137, in cmdGeneric return self._wait_for_ack(hex(cmd)) File "scripts/stm32loader.py", line 98, in _wait_for_ack raise CmdException("Chip replied with a NACK during %s" % info) __main__.CmdException: Chip replied with a NACK during 0x2
I'll take a look at the touchscreen module, thanks :)
-
I tried 1v97 but no luck unfortunately.