AUN on Raspberry Pi not working

I haven’t touched an Arc for about 15 years, but I have just got myself setup with the Pi. I have dug out all my old code (BASIC) and most of it works. However the code that used the ECONET_ SWI calls does not work.

I’ve done some digging, and as far as I can tell, I should be able to get this working (since the new AUN NetI package should implement the same interfaces and just transport stuff via TCP/IP). I tried enabling AUN under the network settings (eg: there is a GUI and a checkbox for this!), but this doesn’t seem to have any impact. I’m pretty sure this is because the NetI module isn’t loaded properly at boot – I think I can see a message about this flash past on boot, however I don’t really know how to debug the boot sequence (eg: log files? slow it down?)

A smoking gun is that the *Networks command doesn’t work (not found) nor any of the other net commands. And my code still says SWI not known.

Anyone else managed to get AUN working? Any advice/suggestions? I’m pretty keen to see if I can make all my old code run.

Thanks

Dave

however I don’t really know how to debug the boot sequence (eg: log files? slow it down?)

http://www.avisoft.force9.co.uk/Reporter.htm

Martin must be busy, normally he’d have chipped in with the response I just gave…

Right.. downloaded that. Any hints as to how to use this to debug boot? I can see it mentioned but having not touched an arc for 15 years I’m going to need some pointers!

Whilst looking for somewhere to add some kind of debug enabler I stumbled upon !Boot.Choices.Internet.Startup which includes:

RMFind NetI 6.18 System:Modules.Network.NetI

If I run this via F12 I get:

File ‘System:Modules.Network.NetI’ not found; although this could be some kind of environmental thing I guess.

Ok so someone has this covered:

http://www.wrocc.org.uk/howto/article.php?id=bootlog

Will have a play around with this and report back.

File ‘System:Modules.Network.NetI’ not found

I’ve put a copy of this module here to try. It should use the messages that are already in ROM for the Net module.

On which note, it does beg the question whether “Net” in ROM should actually be “NetI”. Does anyone have a pointer to a handy facts based bite sized guide as to what the difference between “Net” “NetI” and “NetG” is? They’re all derived from the same sources so can’t be that different. The PRMs don’t mention NetI and NetG that I can see.

Ok fantastic! I will give this a try tonight. I assume I can stick it anywhere for now and then just *RMLoad it manually.

Ok so someone has this covered:

http://www.wrocc.org.uk/howto/article.php?id=bootlog

Will have a play around with this and report back.

That article can be useful, but don’t forget to look at the !Reporter !Help as well!
And if you need any further help, just ask.

Update (from my Pi!)

I got !Reporter working and it’s very useful. I can’t figure out where it writes the boot log file though, so I’m not convinced I’m seeing all the details of Boot, even though I can see the red splash notice on Boot which says it’s loaded. Very useful software though – thanks Martin.

I downloaded Sprow’s module and RMLoaded it and BAM, my applications now load, instead of saying SWI not known. So making progress. I guess I now need to figure out how to configure it all correctly. I appear to have no machine number (although only looked briefly) and the *Networks command still doesn’t work (strange?)

Thanks for the help.

I got !Reporter working and it’s very useful. I can’t figure out where it writes the boot log file though, so I’m not convinced I’m seeing all the details of Boot, even though I can see the red splash notice on Boot which says it’s loaded. Very useful software though – thanks Martin.

By default, Reporter only ‘displays’ in its window what it is logging, it does not ‘write’, although you can also write the results to disc if you wish. And it only logs what you have asked it to! During Boot it can log all commands issued and any errors raised.

Glad you are finding Reporter useful – you will only have scratched the surface yet!

I like !Reporter too – expect that it simply isn’t reliable on my Pi for some reason. At least, the FS API part. I have a load of debug stuff in Squeak that I can turn on and it attempts to open “Report:” and then fprintf’s to the returned file handle. Sometimes it works perfectly and often it simply refuses to open the filing system and the code devolves to a plain old text file log. I wish I could discern a pattern to the failures, but no luck so far.

expect that it simply isn’t reliable on my Pi

I know of no problems…! And unreported problems are unlikely to be fixed!! Even vague bug reports can sometimes be useful.

It’s hard to offer any bug report better than sometimes it worked perfectly, other times it didn’t return a file handle from
log file = open(“Report:”, “w+”);
I tried “a+” as well with no observable difference. I’ll happily try out any test you can suggest or indeed send you the application to play with.

log file = open(“Report:”, “w+”); I tried “a+”…

I have no idea what w+ and a+ mean! Please can you email reporter@av…. about this?

I have no idea what w+ and a+ mean!

Looks like the standard C fopen arguments. w+ is create a text file for update, or truncate to zero length, a+ is append, open text file or create for update, writing at the end of the file.

Dave wrote:
> I appear to have no machine number (although only looked briefly)

Yep, see my post from 4th Feb… same problem, no station/net number.
I didn’t get any answers :(

I’m trying to get AUN going as I’ve built USB Econet board which
appears on the USB as a CDC Ethernet device and converts between
AUN and Econet internally. I was going to run SoftMDFS as a server
on my Pi but may need to consider Linux + AUNd.

Hi Jason, I’m still working on this. So far I’ve got bits working. I do now have a machine number, as I expect, having defined an AUN map. My machine is 2 which matches last part of IP. This was using the NetI module downloaded from link above (many thanks!) The only strange thing now is with the network number which appears to be discovered by my software as 0 even though I know it should be 129 (and indeed things respond if I send messages to 129). So I’m getting close.

Hopefully at the end of all this we can get a Pi version that works out of the box! Loving having an arc again!

The only strange thing now is with the network number which appears to be discovered by my software as 0 even though I know it should be 129 (and indeed things respond if I send messages to 129). So I’m getting close.

That is correct. Networks are supposed to be numbered from 1 to 127 (Econet) and 128+ (AUN). Network 0 is special, it means “the current network”.

For instance, if you are station:
1.252
and there is a fileserver at:
1.254
and another at:
2.254
If we assume that the two networks are linked (some sort of bridge or gateway), then:
"254" (no network specified), 0.254 and 1.254 will all point to the same server.
The other must be explicitly specified as 2.254.

This is talking in terms of old-school Econet topology. For AUN, just assume network 1is 128 and 2 is 129, description still stands. ;-)

If your machine is ‘2’ on network ‘129’, your computer’s IP address for AUN should be 1.0.129.2.
This, obviously, cannot be used for anything that communicates with the “real” internet, as that is actually a real IP address! [link via TinyURL as Textile’s horrible excuse for a parser has outdone itself]

Wow! Cheers Rick. So it sounds like I have it working.

My next step is to debug a client server app I wrote in 1995! But I will get there. And then finally I’ll throw all this old code on GitHub.

Superb. Thanks for Sprow for providing the module.
I’m completely new to RO but managed to find out
where to bung it to make it all start at boot.

I now am able to log into SoftMDFS from BeebEm
over AUN.

Next step to finish off the firmware on my USB
Econet adapter so I can get a real Beeb to log
into SoftMDFS on the Pi.