Latest firmware update has created random exception errors

[mnewkirk]

That's odd.  You should not be able to send any type of data that causes an exception.  Are you using Telnet or a RAW connection?

RAW

[bbsing]

I'm getting an exception as well.

This happens when I'm connected to a mgetty via a call atd,

I use minicom to call my mgetty server. It doesn't take long for the modem to throw exceptions. It seems if I do something simple like list the files via "ls" then try to "ls" again the exception will occur. Other behavior is the connection is just dropped.

Now if I don't use minicom and using the same system to telnet to my mgetty server, I the connection is more stable, but other anomalies appear with the conection with my other modem. The connection directly not using the wimodem with v6.x was to figure out which modem was having the probolem.

I'm using two wimodems: 

The exception also occurs with v6.41 ... Is there anyway to go back to firmware v4.20?

Here are the detals.

WiModem232 - ©2015-2025 By Jim Drew

Firmware:v6.50-01/20/25
Baud:9600,8N1
Outgoing Port:1541
Incoming Port:6400
SSID:wan
MAC8:F1:5B:F:BE:96
IP:192.168.2.151
WiFi Channel:1
FCC ID:2ADUIESP-12


--------------- 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:  40247bab 3ffee898 00000002 40247b40
3ffffe10:  00000002 40247ae7 00000002 40246870
3ffffe20:  40246899 3ffffed0 3ffee898 00000016
3ffffe30:  402442f8 3ffffed0 3ffee628 3ffedfb4
3ffffe40:  3ffeabb0 3ffffed0 3ffffed0 00001900
3ffffe50:  006e6177 00000030 00000010 00000000
3ffffe60:  00000000 00000000 3fff823c 40233c45
3ffffe70:  40240655 0000150c 59a06f4d 00000003
3ffffe80:  ffffffd6 3ffee13c 3ffeabc0 3ffee898
3ffffe90:  3ffed720 00000036 00000000 40244ff3
3ffffea0:  00000000 3fff5b3c ffffffd6 00000000
3ffffeb0:  00000000 3ffee898 0000000d 0000000f
3ffffec0:  3fff57a4 3fff5530 bf0658d0 3fff57ec
3ffffed0:  00000000 10110101 00640104 00000042
3ffffee0:  3ffeabd4 0000018b 3ffeabe6 3ffeabc8
3ffffef0:  3ffeabec 3ffeabd4 3ffeabd9 3ffeabfb
3fffff00:  00000000 00000000 3ffeac01 3ffead38
3fffff10:  3ffeac25 3ffeac41 00000000 3ffeacbf
3fffff20:  00000000 00000000 00000036 00000000
3fffff30:  3fff5f04 40244a62 3ffed720 3fff5b3c
3fffff40:  00000000 3ffee898 3ffed720 3ffeabb0
3fffff50:  3ffeabb0 000001b3 00000000 00000036
3fffff60:  00000000 3ffeabba 4025d7ff 3ffed720
3fffff70:  3ffeaba4 3fffdcc0 3ffe9d38 3ffe9d38
3fffff80:  00000080 3ffed720 00000000 3fffdab0
3fffff90:  4025d0c7 3fffdab0 00000000 40220a0e
3fffffa0:  3ffe9d38 40000f49 ffffff00 40000f49
<<<stack<<<


--------------- CUT HERE FOR EXCEPTION DECODER ---------------

[admin]

Do you guys have AT&K1 enabled? Can you provide your settings by using AT&V?

[bbsing]

Here is my setting:

at&v
at&v
B0 C0 E1 L0 M0 N0 Q0 V1 W0 X0 S0:0 S1:0 S2:43 S3:13 S4:10 S5:8 S6:2 S7:60 S8:2 S9:6 S10:15 S11:90 S12:50 S25:0
S30:0 S37:6 S73:0 *B300 *BL1024 *BT5 *C0 *CT1 *D1 *HO25 *L6400 *LED5 *P1541 *R0 *T0 &C1 &D0 &G0 &K0 &Q0 &S0

[bbsing]

certainly something odd is happening.
My terminal port settings are at 9600 baud, but my wimodem thinks its at 300 baud.

The winmodem is actually behaving at 9600 baud.

+---------[Comm Parameters]----------+
| |
| Current: 9600 8N1 |
| Speed Parity Data |
| A: <next> L: None S: 5 |
| B: <prev> M: Even T: 6 |
| C: 9600 N: Odd U: 7 |
| D: 38400 O: Mark V: 8 |
| E: 115200 P: Space |
| |
| Stopbits |
| W: 1 Q: 8-N-1 |
| X: 2 R: 7-E-1 |

WiModem232 - ©2015-2| |
| |
*** NEW FIRMWARE AVAIL| Choice, or <Enter> to exit? |
+------------------------------------+
Firmware:v6.41-01/10/25
Baud:300,8N1
Outgoing Port:1541
Incoming Port:6400
SSID:wan
MAC8:F1:5B:F:BE:96
IP:192.168.2.151
WiFi Channel:1
FCC ID:2ADUIESP-12


CTRL-A Z for help | 9600 8N1 | NOR | Minicom 2.7.1 | VT102 | Offline | ttyUSB0

[mnewkirk]

K1 is not set on my system.

[admin]

You need to send AT&F after a firmware update. That will reset the baud rate. Also, if you are using 9600 baud or higher you should probably have AT&K1 enabled.

Also, trying setting AT*BL512 (instead of 1024).

[bbsing]

AT&F has no effect on the baud rate. I did at&f after the upgrade and downgrade.

it seemed like at&f didn't do anything until another setting was changed first; i changed k0 to k1. Then at&f took.

after doing at&f, at&k1, at*bl512.

same results still throwing exception. But this time much faster. First ls produced an exception.

[admin]

OK, try using AT*B64 and see if that also is quick. Then try AT*BL8192. It seems that whatever you are using for a BBS or terminal is not paying attention to the AT&K1 handshaking and it is over-running the buffer. That really should not be possible, especially on a standard WiModem for the C64 since serial is so slow. Also, anything that is using Telnet likely needs to have translation enabled.

[bbsing]

at*bl64 worked for about 8 ls -lhtrc (listings). The list has about 25 files.
AT*BL8192 only errors time after time. Like that buffer limit is out of bounds.

when AT*T1 is set there is an immediate exception (29) after connecting to the system.

I'm connecting via client (wimodem with exceptions v6.41) via atd 192.168.x.x:6400 to an ---> mgetty using (wimodem v4.x) on device /dev/ttyS0

This is not really telnet directly. This would be more like an old school dialup server, but similar to a bbs dialin.