Let's get started with a Pandora port

Thats my hope ;-)

To make yourself I am unfortunately too stupid, I can only complain :-(

The battery monitoring rogram shows me the voltage. How I can see the state of charge. Or is the icon too small on the Pandora?

The charging LED does not always under Linux.

At the moment the charge state is only output to the log file. Sorry!

I’ll hopefully have a proper battery monitor program available within a few weeks.

No problem. No need to apologize you.
See above.
Which log file?

You can enable the logging by editing the program and setting log% to TRUE. You can also change log$ to specify the filename. Note that if you change log$ you’ll also have to change the *settype on line 31 (or download the fixed version that’s been updated to use log$ in the settype).

I’ve just checked in the following – I think I made it in time for the ROM build:

• SDCMOS now looks for both $.CMOS and $.!Boot.Loader.CMOS, so you can use the Raspberry Pi FAT+FileCore disc images with OMAP machines
• PandoraKey now supports the nubs + gamepad controls:
  • Left nub is mouse movement
  • Right nub is mouse buttons. It’s the same as Linux, so left = select, up = menu, right = adjust, down = double click select
  • Gamepad is the same as linux too – cursor keys on D-pad and page up/down/home/end on Y/X/A/B.
  • The Pandora key is currently Alt-gr, and pressing L1+R1 is Break.
  • Most of the functionality that was available via Fn+Enter has now been removed (since it’s available via the nubs & gamepad). However a few bits remain, e.g. Print Screen, Scroll Lock, etc.

Let me know if you have any thoughts on how to improve the keyboard layout.

I take the Pandora to work with;-)
Thank you very much.

Sorry. Yesterday, I had little time. Was a very long day.
The described things by you are working very well.
SDCMOS I did not try.
Two things have struck me. Your battery monitor program does not longer work and after a soft-off Linux no start up directly. A reset of the Pandora is necessary.

Thank you. I will try even more. Then you get more response.

Fist response: No SHIFT + double click works

Latest changes:

• tilde, back tick, and forward tick now work
• Audio works. I think it might be quieter than Linux, so I’ll have to investigate that. Also the sound setup plugin doesn’t work yet.
• The startup keyboard scan now uses the Pandora keyboard instead of a USB one
• I’ve fixed the 2nd SD slot not appearing on the iconbar if the slot is empty on startup

If you set bq% to FALSE then the battery monitor should work properly. I’ll look into the other issues.

I have a little time for a short test.
Your changes are working. The sound is good. MP3 with DigitalCD I have tested.
I have any curiosities with the keyboard. I’m not sure how to describe it. Shift is fixed, even for mouse-select …
Alls closed windows are on the Pinboard and are only closeable with additional ESC pressed…
Normally shift doubkle click does not work … I have to try even more.
Many thanks

There is a bug where a key will get stuck down, it’s probably that which you’re seeing. I need to try and find out what’s causing it.

It is possible the last pandorakey is the problem. I remember at first Thomas has build a clean keyboard driver. For emulate the mouse he use a complete other way. It is possible the fist stable pandorakey is better to use.
I will check my SDCards. May be I have the old source here, may be it is at home on the NAS or may be I haven’t. Thomas is also not at home.
Many thanks

Not sure where to drop this request,
Just updated the rom for my beagle board an now all my settings are messed up.
It won’t remember the screen mode i set in !configure nor will it remember my network settings :-(
Any pointers?

Oh, and my mouse is acting up now. not working until i keep clicking and moving until suddely it starts working with intermittent pause.

I have a feeling the configuration settings not working are being caused by your boot sequence being out of date. Try following these instructions to fix VIDCBandwidthLimit and see if that improves things.

Alternatively, if it’s been a long time since you last updated your disc image, you might want to consider starting again with a fresh image. There have been a few useful changes over the past few months which you could be missing out on (e.g. new date & time plugin in Configure with NetTime support; the clock setup window in Alarm is no longer there).

I’m not sure what could be causing the mouse issues. Loose cable, hopefully?

Jeffrey: Thanks for the VIDCBandWidthLimit hint,

My Choices:Boot.PreDesk.Configure.!Run file now contains

|Set Alias$VIDCBandLimit X VIDCBandwidthLimit 2000000000 2000000000 2000000000
|VIDCBandLimit
Set PreDesk$Configure <Obey$Dir>.Monitor
/<PreDesk$Configure>

Thus commenting out the VIDCBandLimit stuff.

Also needed to rmreinit some unplugged networking modules and i will try to see if all is kept even over a power cycle.

The mouse is part of a wireless keyboard and mouse combo so no loose wires there.
It may be that the changes in the mouse driver make it slow to detect or something.
With old roms it would ‘just work’ without hassle.

For those interested: it is a Trust Wireless Deskset (has a USB dongle)
The keyboard works perfectly from the start. Mouse however seems to have some startup delay and can show some intermittent pause on the latest RISC OS ROM.

Best regards,
Jan Rinze.

I´m a little bit confused. I have create a new 32GB ADFS SDCard for the Pandora. I use the ROM and the HDImage from yesterday. Now I wouldt setup my desktop but no since 20 years knowing things (any) works. No desktop-safe via shutdown menu, no Pinboard-save, ,Boot-configure…. look at and Run produce a internal data abort… I can create a !Desktop file per hand and set the options for Filer_boot, Filer_opendir etc. by myself but I´m sure, the most things are going automatic on my xM last year. If I back home next week I will contol this on xM and Panda…

Shutdown —> restart + R1 ends in a data abort error and the CLI.
Later press R1 works as restart with bootmenu.

Try again with tomorrow’s ROM – I think all the errors you’re getting are being caused by the bug I introduced in SDCMOS.

Sorry, means this today or tomorrow (I have a time problem ;-))? I can not see any changes in the today ROM. It was a short test. I hope I have more time in the evening.

Sorry, means this today or tomorrow (I have a time problem ;-))? I can not see any changes in the today ROM. It was a short test. I hope I have more time in the evening.

We all have days like that :-)

The new ROM builds are there time stamped for early Oct 4th – they may not have transferred to the download server until sometime this morning, during our working day, and of course at work we always work and don’t access technical forums. :-|

This is actually a connectivity test.

Yes, it’s the Oct 4th ROMs I’m talking about.

Maybe in future I should wait until after the ROMs are uploaded :)

This is was I have tested. But I have see no changes at the short test. I hope I have a little time in the next hours.

I’m more confused! The ROM download after Lunch is a other after 9 PM! Both Oct. 4th…
After lunch I can UMTS-connect via ComCentre, now never. After lunch restart+R1 failed, now not…
The first download after lunch was very slow, the second normal…

I have after almost every restart (soft off, restart + R1, Pandora + slider …) a different behavior. I’m a bit stumped. Is it possible to do that on the old Pandora things be different?
Once the Pandora was a few hours off, ComCentre working again. Is it possible that data residues remain after a restart, which disappear after a longer break? That would explain the different behavior.

I’m not sure what the problem could be. RAM gets cleared on startup by the HAL, so it shouldn’t be that. Maybe there’s something extra I need to do to make sure the USB controller gets reset properly.

I also need to work out why Linux often hangs on startup after RISC OS has been run. Maybe that’s a symptom of the same problem.

I think you’re right. After your comment I tried some reboots. There are always problems with the UMTS stick when I come with active USB from Linux or RISC OS and boot RISC OS. With RISC OS I have no choice, in Linux I can disable USB before restarting. From RISC OS to Linux re-start takes longer than a normal boot.