Any updates about RiscOS on the Raspberry Pi?

Haven’t had any problems with sound on my end, even after updating to the latest ROM.

Before rebooting I write protected this file !Boot.Choices.Boot.PreDesk.Configure.Monitor

Brilliant, this worked thank you!

I also partially solved the graphics off the side of the screen issue. Turns out it’s an ‘overscan’ problem, well documented on other Pi sites. However – the solution (setting ‘overscan_left / right / top / bottom’ to positive values in the config.txt file) results in very strange behavoiur on the RiscOS image:

With overscan set, the picture fits perfectly – but the hardware pointer and mouse coordinates are not scaled, so the mouse/pointer no longer works! (you have to click icons where they used to be, not where they are!)

Is this a known bug – or is overscan just not supported yet?

Steve

The sound issue appears to be dodgy firmware. I editted config.txt to force the sound to hdmi and it’s back

Is this a known bug – or is overscan just not supported yet?

I suspect it’s not supported properly.

I found one of my screens behaved differently with DVI and HDMI, it didn’t overscan in DVI.

(Also I have noticed errors in the firmware chosen, that weren’t in the previous versions. See above. Maybe there’s more issues.)

That is annoying, how some monitors assume you want overscan when you feed them an HDMI or composite signal. (My Dell 2001FP actually underscans considerably on composite, though.)

You need a different start.elf

Correct – just downloaded the latest firmware (start.elf, bootcode.bin and fixup.dat) and “RISC OS 448Mb” nice :-) just need to find something to fill up the memory now…

Jess, I seem to remember reading the sound doesn’t work if the GPU isn’t allocated enough RAM. Just something to consider.

I’m not sure if this is the right part of the forum to post these.

The Community Support section of the forum is supposed to be for general help getting things working, so it might be worth trying there for future problems. I don’t have a Pi so I cannot help!

Steve Drain wrote:

I have downloaded a Zip file, which contains a BZ2 file of almost identical length.

If I never see another bzip2 file again it will be much too soon. But that takes the biscuit.

As I’ve said elsewhere, that bz2 thing was a cock-up on the RPi side. We’ll have a new release out shortly which is just a zip of the image.

In the RPi forum discussion on TinyBASIC both swirlything and Steve Drain advocate RISC OS for its ease of using the best BASIC. To which Liz Upton replied:

I’ve been asked by Steve Revill not to announce it yet – there are some final tweaks he’s going to make before we can go live. (We spent Saturday at RISC OS London – Steve looks exhausted, poor thing.) You’ll be hearing ALL about it here very soon.

which (except for Steve R’s exhaustion) sounds like a good thing. But the Uptons are away for a period this month, so may I ask if ROOL will be posting to the RPi forum ‘very soon’? No pressure!

RC6 was only finished yesterday. It is now on the RPI web site download area (but not yet announced as such). So ‘very soon’ is quite probable…

