Jump to content

myriadcs

New Members
  • Content Count

    52
  • Joined

Everything posted by myriadcs

  1. old EPROMs are not that cheap, it might be cheaper/easier to get brand new PCBs and more modern EEPROMs
  2. All good now, problem as usual was between chair and keyboard... Thanks again!
  3. omg, wrong flasher downloading correct one now...
  4. When I click Flash ESP I got an error Using '/dev/ttyUSB0' as serial port. Unexpected error: expected str, bytes or os.PathLike object, not NoneType I think It should download latest firmware itself, right? I can download one of Firmware from https://fujinet.online/firmware-dl/ but which one? firmware.bin?
  5. I've built regular fujinet-v1 and it's exactly same error
  6. @tschak909 I flash latest firmware (built from git head) and get an error like in post 2. Any idea what I may be missing?
  7. I find that Micro USB cables are one of the most unreliable connections, I have tons of broken one, half-broken and just ephemeral broken...
  8. This time I've used Official Flasher and Downloaded firmware, it flashed ok with different error in logs [16:35:18]ets Jun 8 2016 00:22:57 [16:35:18] [16:35:18]rst:0x3 (SW_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) [16:35:18]configsip: 0, SPIWP:0xee [16:35:18]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 [16:35:18]mode:DIO, clock div:2 [16:35:18]load:0x3fff0018,len:4 [16:35:18]load:0x3fff001c,len:1044 [16:35:18]load:0x40078000,len:8896 [16:35:18]load:0x40080400,len:5828 [16:35:18]entry 0x400806ac
  9. Looks like it was loose cable. I managed to get it recognized and flashed again. 16:09:25.150 > FujiNet 0.5.d5ab7817 2021-09-13 22:48:24 Started @ 5 16:09:25.150 > Starting heap: 4113035 16:09:25.150 > PsramSize 3918339 16:09:25.150 > himem phys 4456448 16:09:25.150 > himem free 4456448 16:09:25.152 > himem reserved 262144 16:09:25.182 > Detected Hardware Version: 1.0 16:09:25.182 > E (708) SPIFFS: mount failed, -10025 16:09:25.184 > Failed to mount SPIFFS partition, err = -1 16:09:25.245 > SD mounted. 16:09:25.245 > fnConfig::load 16:09:25.247 > Load fnconfig.ini from SD 16:09:25.252 > fnConfig::load read 938 bytes from config file 16:09:25.255 > Config file dosn't exist on SPIFFS 16:09:25.255 > Copying SD config file to SPIFFS 16:09:25.257 > copy_file "/fnconfig.ini" -> "/fnconfig.ini" 16:09:25.257 > copy_file failed to open destination 16:09:25.258 > copy_file copied 0 bytes 16:09:25.258 > Failed to copy config from SD 16:09:25.368 > WIFI_EVENT_STA_START 16:09:25.368 > WiFi connect attempt to SSID "MyNetwork" 16:09:25.368 > esp_wifi_connect returned 0 16:09:25.368 > disk UNMOUNT 16:09:25.368 > disk MOUNT 16:09:25.368 > ATR MOUNT 16:09:25.368 > Guru Meditation Error: Core 0 panic'ed (LoadProhibited). Exception was unhandled. 16:09:25.370 > 16:09:25.370 > Core 0 register dump: 16:09:25.370 > PC : 0x401ff180 PS : 0x00060930 A0 : 0x801ff13d A1 : 0x3ffb2fd0 16:09:25.371 > A2 : 0x3ffb3260 A3 : 0x00000000 A4 : 0x00000000 A5 : 0x00000000 16:09:25.372 > A6 : 0x3ff96458 A7 : 0xff000000 A8 : 0x801ff180 A9 : 0x3ffb2fb0 16:09:25.373 > A10 : 0x00000000 A11 : 0x3ffb300c A12 : 0x0000000a A13 : 0x3ffcb190 16:09:25.374 > A14 : 0x00000000 A15 : 0x00000000 SAR : 0x00000017 EXCCAUSE: 0x0000001c 16:09:25.375 > EXCVADDR: 0x00000064 LBEG : 0x4008e221 LEND : 0x4008e231 LCOUNT : 0xfffffffd 16:09:25.376 > 16:09:25.376 > Backtrace:0x401ff17d:0x3ffb2fd0 0x401ff13a:0x3ffb3040 0x400ed48d:0x3ffb3060 0x400ed18a:0x3ffb3090 0x400db276:0x3ffb30b0 0x400db570:0x3ffb30d0 0x400d3e86:0x3ffb30f0 0x400d3f8f:0x3ffb3110 0x4022aa8b:0x3ffb3140 0x400953f1:0x3ffb3160 16:09:25.583 > #0 0x401ff17d:0x3ffb2fd0 in _fseeko_r at /builds/idf/crosstool-NG/.build/xtensa-esp32-elf/src/newlib/newlib/libc/stdio/fseeko.c:116 (discriminator 14) 16:09:25.583 > #1 0x401ff13a:0x3ffb3040 in _fseek_r at /builds/idf/crosstool-NG/.build/xtensa-esp32-elf/src/newlib/newlib/libc/stdio/fseek.c:89 16:09:25.583 > (inlined by) fseek at /builds/idf/crosstool-NG/.build/xtensa-esp32-elf/src/newlib/newlib/libc/stdio/fseek.c:99 16:09:25.583 > #2 0x400ed48d:0x3ffb3060 in DiskTypeATR::mount(__sFILE*, unsigned int) at lib/sio/diskTypeAtr.cpp:195 16:09:25.583 > #3 0x400ed18a:0x3ffb3090 in sioDisk::mount(__sFILE*, char const*, unsigned int, disktype_t) at lib/sio/disk.cpp:239 16:09:25.583 > #4 0x400db276:0x3ffb30b0 in sioFuji::insert_boot_device(unsigned char) at lib/sio/fuji.cpp:1480 16:09:25.583 > #5 0x400db570:0x3ffb30d0 in sioFuji::setup(sioBus*) at lib/sio/fuji.cpp:1500 16:09:25.583 > #6 0x400d3e86:0x3ffb30f0 in main_setup() at src/main.cpp:108 16:09:25.583 > #7 0x400d3f8f:0x3ffb3110 in app_main at src/main.cpp:171 16:09:25.583 > #8 0x4022aa8b:0x3ffb3140 in main_task at /home/user/.platformio/packages/framework-espidf/components/freertos/port/port_common.c:133 (discriminator 2) 16:09:25.583 > #9 0x400953f1:0x3ffb3160 in vPortTaskWrapper at /home/user/.platformio/packages/framework-espidf/components/freertos/port/xtensa/port.c:168 16:09:25.583 > 16:09:25.583 > 16:09:25.583 > ELF file SHA256: e3819770e4ba2b10 16:09:25.583 > 16:09:25.583 > Rebooting... It says Hardware Version 1.0 and indeed that's what it's on board but i think it's already modified with some fixes. There is resistor on SIO connector It's not working but at least something is working, need to figure out what is missing now copy_file failed to open destination so I guess something with SPIFFS partition is not ok (or it's wrong assumption?)
  10. Today I set up new environment, I've built new firmware commit 7f0dca365a658c50bdccc746b5ba0f26338277f0 (HEAD -> master, origin/master, origin/HEAD) Merge: dfc7374e 2d0c9e5d flashed and now my Fujinet is not working. When I connect USB cable all 3 leds blinks and go dark. FN is no longer recognized by computer. I bought that while ago and *I think* it's 1.3 hardware revision. ESP32 itself has following details: ESP-WROVER-B XX0H28 Here is flashing log: Building in debug mode Retrieving maximum program size .pio/build/fujinet-v1-8mb/firmware.elf Checking size .pio/build/fujinet-v1-8mb/firmware.elf Advanced Memory Usage is available via "PlatformIO Home > Project Inspect" RAM: [== ] 21.6% (used 70764 bytes from 327680 bytes) Flash: [=== ] 30.7% (used 1911213 bytes from 6225920 bytes) Configuring upload protocol... AVAILABLE: esp-prog, espota, esptool, ftdi, iot-bus-jtag, jlink, minimodule, olimex-arm-usb-ocd, olimex-arm-usb-ocd-h, olimex-arm-usb-tiny-h, olimex-jtag-tiny, tumpa CURRENT: upload_protocol = esptool Looking for upload port... Use manually specified: /dev/ttyUSB0 Uploading .pio/build/fujinet-v1-8mb/firmware.bin esptool.py v3.1 Serial port /dev/ttyUSB0 Connecting.... Chip is ESP32-D0WD (revision 1) Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None Crystal is 40MHz MAC: b8:f0:09:89:d1:78 Uploading stub... Running stub... Stub running... Changing baud rate to 921600 Changed. Configuring flash size... Auto-detected Flash size: 16MB Flash will be erased from 0x00001000 to 0x00007fff... Flash will be erased from 0x00008000 to 0x00008fff... Flash will be erased from 0x0000e000 to 0x0000ffff... Flash will be erased from 0x00010000 to 0x001e2fff... Flash params set to 0x0240 Compressed 27536 bytes to 16762... Writing at 0x00001000... (50 %) Writing at 0x00007979... (100 %) Wrote 27536 bytes (16762 compressed) at 0x00001000 in 0.5 seconds (effective 467.9 kbit/s)... Hash of data verified. Compressed 3072 bytes to 117... Writing at 0x00008000... (100 %) Wrote 3072 bytes (117 compressed) at 0x00008000 in 0.0 seconds (effective 532.7 kbit/s)... Hash of data verified. Compressed 8192 bytes to 31... Writing at 0x0000e000... (100 %) Wrote 8192 bytes (31 compressed) at 0x0000e000 in 0.1 seconds (effective 717.2 kbit/s)... Hash of data verified. Compressed 1911344 bytes to 1100164... Writing at 0x00010000... (1 %) Writing at 0x00019da2... (2 %) Writing at 0x000294db... (4 %) Writing at 0x00032cf1... (5 %) Writing at 0x0003cff3... (7 %) Writing at 0x000463f0... (8 %) Writing at 0x000539ae... (10 %) Writing at 0x00064890... (11 %) Writing at 0x00070023... (13 %) Writing at 0x00075f05... (14 %) Writing at 0x0007bf1a... (16 %) Writing at 0x00082752... (17 %) Writing at 0x00089d19... (19 %) Writing at 0x0008fe6a... (20 %) Writing at 0x00095e26... (22 %) Writing at 0x0009b70c... (23 %) Writing at 0x000a1679... (25 %) Writing at 0x000a79c1... (26 %) Writing at 0x000ae887... (27 %) Writing at 0x000b4a03... (29 %) Writing at 0x000ba744... (30 %) Writing at 0x000c015b... (32 %) Writing at 0x000c6073... (33 %) Writing at 0x000cbc64... (35 %) Writing at 0x000d19ce... (36 %) Writing at 0x000d7b45... (38 %) Writing at 0x000dd9e8... (39 %) Writing at 0x000e3bf4... (41 %) Writing at 0x000ea691... (42 %) Writing at 0x000f05e8... (44 %) Writing at 0x000f61b3... (45 %) Writing at 0x000fbb67... (47 %) Writing at 0x001018ab... (48 %) Writing at 0x00106a46... (50 %) Writing at 0x0010be60... (51 %) Writing at 0x001112b6... (52 %) Writing at 0x0011697e... (54 %) Writing at 0x0011be14... (55 %) Writing at 0x001216b4... (57 %) Writing at 0x0012724e... (58 %) Writing at 0x0012d14a... (60 %) Writing at 0x00134b36... (61 %) Writing at 0x0013d4ae... (63 %) Writing at 0x00144e03... (64 %) Writing at 0x0014bd5d... (66 %) Writing at 0x00151d49... (67 %) Writing at 0x00158757... (69 %) Writing at 0x0015ed77... (70 %) Writing at 0x00165d9d... (72 %) Writing at 0x0016c9b9... (73 %) Writing at 0x00173147... (75 %) Writing at 0x0017907c... (76 %) Writing at 0x00181ce9... (77 %) Writing at 0x00187ecd... (79 %) Writing at 0x0018dfe7... (80 %) Writing at 0x0019477a... (82 %) Writing at 0x0019a408... (83 %) Writing at 0x001a07fa... (85 %) Writing at 0x001a770d... (86 %) Writing at 0x001af5f2... (88 %) Writing at 0x001b6306... (89 %) Writing at 0x001bde77... (91 %) Writing at 0x001c549a... (92 %) Writing at 0x001caab7... (94 %) Writing at 0x001d08d7... (95 %) Writing at 0x001d5fd1... (97 %) Writing at 0x001db74b... (98 %) Writing at 0x001e1997... (100 %) Wrote 1911344 bytes (1100164 compressed) at 0x00010000 in 17.1 seconds (effective 893.3 kbit/s)... Hash of data verified. Leaving... Hard resetting via RTS pin... ============================================================================ [SUCCESS] Took 42.21 seconds ============================================================================ Environment Status Duration -------------- -------- ------------ fujinet-v1-8mb SUCCESS 00:00:42.212 ============================================================================ 1 succeeded in 00:00:42.212 ============================================================================ I guess soldering in JTAG connector and flashing via that is only option now?
  11. Thanks for that! I just did fresh install, followed wiki but was getting following error: Archiving .pio/build/fujinet-v1/lib209/libhardware.a Indexing .pio/build/fujinet-v1/lib209/libhardware.a Archiving .pio/build/fujinet-v1/lib45e/libsio.a Indexing .pio/build/fujinet-v1/lib45e/libsio.a Archiving .pio/build/fujinet-v1/libaca/libhttp.a Indexing .pio/build/fujinet-v1/libaca/libhttp.a Linking .pio/build/fujinet-v1/firmware.elf /home/user/.platformio/packages/toolchain-xtensa32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: .pio/build/fujinet-v1/lib916/libFileSystem.a(fnFsSPIF.o):(.literal._ZN16FileSystemSPIFFS8dir_openEPKcS1_t+0x0): undefined reference to `opendir(char const*)' /home/user/.platformio/packages/toolchain-xtensa32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: .pio/build/fujinet-v1/lib916/libFileSystem.a(fnFsSPIF.o):(.literal._ZN16FileSystemSPIFFS8dir_readEv+0x0): undefined reference to `readdir(DIR*)' /home/user/.platformio/packages/toolchain-xtensa32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: .pio/build/fujinet-v1/lib916/libFileSystem.a(fnFsSPIF.o):(.literal._ZN16FileSystemSPIFFS9dir_closeEv+0x0): undefined reference to `closedir(DIR*)' /home/user/.platformio/packages/toolchain-xtensa32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: .pio/build/fujinet-v1/lib916/libFileSystem.a(fnFsSPIF.o): in function `FileSystemSPIFFS::dir_open(char const*, char const*, unsigned short)': /home/user/Projects/fujinet-platformio/lib/FileSystem/fnFsSPIF.cpp:16: undefined reference to `opendir(char const*)' /home/user/.platformio/packages/toolchain-xtensa32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: .pio/build/fujinet-v1/lib916/libFileSystem.a(fnFsSPIF.o): in function `FileSystemSPIFFS::dir_read()': /home/user/Projects/fujinet-platformio/lib/FileSystem/fnFsSPIF.cpp:28: undefined reference to `readdir(DIR*)' /home/user/.platformio/packages/toolchain-xtensa32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: .pio/build/fujinet-v1/lib916/libFileSystem.a(fnFsSPIF.o): in function `FileSystemSPIFFS::dir_close()': /home/user/Projects/fujinet-platformio/lib/FileSystem/fnFsSPIF.cpp:57: undefined reference to `closedir(DIR*)' collect2: error: ld returned 1 exit status *** [.pio/build/fujinet-v1/firmware.elf] Error 1 ============================================================================ [FAILED] Took 88.48 seconds ============================================================================ Environment Status Duration ------------- -------- ------------ fujinet-v1 FAILED 00:01:28.477 ======================================================================= 1 failed, 0 succeeded in 00:01:28.477 ======================================================================= The terminal process "platformio 'run', '--environment', 'fujinet-v1'" terminated with exit code: 1. (pasting here so it will be easier for others to find if looking for same error) after modifying dirent.h all is working as expected. Thanks!
  12. I think he did not mention new server as it is auto ban. LiberaChat? https://www.theregister.com/2021/05/19/freenode_staff_resigns/
  13. this is nice, will be good to have such library on the side note, how do you generate all these sound data for engine? what is Your process for that?
  14. I had similar when my PSU died and fried one of RAM chips
  15. great news! networking games for a8 are flourishing :)
  16. I was pleasantly surprised with https://cdn.myshoptet.com/usr/www.sintech-shop.cz/user/shop/big/6256-1_8144-scart-hdmi-2.jpg as as it worked well. Like @bfollowell mentioned, OSSC is great. Currently connected directly to NEC 1970VX and it's good as well.
  17. Is that one https://hama.hu/termekek/70-tv-hifi-hazimozi/82-egyeb/a3182-scart-hdmi-konverter ? I had something that looked exactly same and wasn't good enough to pick up 15khz if that's what You are looking for. Maybe that one is different, but I've tried 4 different Scart2HDMI and only one was good and reliable
  18. these chips are 256k each, so if you don't have anything on other side, 4 of them makes 1mb per simm
  19. I have removed directory completely, downloaded zip https://github.com/FujiNetWIFI/fujinet-platformio/archive/v0.1.ccbb292f.zip unpacked, added platformio.ini as in earlier post and run build. No errors =========================================================================== [SUCCESS] Took 273.02 seconds =========================================================================== Environment Status Duration ------------- -------- ------------ fujinet-wroom SUCCESS 00:04:33.019 but boot_app0.bin is not there $ find . -name "*.bin" ./.pio/build/fujinet-wroom/partitions.bin ./.pio/build/fujinet-wroom/CMakeFiles/3.16.4/CMakeDetermineCompilerABI_CXX.bin ./.pio/build/fujinet-wroom/CMakeFiles/3.16.4/CMakeDetermineCompilerABI_C.bin ./.pio/build/fujinet-wroom/bootloader.bin ./.pio/build/fujinet-wroom/firmware.bin ./.pio/build/fujinet-wroom/bootloader/CMakeFiles/3.16.4/CMakeDetermineCompilerABI_CXX.bin ./.pio/build/fujinet-wroom/bootloader/CMakeFiles/3.16.4/CMakeDetermineCompilerABI_C.bin ./data/850handler.bin ./data/picoboot.bin ./data/850relocator.bin but also no spiffs.bin this time so I guess something must be missing in my setup.
  20. my platformio.ini looks ok I think $ cat platformio.ini ;FujiNet PlatformIO Project Configuration File ; ; Build options: build flags, source filter ; Upload options: custom upload port, speed and extra flags ; Library options: dependencies, extra library storages ; Advanced options: extra scripting ; ; Please visit documentation for the other options and examples ; https://docs.platformio.org/page/projectconf.html [platformio] description = FujiNet Atari to ESP32 WiFi Multifunction Firmware ; Change this to target the device you use from the list of [env:xxx] sections below default_envs = fujinet-wroom [env] ; Common settings for all enivornments platform = espressif32 framework = espidf extra_scripts = pre:build_version.py lib_ldf_mode = deep+ ;upload_port = COM1 ; Windows upload_port = /dev/ttyUSB0 ; Linux upload_speed = 921600 ;monitor_port = COM1 ; Windows monitor_port = /dev/ttyUSB0 ; Linux monitor_speed = 921600 monitor_filters = time ; ESP32 WROOM [env:fujinet-wroom] board = fujinet-wroom build_type = debug build_flags = ;-D JTAG -D DEBUG_SPEED=921600 -D BLUETOOTH_SUPPORT ;-D FN_HISPEED_INDEX=0 ;-D VERBOSE_SIO ;-D VERBOSE_TNFS ;-D VERBOSE_DISK ;-D VERBOSE_ATX Only thing I can think of is boot_app0.bin which was not produced in build and I had to take it from current one. Maybe it has references to PSRAM? what that binary is responsible for?
  21. My board definition looks like: $ cat boards/fujinet-wroom.json { "build": { "arduino":{ "ldscript": "esp32_out.ld" }, "core": "esp32", "extra_flags": "-DARDUINO_ESP32_DEV", "f_cpu": "240000000L", "f_flash": "40000000L", "flash_mode": "dio", "mcu": "esp32", "variant": "esp32", "partitions": "fujinet_partitions_4MB.csv" }, "connectivity": [ "wifi", "bluetooth", "ethernet", "can" ], "debug": { "openocd_board": "esp-wroom-32.cfg" }, "frameworks": [ "arduino", "espidf" ], "name": "#FujiNet WROOM", "upload": { "flash_size": "4MB", "maximum_ram_size": 327680, "maximum_size": 4194304, "protocols": [ "esptool", "espota", "ftdi" ], "require_upload_port": true, "speed": 460800 }, "url": "https://github.com/FujiNetWIFI/atariwifi", "vendor": "FujiNet Project" } I can see that defined for other boards: $ grep BOARD_HAS_PSRAM * -R boards/fujinet-v1.json: "extra_flags": "-DARDUINO_ESP32_DEV -DBOARD_HAS_PSRAM", boards/fujinet-v1-4mb.json: "extra_flags": "-DARDUINO_ESP32_DEV -DBOARD_HAS_PSRAM", Is my board definition ok? I do not mention BOARD_HAS_PSRAM in flags, or it's defined somewhere else?
  22. I have used that code https://github.com/FujiNetWIFI/fujinet-platformio/releases/tag/v0.1.ccbb292f I can switch to commit you mentioned and test it.
  23. I managed to compile that firmware. I could not use GUI flasher as it's configured for bigger boards. After compilation, in .pio/build/fujinet-wroom/ I had 4 files: bootloader.bin partitions.bin spiffs.bin firmware.bin boot_app0.bin was taken from https://fujinet.online/firmware-dl/ Is that version ok for WROOM? I've used esptool with following offsets: esptool.py write_flash 0x1000 ./bootloader.bin 0x8000 ./partitions.bin 0xE000 ./boot_app0.bin 0x10000 ./firmware.bin 0x200000 ./spiffs.bin I had to play w bit with these offsets to fit. Command output look ok: esptool.py v2.6 Found 1 serial ports Serial port /dev/ttyUSB0 Connecting........_____....._____.. Detecting chip type... ESP32 Chip is ESP32D0WDQ5 (revision 1) Features: WiFi, BT, Dual Core, Coding Scheme None MAC: 30:30:30:30:30:30 Uploading stub... Running stub... Stub running... Configuring flash size... Auto-detected Flash size: 4MB Compressed 26960 bytes to 16219... Wrote 26960 bytes (16219 compressed) at 0x00001000 in 1.4 seconds (effective 150.4 kbit/s)... Hash of data verified. Compressed 3072 bytes to 119... Wrote 3072 bytes (119 compressed) at 0x00008000 in 0.0 seconds (effective 1544.3 kbit/s)... Hash of data verified. Compressed 8192 bytes to 47... Wrote 8192 bytes (47 compressed) at 0x0000e000 in 0.0 seconds (effective 7258.3 kbit/s)... Hash of data verified. Compressed 1960832 bytes to 1137946... Wrote 1960832 bytes (1137946 compressed) at 0x00010000 in 101.3 seconds (effective 154.9 kbit/s)... Hash of data verified. Compressed 1769472 bytes to 339295... Wrote 1769472 bytes (339295 compressed) at 0x00200000 in 30.2 seconds (effective 469.1 kbit/s)... Hash of data verified. Leaving... Hard resetting via RTS pin... It flashed but something is not ok, here is debug output: rst:0xc (SW_CPU_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:0x3fff0030,len:4 load:0x3fff0034,len:5532 load:0x40078000,len:16488 load:0x40080400,len:4840 entry 0x400806a4 E (657) spiram: SPI RAM enabled but initialization failed. Bailing out. E (666) uart: uart_write_bytes(1111): uart driver error E (666) uart: uart_write_bytes(1111): uart driver error E (666) uart: uart_write_bytes(1111): uart driver error E (670) uart: uart_write_bytes(1111): uart driver error E (675) uart: uart_write_bytes(1111): uart driver error E (680) uart: uart_write_bytes(1111): uart driver error E (685) uart: _����垠8�(����R��`D0` @`��̀��<@$��$$"�Dz�ets Jun 8 2016 00:22:57 rst:0xc (SW_CPU_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:0x3fff0030,len:4 load:0x3fff0034,len:5532 load:0x40078000,len:16488 load:0x40080400,len:4840 entry 0x400806a4 I have tried with different offsets as well esptool.py write_flash 0x0000 ./bootloader.bin 0x8000 ./partitions.bin 0xE000 ./boot_app0.bin 0x10000 ./firmware.bin 0x250000 ./spiffs.bin But it also failed, different error this time. rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) flash read err, 1000 ets_main.c 371 ets Jun 8 2016 00:22:57 I guess some of the offsets are not ok. Any idea which one?
×
×
  • Create New...