IMSAI 8080 rebooting after firmware update

[John Doudar]

I have just updated the firmware on my IMSAI 8080 to the  Oct 22 release. All seemed to go well as I got the usual update messages after I dragged the “imsaisim_esp32.bin” file onto the sys desktop icon. However after the reboot, I can not get any lights on the front panel to light up, the led on the ESP32 is lit. I fired up PuTTy it looks like it is in a never-ending reboot cycle. Any ideas on how I can get this working again?

===========================================================

#######  #####    ###            #####    ###   #     #
     #  #     #  #   #          #     #    #    ##   ##
    #   #     # #     #         #          #    # # # #
   #     #####  #     #  #####   #####     #    #  #  #
  #     #     # #     #               #    #    #     #
 #      #     #  #   #          #     #    #    #     #
#######  #####    ###            #####    ###   #     #

Release 1.38-dev, Copyright (C) 1987-2022 by Udo Munk
ESP32 IMSAI 8080 Simulation Release 1.19 (ESP32)
Copyright (C) 2008-2022 by Udo Munk & David McNaughton

CPU speed is 4 MHz, CPU executes undocumented instructions
Guru Meditation Error: Core  0 panic'ed (LoadProhibited). Exception was unhandled.
Core 0 register dump:
PC      : 0x40056722  PS      : 0x00060230  A0      : 0x8005682e  A1      : 0x3ffc6040
A2      : 0x3ffc647c  A3      : 0x00000000  A4      : 0x00000000  A5      : 0x00000000
A6      : 0x00000000  A7      : 0x00000008  A8      : 0x8000be99  A9      : 0x3ffc6030
A10     : 0x3ffc647c  A11     : 0x00000000  A12     : 0x3ffc60a9  A13     : 0x0ccccccc
A14     : 0x00000000  A15     : 0x00000004  SAR     : 0x00000008  EXCCAUSE: 0x0000001c
EXCVADDR: 0x00000000  LBEG    : 0x400012c5  LEND    : 0x400012d5  LCOUNT  : 0xfffffffb

ELF file SHA256: 78f2e7a34a9eb3c6

Backtrace: 0x4005671f:0x3ffc6040 0x4005682b:0x3ffc6070 0x4012fdae:0x3ffc6090 0x400f5dae:0x3ffc62e0 0x400d4663:0x3ffc6360 0x400d2524:0x3ffc6380

Rebooting...
ets Jun  8 2016 00:22:57

rst:0xc (SW_CPU_RESET),boot:0x3f (SPI_FAST_FLASH_BOOT)
configsip: 188777542, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0018,len:4
load:0x3fff001c,len:4524
load:0x40078000,len:13468
ho 0 tail 12 room 4
load:0x40080400,len:3784
entry 0x40080620
I (352) psram: This chip is ESP32-PICO
I (352) spiram: Found 64MBit SPI RAM device
I (352) spiram: SPI RAM mode: flash 80m sram 80m
I (355) spiram: PSRAM initialized, cache is in low/high (2-core) mode.
I (362) cpu_start: Pro cpu up.
I (366) cpu_start: Application information:
I (371) cpu_start: Project name:     imsaisim_esp32
I (376) cpu_start: App version:      v1.10.0
I (381) cpu_start: Compile time:     Sep 18 2022 13:48:00
I (387) cpu_start: ELF file SHA256:  78f2e7a34a9eb3c6...
I (393) cpu_start: ESP-IDF:          v4.0.2-4-g877a28e05
I (399) cpu_start: Starting app cpu, entry point is 0x40081bac
I (390) cpu_start: App cpu up.
I (896) spiram: SPI SRAM memory test OK
I (931) heap_init: Initializing. RAM available for dynamic allocation:
I (931) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
I (933) heap_init: At 3FFC4878 len 0001B788 (109 KiB): DRAM
I (939) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (945) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (952) heap_init: At 4009DD54 len 000022AC (8 KiB): IRAM
I (958) cpu_start: Pro cpu start user code
I (963) spiram: Adding pool of 3625K of external SPI memory to heap allocator
I (983) spi_flash: detected chip: gd
I (984) spi_flash: flash io: qio
I (984) cpu_start: Starting scheduler on PRO CPU.
I (0) cpu_start: Starting scheduler on APP CPU.
I (1053) nvs: Reading settings from NVS
I (1053) nvs: settings = 00000958
I (1053) esp32_boot: Log Level set to NONE
I (1678) phy: phy_version: 4390, 6b3c1f2, Sep 10 2020, 15:09:07, 0, 0

[TheHighNibble]

Did you make the required changes to the directories and config files on the uSD card as per the release notes?

If all you did is upgrade the firmware binary, then this failure mode is to be expected.

[John Doudar]

Opps, RTFM.

[John Doudar]

Have made the changes as per the instructions and can connect ok using PuTTY. I cannot, however, connect to the desktop UI. The IMSAI8080 seems to be stuck in AP mode, I always use STA mode. I have even run the startup configuration again but it always boots up in AP mode. Has anything changed that could affect this as I notice a new line in the boot.config file "WIFI.sta.scan=1"?

--
You received this message because you are subscribed to the Google Groups "IMSAI 8080esp" group.
To unsubscribe from this group and stop receiving emails from it, send an email to imsai8080esp...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/imsai8080esp/5b85ea24-817a-4620-a4e9-46cfd614d430n%40googlegroups.com.

--

Strangely strange yet oddly normal.
There are 10 types of people, those that understand binary and those that don't.

---

My YouTube Channel

[TheHighNibble]

As per the configuration guide Wi-Fi section https://thehighnibble.com/imsai8080/configure/#wi-fi-communications

You'll see in the yellow, warning box: even with the IMSAI8080 set to STA mode, it will fall back to AP mode if it can't connect to your router.

There are many reasons why it maybe can't connect to your router:

• The most obvious would be if you haven't edited the SSID and PASSWORD values in the boot.conf file correctly
• The WIFI.sta.scan=1 parameter has been around for a while (just not as the default)
  • It is only useful if you have multiple APs on your network with the same SSID
  • It just tells the ESP32 to connect to the strongest signal it can find, not just the first one it finds
  • You can remove it from your boot.conf file and see if that does make a difference
• If its not one of the two above, nothing around WiFi was changed in this firmware, so you'd have to start looking at your router config as to why it is rejecting the ESP32.