OpenEuphoria

1. Raspberry Pi

• Posted by newphil82 Mar 07, 2012
• 5537 views

Raspberrry Pi is (I am told - do your own googling!) a small circuitboard with modern stuff including USB and other links - price less than £30 - intended to replace old computers like Sinclair Spectrum: the aim is to stimulate amateur and kid's programming: they say this interest is declining. The buyer must provide a keyboard, a TV(?), a mouse - but can use e.g. BBC BASIC ( a card must also be provided, with a Linux distro and a bit of permanent store space). Perhaps there'll be some unexpected inventions with a cheap "toy" like this. I'm going for more info.

POINT OF ALL THIS? Doesn't it sound like an opportunity to push Euphoria a bit? Needs someone a bit more "with it" than myself though! Any interest?

3. Re: Raspberry Pi

• Posted by DerekParnell (admin) Mar 07, 2012
• 5457 views

I suspect the main road block will be the C compiler that is supplied with it. If its a recent release of gcc then we should be in a good position.

5. Re: Raspberry Pi

• Posted by ghaberek (admin) Mar 08, 2012
• 5394 views

You can download Debian Squeeze from their site to load directly onto the device. Debian Squeeze includes gcc 4.4 which should work just fine (correct me if I am wrong, I often am about C/C++ programming).

It's a Linux environment just like everything else. If we can compile Euphoria for ARM (which we can) then we can build a deb (Debian) or pacman (Arch Linux) package to easily distribute it to other Raspberry Pi users. From there it's a matter of documentation (which we have) and examples/tutorials (which we are working on).

-Greg

7. Re: Raspberry Pi

• Posted by Jerome Mar 08, 2012
• 5425 views

I agree! I've cross-compiled the Euphoria arm branch using Code Sourcery GCC which is based on 4.5.2, and the produced binaries work well in QEMU for the Debian image. I'm also going to test out the Arch image, but there shouldn't be any difference as far as Euphoria is concerned!

This would be fantastic! I was planning to wrap the necessary C calls for GPIO access, but native Euphoria support would be great.

Thanks,
Ira

9. Re: Raspberry Pi

• Posted by rkdavis Mar 31, 2012
• 5341 views

I have remote access to a Raspberry Pi alpha board running the fedora f14 remix and I just tried the http://openeuphoria.org/eubins/linux/4.1.0/arm-32-bit/eubin-arm-cortex-a8-2012-01-13-ee49c6b8a340.tar.gz binaries on it.

It's a bit on the slow side but it does run.

Press Enter...[ukscone@raspi demo]$ cd bench 
[ukscone@raspi bench]$ ls 
sieve8k.ex  sieve8k.pro  sieve8k.pro2 
[ukscone@raspi bench]$ eui sieve8k.ex 
Prime Sieve Benchmark 
Count: 1028, Largest: 8191 
time: 141.11 
[ukscone@raspi bench]$ eui sieve8k.ex 
Prime Sieve Benchmark 
Count: 1028, Largest: 8191 
time: 59.75 
[ukscone@raspi bench]$ eui sieve8k.ex 
Prime Sieve Benchmark 
Count: 1028, Largest: 8191 
time: 57.49 
[ukscone@raspi bench]$ 

11. Re: Raspberry Pi

• Posted by rkdavis Mar 31, 2012
• 5184 views

and a quick & dirty video of it running :) http://www.youtube.com/watch?v=TMixJbJCfS8

13. Re: Raspberry Pi

• Posted by useless_ Apr 01, 2012
• 5111 views

Congrats on it running! But i am concerned about the sieve8k test taking 57 seconds? I just ran it on a 12 year old 2.4Ghz desktop computer, and it was done almost instantly. The Pi is running 700Mhz, i expected faster code execution from it. Any idea what is holding it back?

Have you been able to plug into your lan and get online with it?

useless

15. Re: Raspberry Pi

• Posted by rkdavis Apr 01, 2012
• 5065 views

I ran the same binaries on an ecafe slim hd netbook that is an 800mhz arm7 device and sieve8k took 26 to 27 seconds.

by the way the configure script needs a tiny tweak as the grep on the uname -s (line 63) should either be grep -i or check for arm rather than ARM as all the arm devices I have uname -s returns lowercase.

i don't have the ability to compile on the raspberrypi itself as it's a shared device with people doing "real" work on it but i'll rebuild the binaries using scratchbox2 and see if that helps

17. Re: Raspberry Pi

• Posted by Jerome Apr 01, 2012
• 5036 views

Thanks for update on the Raspberry Pi! To add another data point, I ran the Sieve benchmark on my Nokia N900 with an ARMv7 Cortex-A8 overclocked to 805 MHz.

Prime Sieve Benchmark 
Count: 1028, Largets: 8191 
time: 27.51 

I know comparing different ARM architectures (ARMv6 to ARMv7) isn't apples to apples, but I was hoping the Pi would be comparable to my N900 CPU wise. I'm sure we'll find out more when they start shipping!

Thanks,
Ira

19. Re: Raspberry Pi

• Posted by DerekParnell (admin) Apr 01, 2012
• 5018 views

Something like this ...

eui tests/t_bundled.e 

21. Re: Raspberry Pi

• Posted by Jerome Dec 26, 2012
• 4358 views

I've updated the Raspberry Pi wiki page with some information about cross-compling Euphoria for the Raspberry Pi. My next side project is to attempt to patch GPIO/SPI support directly into Euphoria. I plan on doing a robotics project and would also love to have direct GPIO access from Euphoria!

Happy holidays,
Ira

23. Re: Raspberry Pi

• Posted by ChrisB (moderator) Sep 03, 2021
• 1768 views

Hi Kat

Yeah, I wrote that , you can hear my dulcid tones on the youtube video. I think it demos quite nicely the use of wiringPi.

What undefined calls - maybe I can point you in the right direction.

Cheers

Chris

25. Re: Raspberry Pi

• Posted by katsmeow Sep 03, 2021
• 1737 views

Thanks, Chris. What i didn't know when i wrote that was the use of "wiringpi" and where the include files were. I zoomed down the webpage and, expecting one OE file that contained the total code to operate the pins, missed the include files. I expected nothing more than a peek() or poke() or puts() or getc() to access the pins. I found pinMode() and digitalWrite() and immediately went on a search for them and could not find them in any OE manual. I felt like that was the start of a rabbit hole looking for include files to an OS i have no clue about. Indeed, i found the webpage of the author of wiringpi, and he pretty much says "don't use this", based on hackery and different raspi versions. So i didn't edit my post here about about not having code defining pinMode() and digitalWrite(). I remember reading something by a nix guru that such devices in nix are all treated the same, as if they were files, and were accessed with simple read() and write() commands. A couple hours of web searching and reading was not enlightening.

This is like buying a "car" and then needing to locate all the actual parts and programming spread all over the world for completing the "car" before you can use it. It's not your fault, it's just the way it is.

Well, it does. But it's like demoing changing the tailight bulb on a car by showing the new one operates after all the work is done to change it (without showing the work).

Kat