Adafruit touchscreen (AR1100)

Great stuff. If you do find out a ‘native’ process, I wonder if it’s something that could go on the wiki here…?

Hi,

I am new to RIsc OS and I have been very impressed by its speed and lightness.
I want to use it for some applications. All of them need touch screen solutions. I was very happy to find out you could make it work. But I am not sure to understand how you did it?
It seems to me that you have changed the code inside the OS itself then compiled the OS to make a new version?
I was wondering if it was possible to achieve the same result with a module?
Is somebody working on it?

Thanks

Chris

I’m not sure if Chris Mahoney got round to submitting the changes to ROOL or not, but I should be able to commit them directly to CVS when I get home tonight. Then you should just need to wait a day or two for the autobuilder to produce a new set of ROM builds (supposedly it happens every night, but recently it looks like it’s either not happening so often or there’s an extra delay somewhere. Either way, I’ll post here once the ROMs are ready)

I did submit the changes, but never heard anything back. I’ve heard that some submissions have taken months so was just being patient, but it sounds like you’re on top of things. Thanks :)

PS. I’m pretty sure that my post on page 2 contains the entirety of the submitted changes.

Edit: And it’s in! Thanks again to everyone that helped with this; I’ll test the autobuilt ROM once it’s available.

Thanks, I can’t wait to try it with my display

Sorry, last months I’m a little bit busy mostly with non RISC OS thinks. I will also try soon as possible. The changes are in the tarballs for “self compiling”?

I’ve just looked at the Pi tarball and it’s not included yet. It’s in CVS so should be in the tarballs soon.

Have found. I hope I found the time this evening to play around with. I have a small Adafruit (RPi) and bigger from Chalk (RPi, Beagle) and Chipsee (xM). The Chalk and Chipsee are working as a display with RISC OS and I hope with “touch” soon.
Thanks a lot.

The tarballs and ROMs have been updated since my last post. Unfortunately the ROM doesn’t want to boot on my Pi (SWI &42701 not known) so no testing today, I’m afraid.

Hmm, that’s a Squash SWI. Interesting! I’ll take a look tonight, unless someone gets there first.

I’ll also let ROOL know that the downloads all seem to be a day behind (it looks like the autobuilder builds everything as expected, but then the downloads only get uploaded/linked a day later)

SWI &42701 is Squash_Decompress. Maybe you can build a new ROM from tarballs or try to decompress the daily with rompress (rompress -d infile outfile) and use it non compressed or recompress with “*rompress -Z infile outfile”.

I’ll also let ROOL know that the downloads all seem to be a day behind (it looks like the autobuilder builds everything as expected, but then the downloads only get uploaded/linked a day later)

Possibly a scheduling issue – the builds may not have finished when the scheduled upload occurs?

SWI &42701 is Squash_Decompress. Maybe you can build a new ROM from tarballs or try to decompress the daily with rompress (rompress -d infile outfile) and use it non compressed or recompress with “*rompress -Z infile outfile”.

That error shouldn’t be related to use of compressed ROMs (the compressed ROMs use ZLib, and the decompression code doesn’t make any SWI calls)

Unfortunately the ROM doesn’t want to boot on my Pi (SWI &42701 not known)

Assuming it is the ordinary Raspberry Pi daily build at issue here then the build of 30-Jun-15 has booted up here without any error on my Mk1 Raspberry Pi.

Now that’s interesting! I’m on a B+ but I can’t imagine that that’d make any difference. Can a third person please give it a go?

Edit: I’m going from 5.21 to 5.23 so I wonder whether I’ve ended up with something incorrectly unplugged. I know that this was an issue from 5.20 to 5.22 so I suspect that I may have hit the same problem. I should be in bed by now though (the joys of being on the other side of the world) so it’ll need to wait until tomorrow!

I should not go to lunch break with an unsend post ;-)
So I have not seen Jeffreys first answer.

Can a third person please give it a go?

Are there that many of us?

FWIW the the 30-Jun-15 ROM is also good on the Iyonix and RPCEmu (Mac).

the joys of being on the other side of the world

Here on this side of the world it is so hot that the Iyonix started up, with its networking working, first time.

I’ve retested the ROM, this time not retaining my old CMOS settings, and it boots up fine. The AR1100 works too :)

Too fast for me ;-)
The new ROM works with my B+.
Now I will try any things.

No success at all. Maybe I make a mistake.
How should I use this?

With mine, I can just connect the USB cable and touch the screen, and the pointer will follow my finger. There isn’t any configuration required¹; it “just works”.

¹ Getting the desktop onto the screen via HDMI is a little trickier and requires a CONFIG/TXT tweak documented on the Adafruit site. But there is no configuration needed to get the touch elements working.

Touch works not. Display works with my B+ via HDMI with 1280×800. “Touch” is USB No.5 HiD N-trig DuoSense. Plug before or after boot… the same.
Use a comparable Display with my xM (not HDMI, internal LCD port), “touch” via USB, the same.
Both with the latest ROM.

I tested 4 different touch displays from 4 different manufacturers, only one of them works fine. 1 freeze the raspberry and I have to start it again and for the 2 other ones the mouse icon don’t move.
they are all supposed to use the mouse pointer protocol with absolute coordinates in single touch mode. I will try to find out if there is some difference with the one who works.
Since I am new to Risc Os, can you tell me what will happen next with this OS change?
Congratulation to Chris for his work.

Thanks

I tested 4 different touch displays from 4 different manufacturers, only one of them works fine. 1 freeze the raspberry and I have to start it again and for the 2 other ones the mouse icon don’t move.
they are all supposed to use the mouse pointer protocol with absolute coordinates in single touch mode. I will try to find out if there is some difference with the one who works.
Since I am new to Risc Os, can you tell me what will happen next with this OS change?
Congratulation to Chris for his work.

Thanks

Sorry for this mistake :-)