V6.0 FIRMWARE RELEASED!
#11
Hey Jim, I know it's too late for this release but in the next release can you
increase the banned IP list to 20? I've filled mine up and need more entries.

I think we had talked about this one time before. No rush, BTW. Thanks.
Reply
#12
Will do! Do you need more than 20? I have space set aside for up to 50 entries. The issue of course is looking at them because 50 entries would scroll them off the screen.
Reply
#13
Thanks, I guess 20 will do. Unless...you can add a keypress or page break
to stop the scrolling? I really don't know what you can and can't do with
the WiModem232 (although it always seems to border on the miraculous
to me!). Smile
Reply
#14
Well, I could make it so that after so many entries that are used it pauses and wait for any key to be pressed. I will look at that.
Reply
#15
Awesome, thanks much! Smile
Reply
#16
I noticed an issue with a crash that seems to be specific to the latest firmware, so noting it here, tried several machines. I rolled back from 6.10 to 6.01 and it worked. Upgraded back to 6.10 and crashed again on this specific BBS: bbs.fozztexx.com

ati
WiModem232 - ©2015-2023 By Jim Drew

Firmware:v6.10-05/21/23
Baud:600,8N1
Outgoing Port:23
Incoming Port:6400
..

CONNECT


Welcome to the *NEW* Level 29 BBS!
916 965 1701 - bbs.fozztexx.com

              __
  ___________/__\___________
/
  --------------- CUT HERE FOR EXCEPTION DECODER ---------------

Exception (29):
epc1=0x4000df64 epc2=0x00000000 epc3=0x00000000 excvaddr=0x00000000 depc=0x00000000

>>>stack>>>

ctx: sys
sp: 3ffffcb0 end: 3fffffb0 offset: 0150
3ffffe00:  40246507 3ffeebb0 00000002 4024649c
3ffffe10:  00000002 40246443 00000002 402451cc
3ffffe20:  402451f5 3ffffed0 3ffeebb0 00000016
3ffffe30:  40242c54 3ffffed0 3ffeea58 3ffee42c
3ff▒
Looking for router...

Connected to DeathStar


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


Connected to DeathStar


ati
WiModem232 - ©2015-2023 By Jim Drew

*** NEW FIRMWARE AVAILABLE ***

Firmware:v6.01-03/22/23
Baud:600,8N1
Outgoing Port:23
Incoming Port:6400
...

CONNECT


Welcome to the *NEW* Level 29 BBS!
916 965 1701 - bbs.fozztexx.com

              __
  ___________/__\___________
/  _  _  -__ -  ___  -  \
\__________________________/
            |  |
            |  |
        _____|  |______
    ___|    |  |      |___
  |  |    |  |      |  |
___|___|____/____\_____|___|___
                        __  __
|    __        __  |  /  \ /  \
|    /__\ |  | /__\ |  __/ \__/
|___ \__  \/  \__  |  /___  /

The official BBS of
RetroBattlestations.com


Enter your username or NEW or VISITOR
User:
Reply
#17
I went back to the v6.01 and found just like you that it worked fine. However, after a bunch of experimenting suddenly v6.01 (or any other previous version) no longer worked! I am trying to determine WHY this happens, and only with 600 baud!
Reply
#18
So, it seems to randomly work at 600 baud. I went back to v5.00 firmware and the same problem exists. I then tried a simple example serial bridge and the same thing happens, but only at 600 baud. I think that this is some type of bug in the ESP8266 OS. The bad thing is that I can't debug it or even look at the complete stack trace to know where the problem is because at 600 baud the crash report is too slow to complete before the CPU reboots itself! The report should contain 28 more lines, which are needed in order to determine the problem. Sad

I ran into the same issue at 300 baud, but less frequent, and 110 baud or higher than 600 never had a problem. I am not sure what can be done to debug this issue because this error (29) is due to something in the OS storing data where it does not belong.
Reply
#19
Thanks for the update, in the past I've mainly used this on a pentium era DOS PC at 57.6K, but I'd recently picked up a trs80 model 100 which I've read can't handle drawing text faster than 600 baud. With v6.10 I was able to connect at 110 baud, but it's pretty slow. I'm not too concerned with it myself, is the OS something that's still getting updates and might get a fix in the future?
Reply
#20
The problem has to be reported with something where it can be reliably duplicated. I think that is the case here. What is interesting is that whatever the issue might be it only happens with this BBS and only at 600 baud. So, I will report it and see if the company that makes the OS can track down the issue. The OS is being actively updated. This product uses a ESP8266. I have prototypes of the WiModem232 using ESP32 standard and RISC-V CPUs and neither of them have this issue.
Reply




Users browsing this thread: 1 Guest(s)