TIPI Usage and Support

[+jedimatt42]

Ok, that is super confusing... 

 

So, then, I'd recommend going through:

 

sudo raspi-config, from a connected keyboard/monitor and try and re-specify your network settings. 

 

Looks like Raspberry PI OS now has 'predictable network interface names' off by default...  this is something that can be turned on in raspi-config... I never heard of this before... 

 

my ethernet works, it is just named some crazy: 

enxb827ebf07f81: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.114  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 ----------------------- prefixlen 64  scopeid 0x20<link>
        ether ----------------  txqueuelen 1000  (Ethernet)
        RX packets 379  bytes 75125 (73.3 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 88  bytes 15494 (15.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
 

I had never even looked at it... just plugged a cable in, and it worked. 

 

 

[+jedimatt42]

I don't think we get 'eth0' back, but ethernet seems to work for me fine... however, the problem that you can't find your IP address?  Probably the TIPI PI.STATUS code that looks for it, doesn't understand the new ethernet names.  And while, I am using ethernet, I do have wifi enabled and configured, so I'm getting _an_ ip address. 

 

If that is the issue, it is something I can fix within the TIPI software. 

 

 

[Omega-TI]

It looks like I'm going to have to start over with a new SD card, reformat, reflash and re-install 2.3 'buster' then expand the file system, then upgrade to 2.4 all over again.  For some strange reason sometimes when I turn on the TIPI it comes up showing a CRU base of 2000 instead of 1000 and it cannot find the network.  After a reboot it comes up on showing the correct CRU base of 1000 and it finds the network... BUT...  when I load TIPI.NET.TELNET I connect to Heatwave BBS, but nothing comes back.  I found an earlier SD card with version  1.41 of the Rpi software and everything works as expected.  I cannot even guess at what is going wrong.  

 

TIPI 2.4/TELNET failure

 

I'm also wondering if TELNET got corrupted on the new somehow... I think I'll copy over the programs from the other TIPI to this one first and see if that corrects the problem before I go through the time consuming process of a total reinstall.

--- EDIT --

 

NOPE that did NOT work.  It appears to be something wrong with my 'buster' version.  I'll re-download the file and start over this evening

 

 

 

Edited July 7, 2020 by Omega-TI

[+jedimatt42]

Nothing on the SD card should be capable of affecting the CRUBASE discovered by TIPICFG...

Nothing...

 

Something else is changing physically... Those that have received this error have not recovered by starting fresh with a new SD card... 

[J-Data]

Just to add another data point, I'm seeing some similar issues with 2.4 on my TIPI/32K with RPi Zero W. 

 

I burnt a fresh SD card with 2.3 form the new ISO, and then upgraded to 2.4. so its a fairly clean image.  (I haven't attempted upgrading from 1.6x to 2.x, since I've had issue with upgrades, so I avoid them unless there's something I really need, and I do keep back up copies of all the old images as ISO files.)

 

So my issues are somewhat different.   Sometimes I get an IP address, sometimes I don't.  When I get an IP address, the CRU address is >1000, when I don't its >2000, which should literally be impossible with the new rev 3 of the CPLD (Ignores CRU MSB).  The answer changes from one "CALL TIPI" to the next, and the first boot on power up seems to be the most unreliable.  

 

Also, the myti99.com apps (Chatti, Chess, SNEK) are all slightly broken with 2.4, either forgetting my logins, not launching reliably, or having new odd bugs that make them unusable.  I've tried going back to my old V1.61 image and these issues seem to go away.    I think you've already explained what might be causing the app issues a few posts ago. 

 

Anyway, I'll going back to my 1.61 image for now.

[Omega-TI]

Yeah, I just got done reinstalling TIPI 2.3 (I didn't even update to 2.4).  The first thing I did was load the TELNET program and sonofa-B, same $hite.  ?

[Omega-TI]

Here is the log from my clean install...

2020-07-07 16:25:38,935 TipiService : INFO     physical mode enabled
2020-07-07 16:25:38,938 TipiService : INFO     TIPI Ready
2020-07-07 16:26:57,239 TipiDisk    : INFO     Opcode 5 LOAD - TIPI.NET.TELNET
2020-07-07 16:26:57,242 Pab         : INFO     opcode: Load, fileType: Sequential, mode: Update, dataType: Display, recordType: Fixed, recordLength: 0, recordNumber: 8198
2020-07-07 16:26:57,262 TipiDisk    : INFO     LOAD image size 8192
2020-07-07 16:26:58,351 TipiService : INFO     Request completed.
2020-07-07 16:26:58,570 TipiDisk    : INFO     Opcode 5 LOAD - TIPI.NET.TELNEU
2020-07-07 16:26:58,572 Pab         : INFO     opcode: Load, fileType: Sequential, mode: Update, dataType: Display, recordType: Fixed, recordLength: 0, recordNumber: 8198
2020-07-07 16:26:58,588 TipiDisk    : INFO     LOAD image size 5120
2020-07-07 16:26:59,268 TipiService : INFO     Request completed.
2020-07-07 16:27:26,344 TiSocket    : INFO     open socket(0) HEATWAVE.DDNS.NET:9640
2020-07-07 16:27:26,541 TiSocket    : INFO     connected
2020-07-07 16:27:26,873 TiSocket    : INFO     read 6 bytes from 0
2020-07-07 16:27:27,045 TiSocket    : INFO     read 0 bytes from 0
2020-07-07 16:27:50,280 TipiService : INFO     physical mode enabled
2020-07-07 16:27:50,282 TipiService : INFO     TIPI Ready
2020-07-07 16:28:08,331 TipiService : INFO     physical mode enabled
2020-07-07 16:28:08,333 TipiService : INFO     TIPI Ready
2020-07-07 16:28:08,339 TipiDisk    : INFO     Opcode 0 Open - TIPI.AUTOCMD
2020-07-07 16:28:08,341 Pab         : INFO     opcode: Open, fileType: Sequential, mode: Input, dataType: Display, recordType: Variable, recordLength: 0, recordNumber: 0
2020-07-07 16:28:08,347 TipiDisk    : INFO     Passing to other controllers
2020-07-07 16:28:08,349 TipiDisk    : ERROR    responding with error: 0
NoneType: None
2020-07-07 16:28:08,352 TipiService : INFO     Request completed.
2020-07-07 16:28:13,081 TipiDisk    : INFO     Opcode 0 Open - TIPI.
2020-07-07 16:28:13,084 Pab         : INFO     opcode: Open, fileType: Relative, mode: Input, dataType: Internal, recordType: Fixed, recordLength: 0, recordNumber: 0
2020-07-07 16:28:13,128 TipiService : INFO     Request completed.
2020-07-07 16:28:13,156 Pab         : INFO     opcode: Close, fileType: Relative, mode: Input, dataType: Internal, recordType: Fixed, recordLength: 38, recordNumber: 0
2020-07-07 16:28:13,158 TipiService : INFO     Request completed.
2020-07-07 16:28:13,183 TipiDisk    : INFO     Opcode 0 Open - TIPI.
2020-07-07 16:28:13,185 Pab         : INFO     opcode: Open, fileType: Relative, mode: Input, dataType: Internal, recordType: Fixed, recordLength: 0, recordNumber: 0
2020-07-07 16:28:13,220 TipiService : INFO     Request completed.
2020-07-07 16:28:13,237 Pab         : INFO     opcode: Read, fileType: Relative, mode: Input, dataType: Internal, recordType: Fixed, recordLength: 38, recordNumber: 0
2020-07-07 16:28:13,266 TipiService : INFO     Request completed.
2020-07-07 16:28:13,364 Pab         : INFO     opcode: Read, fileType: Relative, mode: Input, dataType: Internal, recordType: Fixed, recordLength: 38, recordNumber: 1
2020-07-07 16:28:13,371 TipiService : INFO     Request completed.
2020-07-07 16:28:13,403 Pab         : INFO     opcode: Read, fileType: Relative, mode: Input, dataType: Internal, recordType: Fixed, recordLength: 38, recordNumber: 2
2020-07-07 16:28:13,425 TipiService : INFO     Request completed.
2020-07-07 16:28:13,462 Pab         : INFO     opcode: Read, fileType: Relative, mode: Input, dataType: Internal, recordType: Fixed, recordLength: 38, recordNumber: 3
2020-07-07 16:28:13,480 TipiService : INFO     Request completed.
2020-07-07 16:28:13,539 Pab         : INFO     opcode: Read, fileType: Relative, mode: Input, dataType: Internal, recordType: Fixed, recordLength: 38, recordNumber: 4
2020-07-07 16:28:13,564 TipiService : INFO     Request completed.
2020-07-07 16:28:13,572 Pab         : INFO     opcode: Close, fileType: Relative, mode: Input, dataType: Internal, recordType: Fixed, recordLength: 38, recordNumber: 4
2020-07-07 16:28:13,601 TipiService : INFO     Request completed.

[+jedimatt42]

17 minutes ago, Omega-TI said:

Yeah, I just got done reinstalling TIPI 2.3 (I didn't even update to 2.4).  The first thing I did was load the TELNET program and sonofa-B, same $hite.  ?

Blanking out and mispelling a word doesn't change the fact that you said it... I do this for free. MIND YOURSELF!

[Omega-TI]

2 minutes ago, jedimatt42 said:

Blanking out and mispelling a word doesn't change the fact that you said it... I do this for free. MIND YOURSELF!

 

Sorry for the misinterpretation Matt, it's nothing against your software, it was just the frustration of all the time invested thinking I was stupid and couldn't follow basic directions.  Not being a programmer, I cannot say with certainty, but I'd be willing to guess it has more to do with the new Raspian Kernal than anything else.  If other people running RPI 3's are not having an issue, I would think it has more to do with the new OS not liking Pi Zeros.

[J-Data]

I repeated the same test with another console, a different TIPI/32K and a different RPi zero and got the same results.  (no IP at times, CRUBASE >2000, and generally flaky behavior) 

 

I repeated a third time with a TIPI/32K but with RPi 3b (connected to wifi) and DID NOT see the Ethernet or CRUBASE issues.  (I did still see the SNEK high score issue though).  I suspect this is a RPi Zero W specific problem, like @jedimatt42 suggested earlier. 

 

I could do a test with the original Sidecar TIPI and a RPi Zero If anyone thinks that datapoint would be useful. 

 

I should mention, the longer I test, the more stable 2.4 seems to get.  I seem to remember a similar behavior when upgrading to 1.59 or so, that it took some time for the upgrade to "settle in" on the RPi zero.  I know it doesn't make much sense, but It does feel similar. 

 

If anyone needs it, I posted a back-up ISO of 1.61 (and 1.43) if you want back out of 2.4, and don't have an image to go to:

 

http://www.lilyandgrace.com/ti/TIPI-32K/ISO/

 

Obviously the .zip file is much smaller and will be faster to download. 

[Omega-TI]

13 minutes ago, J-Data said:

If anyone needs it, I posted a back-up ISO of 1.61 (and 1.43) if you want back out of 2.4, and don't have an image to go to:

 

http://www.lilyandgrace.com/ti/TIPI-32K/ISO/

 

Obviously the .zip file is much smaller and will be faster to download. 

 

Thanks, I'm trying to download the 1.61 image now.  If I remember correctly it should top out at 1.65 in an update.  My pooter say's 27 minutes to go!

[+jedimatt42]

If someone with the problem can make an image of their failing SD card available to me, I might be able to see what's going on.

 

I reviewed the TIPICFG code, and crubase 2000 is a side effect of failing to read the PI.STATUS, and continuing to look for the file down the crubase line... 

 

I have tested PI Zero W, and had not had the problem... 

[+jedimatt42]

7 minutes ago, Omega-TI said:

 

Thanks, I'm trying to download the 1.61 image now.  If I remember correctly it should top out at 1.65 in an update.  My pooter say's 27 minutes to go!

 

If you update from 1.61 image, it will say the 1.65 update is available, but it will apply the 2.4 update.

[Omega-TI]

1 minute ago, jedimatt42 said:

 

If you update from 1.61 image, it will say the 1.65 update is available, but it will apply the 2.4 update.

 

Good to know.  I'll apply his update and keep that as my working copy for the TIPI/32K.

[+helocast]

2 minutes ago, jedimatt42 said:

If someone with the problem can make an image of their failing SD card available to me, I might be able to see what's going on.

I reviewed the TIPICFG code, and crubase 2000 is a side effect of failing to read the PI.STATUS, and continuing to look for the file down the crubase line... 

I have tested PI Zero W, and had not had the problem... 

I very much appreciate your support. I popped in to say that you can cross me off your list of having install problems for now and saw this post, so I'm replying here.

What fixed it? I don't know. I DID go back and reflow all the pins on the tall extension header between the PI Zero W and the TIPI speech board.

As was mentioned here in another reply, I don't do sloppy soldering despite old eyes ... so yes I also visually went back over the dual supplied headers I had soldered along the right side of the PI - no bridges there.

 

This is new and exciting tech and application in the TI world (even though I'm a late adopter), so even though this isn't your product you are to be commended it works in sidecar, PEB-, and speech-synth formats.

Doug

P.S. V2.4 is stable! ?

[+InsaneMultitasker]

3 hours ago, Omega-TI said:

n I load TIPI.NET.TELNET I connect to Heatwave BBS, but nothing comes back.  I found an earlier SD card with version  1.41 of the Rpi software and everything works as expected.  I cannot even guess at what is going wrong. 

I heard heatwave chattering more than usual (I can pick up on the EZ135 head seeks when the house is quiet, i..e, i'm not on a conference call)  so I went upstairs to check the system.  I might have been there during one or two of the connection tests.  The BBS responded just fine but no login activity. I was able to telnet in myself so I attributed it to a bot scan or some other internet tomfoolery. 

[J-Data]

52 minutes ago, jedimatt42 said:

I do this for free.

The work you've done is awesome and I'm grateful for everything you've contributed for this community.   The TIPI brings me joy every day. 

 

 

I repeated my test a sidecar TIPI and RPi zero with similar results, so I'm 80% sure its just the lower performance of the zero bring out a corner case that may not show up under normal testing.  For now, 1.61 works great for me, and I'm stick with it.  Let me know if there is anything I can do to help. 

[Omega-TI]

Just now, J-Data said:

The work you've done is awesome and I'm grateful for everything you've contributed for this community.   The TIPI brings me joy every day. 

Me too.  Matt made one of those rare gadgets that if it disappeared tomorrow, all the fun would go away.  

[+arcadeshopper]

I'm able to duplicate the telnet issue here w zerow
Works fine on pi3
Also seeing some comm issues on zero
Also the activity light is solid on the zero now.. wasn't on 1.x



Sent from my LM-V600 using Tapatalk

[+jedimatt42]

I was able to reproduce some flaky behavior for a bit when the PI first powers up... while the cpu load was over 100%   

After it settled down, it behaves fine for me... -- are the PI's being separately powered? During power up the power draw can be higher than normal also, and PI's operate erratically when under-powered.

 

There might be things we can do to make the powered from 4A experience more viable... you can turn off WIFI, and take care to stop more services that we aren't actually using... I didn't prune down the Raspbian at all... as there wasn't a need... normally a PI Zero W should run at around 30% cpu load ( buster days ) 

 

 

[dgrissom]

2 minutes ago, jedimatt42 said:

I was able to reproduce some flaky behavior for a bit when the PI first powers up... while the cpu load was over 100%   

After it settled down, it behaves fine for me... -- are the PI's being separately powered? During power up the power draw can be higher than normal also, and PI's operate erratically when under-powered.

 

There might be things we can do to make the powered from 4A experience more viable... you can turn off WIFI, and take care to stop more services that we aren't actually using... I didn't prune down the Raspbian at all... as there wasn't a need... normally a PI Zero W should run at around 30% cpu load ( buster days ) 

 

 

This may or may not be useful?

For the record.  I am powering my PI Zero on a separate power supply.  I usually leave it on to maintain TIPI folders and files and let my poor old console cool down.  If my machine is going to freak out, it is usually just after TIPI/PI startup.  Sequence:  Start nanoPEB, RPi, Wait 30 sec. , start console for TIPI. 

Anytime the nano is hooked into the system, I run it's 32k and I switch off the TIPI's 32K.  

Is this issue related to the CRUBASE firmware changes?

[fimbulvetr]

My pi zero w is powered on its own with an “official” raspberry pi power supply that came with it and I keep it powered on all the time,  but I had the weird CRU 2000 issue and whatnot.

[+helocast]

23 minutes ago, jedimatt42 said:

I was able to reproduce some flaky behavior for a bit when the PI first powers up... while the cpu load was over 100%   

After it settled down, it behaves fine for me... -- are the PI's being separately powered? During power up the power draw can be higher than normal also, and PI's operate erratically when under-powered.

 

Certainly not out of the realm of possibility ... gray/brown outs are tough to track.

I do NOT power the PI separately, because I remove original TI power supplies and power the whole console with an external Meanwell supply

which keeps more amps on all three rails, +12, +5, and -5. I'm not rich enough to own anything to measure the plus up on the power busses over

what the original TI supply provides nor would I know how to quantify that, sorry.

Doug

 

 

 

[dgrissom]

1 minute ago, fimbulvetr said:

My pi zero w is powered on its own with an “official” raspberry pi power supply that came with it and I keep it powered on all the time,  but I had the weird CRU 2000 issue and whatnot.

Are you still experiencing it, or did the rpi settle down and the issue went away? (or the 2.4 upgrade fixed it?)

 

I haven't experience it.  Lord (and JEDIMATT) knows I had my own set of problems with the upgrade!   Ain't smug, just puzzled as usually I am the one who has the problems.

   

 I might have been there during one or two of the connection tests.  The BBS responded just fine but no login activity. I was able to telnet in myself so I attributed it to a bot scan or some other internet tomfoolery. 

I can TELNET (it was probably me that triggered the clicking.  I did not log on  ?  )

 

I haven't detected the CRU change.  I only see it during a CALL TIPI and while running Force Command.   It is always >1000  (>1100 on my nanoPEB.) 

[fimbulvetr]

28 minutes ago, dgrissom said:

Are you still experiencing it, or did the rpi settle down and the issue went away?

I reflashed and retried about half a dozen times last week with the same problems, then went back to the old version. I haven’t tried upgrading since then.