Hi Hesham,
I don't have an answer for you, but you may be able to find some help or
example code on the raspberrypi.org forums.
A couple of examples:
http://www.raspberrypi.org/phpBB3/viewtopic.php?t=40183p=336705
http://www.raspberrypi.org/phpBB3/viewtopic.php?t=40665p=332205
I avoided the
The Raspberry Pi could use drivers:
SPI / SD card access,
I2C Bus
Ethernet ( this could be hard since it is a USB device ) ,
HDMI/graphics console,
Sound?
Alan
On 9/2/2013 4:35 PM, Karel Gardas wrote:
On 09/ 2/13 07:33 AM, Ritesh Harjani wrote:
I have Raspberry pi + ti stellaris lm4f120
This is for RTEMS Source Builder. Binutils 2.23.x did not build on Ubuntu 13.10
because of texinfo 5.1. The problem is fixed in Binutils 2.24, so the check for
texinfo 5.x is no longer needed for this configuration.
---
rtems/config/tools/rtems-gcc-4.8.2-newlib-cvs-1.cfg | 5 -
1 file
This is for the RFS file system. There is a bug in the group search algorithm
where it will skip groups, causing blocks to remain unallocated. This is
dependant on the size of the blocks and number of blocks in a group, so it does
not always show up. The fix corrects the skipping of groups
This is for the RFS file system. There is a bug in the
rtems_rfs_bitmap_create_search loop. It is supposed to iterate over the range
of bits in a search element ( usually 32 bits ), so it should loop through bits
0 through 31. Instead it loops through 0 - 32, causing some blocks not to be
This is for the RFS file system. The statvfs call reports 1 block free when the
file system is full because it does not account for the superblock in its
calculation of free blocks.
This is a simple fix that adjusts the number of blocks reported to account for
the superblock. We may want to
I was just able to build the sparc-rtems4.11 toolchain on Centos 6.5 ,
64 bit
This was on a fresh Centos 6.x VM with all updates, no previous RTEMS
tools installed.
Alan
[alan@centosvm Desktop]$ sparc-rtems4.11-gcc -v
Using built-in specs.
COLLECT_GCC=sparc-rtems4.11-gcc
I checked around at work and there is some interest in using the OpenRISC
architecture, but no definite plans.
Another idea is to advance the Microblaze port.
Alan
On Mar 4, 2014, at 1:22 PM, Hesham Moustafa heshamelmat...@gmail.com wrote:
On Mon, Mar 3, 2014 at 6:54 PM, Gedare Bloom
There is a Microblaze port out there, but it has not been released.
But, I agree that the availability of the toolchain should be a factor.
Tough call: If we do the microblaze port, it may be duplicating work that
may eventually become available to the RTEMS project. If we do the OpenRISC
port,
From my limited research, it looks like the emmc controller in the
Raspberry Pi BCM2835 may be the way to go.
It looks like it is a high level controller for the SD/MMC card slot on the
Pi.
Since this is a custom controller, I don't think there would be an existing
driver in RTEMS.
It seems that
else in rpi-boot has a different license.
All files in rpi-boot use a similar licence, so I will be using some code
from rpi-boot as a base for this.
Great.
On Thu, Apr 3, 2014 at 10:06 PM, Alan Cudmore alan.cudm...@gmail.com
wrote:
From my limited research, it looks like the emmc
On Wed, Apr 16, 2014 at 4:49 PM, Joel Sherrill joel.sherr...@oarcorp.comwrote:
On 4/16/2014 2:06 PM, Alan Cudmore wrote:
On Thu, Apr 10, 2014 at 7:11 PM, Andre Marques
andre.lousa.marq...@gmail.com wrote:
On 04/04/14 20:19, Joel Sherrill wrote:
On 4/4/2014 1:15 PM, Gedare Bloom wrote
On 4/17/2014 5:42 AM, Andre Marques wrote:
On 04/17/14 03:22, Alan Cudmore wrote:
On Wed, Apr 16, 2014 at 4:49 PM, Joel Sherrill
joel.sherr...@oarcorp.com mailto:joel.sherr...@oarcorp.com wrote:
On 4/16/2014 2:06 PM, Alan Cudmore wrote:
On Thu, Apr 10, 2014 at 7:11 PM, Andre
that could
be used as a HDMI console or host the RTEMS graphics toolkit.
Alan
On 4/16/2014 11:49 PM, Chris Johns wrote:
On 17/04/2014 12:22 pm, Alan Cudmore wrote:
The details of the GPU have been closed, and the linux port has relied
on a binary blob for the GPU firmware, but Broadcom recently
On Fri, Apr 25, 2014 at 6:07 PM, Andre Marques
andre.lousa.marq...@gmail.com wrote:
I'm taking this conversation to the list.
Sorry, I didn't realize that I did not reply to the list.
On 04/23/14 01:21, Alan Cudmore wrote:
On Tue, Apr 22, 2014 at 6:09 AM, Andre Marques
I will definitely try that out. It would be great to automate all tests on
this board.
It seems less than 10 seconds to load a 1 megabyte RTEMS image to the Pi
using JTAG.
Alan
On Mon, Apr 28, 2014 at 7:20 PM, Chris Johns chr...@rtems.org wrote:
On 29/04/2014 12:34 am, Alan Cudmore wrote
I recently tried to compile and run my RTEMS kernel image (
github.com/alanc98/rki ) on the latest git head. I was able to get past
a configuration option change:
#define CONFIGURE_MAXIMUM_TASKS 1024
kept the system from starting, so I changed it to 128 and it comes up.
But now I do not get a
and use it to load RTEMS images
to the Pi.
Alan
On Fri, May 2, 2014 at 6:48 PM, Chris Johns chr...@rtems.org wrote:
On 3/05/2014 3:07 am, Alan Cudmore wrote:
Chris,
I can use OpenOCD to load, run, break, resume, etc, but I am not having
luck with GDB yet.
Excellent.
I can connect
On 5/13/2014 3:48 PM, Andre Marques wrote:
On 05/09/14 03:24, Alan Cudmore wrote:
I have not had much time to figure out why GDB is not working with
the Pi/openOCD setup yet.
But I started documenting my setup. The hardware details are here:
http://alanstechnotes.blogspot.com/2014/05/a-low
Andre,
If you have not seen this library, please check this out:
http://wiringpi.com
It looks like a good resource programming the Raspberry Pi GPIO. It may
give you some insight and ideas about the GPIO API. The code appears to be
LGPL.
Alan
On Sat, May 24, 2014 at 8:37 PM, Gedare Bloom
OK, that's good to know. But it could at least help shape the RTEMS GPIO
API.
Alan
On Wed, May 28, 2014 at 3:08 PM, Gedare Bloom ged...@rtems.org wrote:
On Wed, May 28, 2014 at 11:56 AM, Alan Cudmore alan.cudm...@gmail.com
wrote:
Andre,
If you have not seen this library, please check
201 - 221 of 221 matches
Mail list logo
