Hi again,
Having conquered mandelzooming, I'm now giving Helios a try. My TRAMs may be a little small for Helios, but hopefully most of them aren't *too* small.
Well, things are working well when I run on TRAM 0 only, but I'm having bad luck going any further than that. I see this error message when the network server attempts to boot the next eligible TRAM connected to TRAM 0, which is a T414 with 1 MiB of RAM:
https://photos.app.goo.gl/e7e6wySWZMmhrBJbA
The critical error messages seem to be:
ns: failed to boot processor 03 via link 2 of processor 00
ns: reported fault was 0xd105000a
In Helios, decoding the fault code by typing `fault d105000a` reports that ns is experiencing a timeout. Does anyone know what might cause this? I think the TRAM should be healthy enough since it works with CSA Mandelzoom and since it passes `rspy /zmx`
and `rspy /f` tests. Some thoughts:
- Is a 15 MHz T414 too slow for Helios?
- Would host.con for an 8 MHz PC/AT need a BOGOMIPS setting? Surely not...
- Some TRAMs on this network don't have enough RAM for Helios, but those aren't the ones that are having this trouble. Could they still be a problem?
For reference, my B008 is configured in the out-of-the-box way described under "A Single Board for Developing Software" in the B008 manual (
http://transputer.net/mg/b008ug/b008ug.html#x1-150002.4.1).
You can see all other details of my network and my TRAMs here:
https://drive.google.com/file/d/1mQWEg_Z7exJCgEMe-1S1oqLBgUiYT5R3/view?usp=sharing
Now for some rspy questions:
1. I'd like to use rspy to reconfigure the c004 switch. It can do this, but it needs a file in "iswitch" or "swc" format. Is there a good reference for this format anywhere?
2. Is there any way to have rspy tell TRAM 0 to issue a subsystem reset?
3. Why does rspy /ch produce the line "reset { driver; ; null_ra.d }" instead of "reset { driver; ; tram_ra.d }"?
4. Why does rspy number my TRAMs as 0,1,3,4,5,6,7,8? Where's #2?
Thanks for any help!
--Tom
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)