S-132 displays endless stream of dots since upgrade from v1.7.0 to v1.8.0 (+IMSAI from v1.13.0 to v1.14.0) #271
Closed
ElectricDream
started this conversation in
S-132 add-on for IMSAI & Cromemco replicas
Replies: 1 comment 4 replies
|
I'm assuming you mean you updated from version 1.13.0 to 1.14.0 on the imsai esp firmware. I'm having the same problem: https://github.com/orgs/thehighnibble/discussions/270#discussioncomment-17182524 I just downgraded back to v1.13.0 for now and will wait to hear from @dmcnaugh about a fix. |
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hello,
I have just updated a couple hours ago my IMSAI8080esp from v1.3.0 to v1.4.0 and the S-132 add-on from v1.7.0 to v1.8.0 using the latest releases.
I started by updating the S-132, which completed successfully ("Firmware update complete" message displayed). I then updated the IMSAI8080esp. Everything went smoothly, and I verified that the version numbers reported by SYS are correct. After the update, the IMSAI was fully functional both through the web interface and from the S-132 terminal.
A few hours later, I restarted the IMSAI and ran into a problem. The IMSAI still works perfectly through the web interface, but the S-132 continuously displays dots, as if it cannot find or connect to the IMSAI.
I confirmed that the "S132.init=1" line is present in the configuration file. To rule out a configuration issue, I changed it to "S132.init=0", restarted the IMSAI, and then changed it back to "S132.init=1". Unfortunately, that did not help. The S-132 still displays an endless stream of dots.
I also tried pressing the RESET button on both the IMSAI and the S-132, but that made no difference. The dots continue to appear.
One small detail that may or may not be relevant: just before this problem occurred, I had started the IMSAI8080esp without its microSD card installed. I always make backups before and after firmware updates, so I had temporarily removed the card. Could booting once without the SD card have caused this issue?
At this point, I'm not sure what else to try. When i power on the IMSAI, and check SYS via the web interface, all the settings in boot.conf and system.conf appear correct, and I have compared them against my backups without finding any differences.
Does anyone have an idea what might be causing this problem?
Thanks in advance for any help.
All reactions