I noticed something odd in the ARM Client *command processing, but assumed I was just misreading it. It looks like there is an actual error there. It looks like host errors aren't being collected correctly.jms2 wrote:Some other puzzling things I've noticed with the ARM1176 processor are:
a) *GO isn't recognised, and just hangs the machine. By contrast other * commands which need to be passed across the Tube are recognised, eg *DIN works. If *GO isn't implemented shouldn't it just report "Bad command"?
b) Any other unrecognised * commands also seem to cause a hang, rather than "bad command". I discovered this by mistyping something.
Which banner? The line that says 'BASIC'? That's not the banner, that's the title of the selected language. What is called the banner is the very first line, the line either displayed by the MOS or by the Tube Client on initialisation (and modified by the 'display banner' OSBYTE) , and says something along the lines of "BBC Computer" or "6502 Tube", etc.jms2 wrote:c) The banners at the top of the screen report the OS message, then "Master MMFS" then "BASIC". That can't be right though - 6502 basic won't work and sure enough all I get is a * prompt. I don't understand where this banner comes from.
The line that says 'BASIC' says 'BASIC' because BASIC is the default language on your system, so on reset, the MOS is selecting BASIC, printing it's title, then passing it over the the Tube Client for the Tube Client to do whatever it wishes to do with it. If the Tube Client is not a 6502 then the Tube Client will generate an error saying something along the lines of 'This is not XXXX code'.
The MOS has absolutely no knowledge or ability to know what CPU is on the other side of the Tube, it's the responsibility of you, the user, to select an appropriate foreground application to run on the other side of the Tube.