Raven. A homemade Atari-like computer

[artik-wroc]

The base IO address for the bus is indeed gotten from ISA_BIOS though, and failing that it knows it for a few existing machines itself;
Hades: 0xFFF30000, Milan: 0xC0000000, Raven: 0x81000000, Panther: needs C__P2I cookie since it's completely wild west territory

The addresses that can be read from the ISA cookie are correct. There is some connection if the ping works. The router assigns the correct IP address (DHCP). Only the browser throws the message "server rejected the connection". I'm not giving up :)

[agranlund]

Only the browser throws the message "server rejected the connection". I'm not giving up :)

Hmnmn, not sure why it would matter but maybe you'll have more luck with another client?
I've tested with the standard ftp commandline client here but now I mostly use ncftpget/ncftpput to send and retrieve files.

(just to clarify in case it got lost in the original post; the normal uiptools webserver is not compiled in and for now until I've sorted out some compile issues it only runs the FTP server)

[artik-wroc]

My mistake. Now I understand. FTP connection works on both Hades and Panther. Great.
If it worked as a client, like Ghostlink (additional drive) it would be interesting :D
It's great, thanks a lot.

[agranlund]

Raven can now do in-system ROM flashing.
And now that I have that, I'm questioning how on earth I managed to cope without it for so long :)
For me, this will drastically reduce swapping of the rom simm between Raven and the programmer.
https://github.com/agranlund/raven/rele ... .A1.latest

Flashing a rom image from TOS:
1) run c:\raven\flash.ttp <filename>
(or just drag-and-drop a rom image onto that program)

You should see the power LED blink at a steady pace while programming is in progress.
Once finished, the computer will automatically restart itself.

Note that flash.ttp depends on already running at least the version which is currently latest. Thus you're going to need to flash that one with the simm-programmer as usual and the benefit of having in-system flashing will be next time you update.
I've only had a chance to test with the 2xSMD simm so far. Let me know if there are any issues with the 4xPLCC model.


The following stuff is probably mostly interesting for programmers who work on rom related code (?)

Flashing a rom image from monitor:
1) Run the monitor 'flash' command.
2) Initate a raw file transfer of the rom image from your connected serial terminal.

Flashing a rom srec from monitor:
1) No command necessary, just send the .s19 file from a connected terminal same as you would for an srec ram program.
It will automatically detect if the srec was built for rom or ram and act accordingly.


You'll get to the monitor from anywhere by pressing the NMI button. All interactions with it are then over serial connection.
Alternatively, one can run c:\raven\mon.tos to interact with the monitor through TOS rather than from a serial terminal.

Raven boots with the serialport configured for 115200 baud as default.
Since this is quite slow I recommend for now to locally change in "sw/rom/mon/_boot.S" to something faster if you're working in rom code and flash over serial.
Ideally this should end up being some kind of setting that is somehow accessible at very early boot stage. NVRAM isn't, so possibly flashed to a section in rom. Next board revision is getting a few cpu-readable config jumpers which could be useful for situations like this.
Or perhaps the default should just be bumped up to something faster?

[Oldskool]

Maybe stupid question. But how do I use that uip tool. Does it need some arguments as it does not seem to start. Just got this network card but maybe it is not supported or so…

IMG_3099.jpeg

IMG_3100.jpeg

[agranlund]

Maybe stupid question. But how do I use that uip tool. Does it need some arguments as it does not seem to start. Just got this network card but maybe it is not supported or so…

Not a stupid question at all.
Put this line in C:\ISA_BIOS.INF should do the trick:

Code: Select all

dev.WSC8019.RTL8019.io = 300

(uip is hardcoded to look at port 300 for a compatible card. This is me being lazy, I should really make it ask isa_bios first.
My only defence is that the mint ethernet driver we borrowed from Hades is also hardcoded for 300 so that's where the card needs to sit for now anyway. I'd like to update or rewrite that one too at some point.)

[Oldskool]

Thanks for the help!
I normally would not bother with network stuff but this uip tool is great.
Indeed very easy.

And it works now!!

[Oldskool]

I really hate network stuff and reading text files but this network card I just need to get Mint online.
The webbrowser is really old but luckily the most important site works.
This Raven computer is just so much fun… :)

IMG_0004.jpeg

[Atarian Computing]

I really hate network stuff and reading text files but this network card I just need to get Mint online.
The webbrowser is really old but luckily the most important site works.
This Raven computer is just so much fun… :)

IMG_0004.jpeg

You can use http://wrp.atarinet.info as a rendering proxy to view any modern website. More info here: http://www.atarinet.info.

[Oldskool]

It seems your service is down but it was more to get it working (network). Not really going to use it for surfing :D

I’m really getting it now with that interleave thing/discussion. Was playing around with some settings in Mint in higher resolutions and the various aes versions and options but the speed is OK on the W32 but you just feel that slowness/screentearing a tiny bit. The Mach32 card is indeed just that tiny bit faster and it’s noticable in the desktop
A pity that that the resolution switching is a pain otherwise it would be a better. Especially in desktop use.

IMG_1817.jpeg