I’m going to leak some news – the announcements/blog posts/etc are planned for Monday. And yes, I’m exhausted :( I’m on a week ‘holiday’ and I’ve spent the whole lot doing either housework or ROOL work. Hey ho.

It’s only been on the RPi website a few hours and the torrents are warming up nicely…
(and I’m looking forward to burning my 500GB/month bandwidth, so come play :-)

Hi,
I’m currently working on a Raspberry Pi target for QEMU.
You can get it from here : https://github.com/Torlus/qemu/tree/rpi
It boots Linux fine, but not RiscOS yet.

Could anyone provide me the debug output available on the UART, using the latest distribution, as provided here (using an older build) ? https://www.riscosopen.org/forum/forums/9/topics/997?page=2

Thanks in advance,
Greg

Nevermind, I managed to retrieve it, it isn’t as verbose as the previous one but well, here it is:

HalStartup
HalQueryPl
1D400000 007F8000 HalQueryPldone
1D400000 HalStartup2
00008000 00000000 1C000000 ROM start, RAM start, RAM size
ROM relocated
HalStartup3 .. rst  rend
00000000 1BA00000 HalStart from OS
1C000000 04000000 F5000000  HAL Init completed

Regards,
Greg

@Gregory: could you explain where your patches are (or are they added to the github repo?)
Also how do you start qemu-system-arm? I have tried various methods but all fail.
Is there a -M rpi?

could you explain where your patches are (or are they added to the github repo?)
Also how do you start qemu-system-arm? I have tried various methods but all fail.
Is there a -M rpi?

The git repository is here

I used these instructions to build and run it on debian. Although it doesn’t run. It gets as far as ‘ModuleInit’.

git clone "https://github.com/Torlus/qemu.git"
git checkout rpi
git submodule update --init dtc
./configure --target-list=arm-softmmu
make
sudo make install
qemu-system-arm -kernel RISCOS.IMG -initrd RISCOS.IMG -cpu arm1176 -m 512 -M raspi -snapshot -sd ./ro519-rc6-1876M.img -d guest_errors -serial stdio

RISCOS.IMG is the rom image.

Chris, thanks! the clue is that i need the rpi branch.
It now boots but gives a garbage screen. Will investigate.

$ ./qemu-system-arm -sd ./riscos-2013-07-10-RC11.img -serial stdio -kernel ./kernel.img -M raspi -cpu arm1176 -m 512 -d guest_errors
HalStartup
HalQueryPl
1C100000 007E9000 HalQueryPldone
1C100000 HalStartup2
00008000 00000000 1C000000 ROM start, RAM start, RAM size
ROM relocated
HalStartup3 .. rst rend
00000000 1BB00000 HalStart from OS
1C000000 04000000 F5000000 HAL Init completed
HAL initialised
IICInit
HAL_KbdScanSetup
HAL_CleanerSpace
Allocating decompression workspace
Decompressing ROM
Decompression complete
ROM decompression workspace freed
ROM access changed to read-only
InitCMOSCache entry
InitCMOSCache done
IMB_Full done
Keyboard scan complete
Reset CMOS
InitDynamicAreas
InitVectors
InitIRQ1
IMB_Full
VduInit
ExecuteInit
KeyInit
MouseInit
OscliInit
Enabling IRQs
IRQs on
HAL_InitDevices
SD: CMD7 in a wrong state
InitVariables
AMBControl_Init
ModuleInit

now a black screen and nothing else.

finally got around to get RISC OS 5 working on the Rpi.
I still have a huge black border around the screen and reading 25 pages of furum info feels intimidating.
Hopefully i will stumble over an easy fix somewhere in this forum (search function of the forum is quite poor)
With this last addition I now have a nice line-up with RiscPC, Beagle, Panda and RPi.

Edit: found the fix really fast with the forum search. Mea Culpa.

Feedback about Risc Os on (RC12) RPi:

Everything works well, except my SSD-Disk on USB.
it starts up soemetimes, most times Risc Os
doesn’t find it. Therefore i changed to a flash-drive.
The same prob on the micro router, i can’t get
an ip-adress over DHCP, after a soft reser of
Risc Os it works. Therefore i think the reason
for this could be the fast starting up of Risc Os.
Solved that with a fixed IP.
Also missing in CONFIGURE a setting for the sound-defaults
( volume, system-sound-type)
But: functionality is excellent. everything works
well. special nice is that FAT32FS is allready installed.
Risc Os on the Pi is allready at a point where i
can compare it with the RPC.

A big THANK YOU to all people who were and are
working to bring Risc Os forward.

After 10years away, i’m now back on a Risc Os
Desktop- Computer.

All my old stuff working still on RPi

Thank You

Me too, I’ve not used RISC OS since my A9Home back in 2008. Now, thanks to ROOL, Jeffrey Lee and others, I’m using RISC OS every day again.

Just downloaded 12a and it seems I can’t use over scan again without affecting the mouse offset. Is there any way I can get my desktop to fit all my screen.

You’re trying to use off-center overscan settings, right? (e.g. left/right overscan not set to the same value). It does look like there’s a bug with how RISC OS is dealing with that, although I’m not sure how long it’s been around for (I would have thought I would have tested that case when I first wrote the code, but that was quite a while ago)

Anyway I think I’ve got a working fix, so after a bit more testing tonight I should be able to check it in. Then on Friday you should be able to download a new development ROM and use that.