On 24/05/16 18:53, Olufowobi, Habeeb wrote:
Hi,
I was able to successfully built the lm3s69xx BSP. While I tried
running the hello.exe on qemu, I got the following hardware error.
Warning: nic stellaris_enet.0 has no peer
qemu: hardware error: ssys_read: Bad offset 0x6c
CPU #0:
R00=000
Hello Deval,
where is this DWC OTG driver code? The driver must have the right
DRIVER_MODULE() and MODULE_DEPEND() definitions.
On 24/05/16 20:04, Deval Shah wrote:
Hello,
Currently, I am working on porting USB DWC OTG driver on Raspberry Pi.
Last year Yurii Shevtsov worked on the same. So,
On 25/05/16 03:38, Gedare Bloom wrote:
I guess this means 1 more word of storage per thread queue in the MP
case, and 1 more dereference for each lock context access? It seems
reasonable.
No, there is no additional storage in the thread queue required. The
Thread_queue_Context resides on the s
On Tue, May 24, 2016 at 5:01 AM, Jan Kiszka wrote:
> Hi Wonjun Hwang,
>
> On 2016-05-24 10:53, 황원준 wrote:
>> I found Jailhouse Github repository and there are instructions for building
>> and installation for Linux.
>> I want to start coding quickly. however it is hard to build for
>> understand
Hello,
Currently, I am working on porting USB DWC OTG driver on Raspberry Pi. Last
year Yurii Shevtsov worked on the same. So, I forked the latest rtems-libbsd
and cherry-picked Yurii's commits. While building libbsd using waf, I got
the following error.
--
Hi,
I was able to successfully built the lm3s69xx BSP. While I tried running
the hello.exe on qemu, I got the following hardware error.
Warning: nic stellaris_enet.0 has no peer
qemu: hardware error: ssys_read: Bad offset 0x6c
CPU #0:
R00= R01= R02=87800800 R03=c100
R04=400fe
On Tue, May 24, 2016 at 1:13 AM, Chris Johns wrote:
> On 23/05/2016 22:37, Gedare Bloom wrote:
>>
>> How does this affect user applications?
>
>
> It should not but if a user has an application that is using the plugin
> interface there is a struct name change. The previous struct ended in '_t'
>
Hi Pavel,
I have pulled your branch and I am able to build the rki.bin using the
following commands.
mkdir b-rpi2
cd b-rpi2
../rtems/configure --target=arm-rtems4.12 --prefix=$sandbox/rtems-4.12
--enable-rtems-inlines --disable-multiprocessing --enable-cxx
--enable-rdbg --enable-maintainer-mode
We will have our first weekly IRC meeting for GSoC students tomorrow,
Wednesday May 25 10:00 A.M. Eastern Daylight Savings Time (EDT: UTC-4)
hence 14:00 UTC/GMT. The purpose of these meetings is for each student
to briefly (about 5 minutes) discuss what they have been working on,
and what they will
The RKI image and other RTEMS examples work on the RPI2. When I build for
the raspberrypi2 BSP, I have to copy the rki.bin ( or other example image )
to kernel7.img on the SD card. No other conversion should be required.
I recently tested the RKI image on the RPI2, so it should work.
Also, make s
Hello Mudit,
On Tuesday 24 of May 2016 16:17:07 Mudit Jain wrote:
> Hi Pavel,
>
> I have pulled your branch and I am able to build the rki.bin using the
> following commands.
>
> mkdir b-rpi2
> cd b-rpi2
> ../rtems/configure --target=arm-rtems4.12 --prefix=$sandbox/rtems-4.12
> --enable-rtems-in
Hello Mudit,
On Tuesday 24 of May 2016 14:35:46 Mudit Jain wrote:
> It would be great if you could prepare a personal fork . And as you
> mentioned it would be helpful for further RPI development as well.
there is my fork
https://github.com/ppisa/rtems
My changes are on "rtems-rpi-devel" branch
Hi Pavel,
It would be great if you could prepare a personal fork . And as you
mentioned it would be helpful for further RPI development as well.
Thanks
On Tue, May 24, 2016 at 5:53 PM, Pavel Pisa wrote:
> Hello Mudit,
>
> I do not have public RTEMS repo for RPi at this moment.
> I run against
Hello Mudit,
I do not have public RTEMS repo for RPi at this moment.
I run against mainline and all patches are in the series
[PATCH v2 0/7] Raspberry Pi VideoCore support for console on HDMI output
But I can prepare my personal fork on GitHub
if it helps with testing. For my TMS570 I use my pr
Hi Pavel,
I do have a RPI2 and can help in testing your series.
Could you provide me with the details of your repo and also the tests that
are to be performed so that your series can be ACKed for mainline
integration.
Thanks
On Tue, May 24, 2016 at 5:29 PM, Mudit Jain
wrote:
> In my scenario
---
cpukit/posix/src/condwaitsupp.c| 7 ++-
cpukit/posix/src/mqueuerecvsupp.c | 3 +--
cpukit/posix/src/mutexlocksupp.c | 2 +-
cpukit/posix/src/pbarrierwait.c| 3 +--
cpukit/posix/src/prwlockwrlock.c | 3 +--
cpukit
Get rid of the mp_id parameter used for some thread queue methods. Use
THREAD_QUEUE_QUEUE_TO_OBJECT() instead.
---
cpukit/libnetworking/rtems/rtems_glue.c| 1 -
cpukit/posix/src/condsignalsupp.c | 1 -
cpukit/posix/src/condwaitsupp.c| 1 -
cpuki
Account for the heap minimum block size.
---
cpukit/sapi/include/confdefs.h | 12
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/cpukit/sapi/include/confdefs.h b/cpukit/sapi/include/confdefs.h
index 95f29fd..d35aaa4 100644
--- a/cpukit/sapi/include/confdefs.h
+++ b/cpuk
We must call the MP callout for proxies if we unblock them after a
thread queue extraction. This was missing in
_Thread_queue_Flush_critical(). Move thread remove timer and unblock
code to new function _Thread_Remove_timer_and_unblock().
---
cpukit/score/include/rtems/score/threadimpl.h | 19 ++
In my scenario the build fails because the networking is disabled. I again
have done a clean build again as follows:
make clean
../rtems/configure --target=arm-rtems4.12 --enable-rtemsbsp=raspberrypi2
--enable-tests=samples --enable-networking --enable-posix
--prefix=/home/mudit/Desktop/sandbox/rt
Hello Mudit,
On Tuesday 24 of May 2016 11:17:44 Mudit Jain wrote:
> Hi All,
>
> For raspberry pi bsp, the RKI image using https://github.com/alanc98/rki is
> successfully build by modifying the Makefile as per the instructions given
> in the same .
>
> However when I try the same for raspberry pi
Hi,
You might need to edit the Makefile for the Raspberry Pi 2. I don't know if
passing in the command line variables are enough.
The RKI waf build has recently been updated, and I just tested it to make
sure it builds.
I also have a rki-drivers branch where I am starting to integrate i2c
drivers
Hi All,
For raspberry pi bsp, the RKI image using https://github.com/alanc98/rki is
successfully build by modifying the Makefile as per the instructions given
in the same .
However when I try the same for raspberry pi 2 bsp, the build fails with
the following error :
I found Jailhouse Github repository and there are instructions for building and
installation for Linux.
I want to start coding quickly. however it is hard to build for understanding
whole structure easily.
Can I get some instructions to build Jailhouse on RTEMS?
And I don't know other mentors
24 matches
Mail list logo
