RISC OS itself has nothing built in to control the GPIO ports, but I have added Raspberry Pi support to the GPIO module from http://www.tankstage.co.uk/Software .Wizard wrote:My webserver runs really well and most php stuff does what its supposed to do but I have yet to wire in my sensors via GPIO. I must have a butchers at the documentation first since I'm more or less in the dark when it comes to GPIO and RISC OS.
Sweet!!!tank wrote: RISC OS itself has nothing built in to control the GPIO ports, but I have added Raspberry Pi support to the GPIO module from http://www.tankstage.co.uk/Software .
This module will let you control the GPIO ports with a SWI interface.
It also detects any MCP23017 GPIO extenders fitted and allows control of them.
They both have been. You probably want to use Nettle - the version in PackMan comes with SSH support. Confusingly, there's another version (not in PackMan) called NettleSSH which is ancient and is almost certainly not what you want.SEDev wrote:For ssh you could try the packages offered by PackMan (NettleSSH, Openssh) but I'm not sure if they've been updated for ARMv6/v7.
You should unbzip2 that to get ro519-rc5-1876M.img and write that to SD with the usual SD write tools - looks like your unzip tool is pulling apart all the partitions in the image, which you don't want to happen.pygmy_giant wrote:Sorry to interupt but I downloaded riscos-2012-10-16-RC5.zip via the torrent, un-zipped it, got the ro519-rc5-1876M.img.bz file further unzipped that and got 0.fat, 1.img and '2'.
I have just uploaded a version that works OK with I2C on the rev 2 Pi......Grumpy Mike wrote:@tank
While the last alpha version of RISC OS could talk to the I2C lines, do you know if there is any way of switching it over to the second I2C bus that appears in the revision 2 boards?
The second I2C is not supported ATM in RISC OS.theom wrote:
RISC OS should detect what revision of board you have and select the I2C pins as appropriate, so if you speak 'I2C' it comes out of the same pins on P1 irrespective what rev you have. However rev2 boards also have a second I2C on P5 with RISC OS supports - I'm sure tank will be along in a moment to say if that works with his GPIO module.
Steve, the latest GPIO module also has 16 bit wide access to the ports using SWI GPIO_ReadExp32 and the other ...Exp32 calls to read and write the OE register and data registers (it reads/writes both 8 bit ports and sends/presents the data in the bottom 16 bits of the returned/sent register from the SWI's).Steve Drain wrote: I have written a much less comprehensve module, specifically with the Ciseco SliceOfPIO in mind, that communicates with this chip over IIC and allows 8-bit port operations. It is not yet registered or publicly available, but I can certainly send it to anyone interested.
In BBC BASIC you use indirected variables for PEEK and POKE, a much more powerful construct, eg:stylx wrote:I've read through the bbc basic manual and there isn't a peek or poke to be found ...
Code: Select all
and if you just want single byte indirection there is the ? operation so to peek at an address use:-there isn't a peek or poke to be found anywhere,
As I said, there are more things to find out about indirected variables, and that does not complete the list, yet.Grumpy Mike wrote: To complete the list and the confusion:
works as well.
Call me a splitter but ... is there a version of GCC(SDK) available for this flavour of RISC OS?
Can I just use the latest release from this page: (http://www.riscos.info/downloads/gccsdk/)
What compiled programming options are available?
for packages in general, can I just use any old RISCOS app or do I need architecture specific versions?
Yes, GCC 4.1.2 release 2 or later should be fine. Previous releases won't emit correct code on ARMv7 processors, which includes the Pi with the CPU set to ARMv7 strict mode (see below). GCCSDK (the cross compiler - build on Linux/Mac/etc, run on RISC OS) will also work.
It's complicated. ARM keep changing the instruction set, so there have been a variety of architecture changes which affect compiled programs. There's not really any concept of building for a specific architecture (armhf, armel, etc) - almost all RISC OS programs built today can run on an ARM2 from 1987 - the problem is running old programs on new hardware:for packages in general, can I just use any old RISCOS app or do I need architecture specific versions?