Re: RKI Image for Raspberry PI 2

I just tried the firmware in the repository above ( did not realize the whole git repo was over 3 gigs! ) I backed up my RTEMS pi SD card and copied the contents of the firmware "boot" directory to my card. I replaced kernel.img and kernel7.img with my RKI images for the Pi and Pi2. RTEMS boots o

Re: RKI Image for Raspberry PI 2

A couple of days ago, I created a new Ubuntu 16.04 virtual machine, built the RSB toolchain ( same version as in your log ) and built the RKI image for sparc/sis, raspberrypi, and raspberrypi2. They all work for me. I used these options to build RTEMS: ../../rtems-git/configure --target=arm-rtems

Re: IRC meeting follow-up

I am extremely sorry that there was an unexpected power cut here.So I am briefing my project's aim and the work I planed to do this week. Main task of the project is to map RTEMS file API to lower level of LwIP API and test it on emulated i386 machine.As I said my exams were completed on 10

Re: [rtems commit] cpukit, testsuite: Add rtems_printf and rtems_printer support.

On 25/05/2016 21:30, Sebastian Huber wrote: I get now an undefined reference error: Making all in loopback gmake[6]: Entering directory `/build/git-build/b-sis/sparc-rtems4.12/c/sis/testsuites/samples/loopback' sparc-rtems4.12-gcc -B../../../../../sis/lib/ -specs bsp_specs -qrtems -mcpu=cypress

Re: [PATCH 3/3] score: Add Status_Control for all APIs

These seem good. Not able to look thoroughly, but fairly mechanical. On Wed, May 25, 2016 at 9:48 AM, Sebastian Huber wrote: > Unify the status codes of the Classic and POSIX API to use the new enum > Status_Control. This eliminates the Thread_Control::Wait::timeout_code > field and the timeout

Re: Errors while building USB DWC OTG driver

On Wed, May 25, 2016 at 7:12 PM, Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 25/05/16 14:59, Deval Shah wrote: > >> >> On Wed, May 25, 2016 at 3:07 PM, Sebastian Huber < >> sebastian.hu...@embedded-brains.de > sebastian.hu...@embedded-brains.de>> wrote: >> >> If you get >

[PATCH 2/3] posix: Fix sem_init() with too large initial value

Close #2721. --- cpukit/posix/src/seminit.c | 7 ++- testsuites/psxtests/psxsem01/init.c | 12 2 files changed, 18 insertions(+), 1 deletion(-) diff --git a/cpukit/posix/src/seminit.c b/cpukit/posix/src/seminit.c index cc47312..249edf6 100644 --- a/cpukit/posix/src/semi

[PATCH 1/3] Fix semaphore post overflow status

Close #2720. --- cpukit/posix/src/semaphoretranslatereturncode.c | 5 +--- cpukit/posix/src/sempost.c | 14 -- cpukit/rtems/src/semrelease.c | 1 + cpukit/rtems/src/semtranslatereturncode.c | 2 +- cpukit/score/include/rtems/score/coresemimpl

Re: Errors while building USB DWC OTG driver

On 25/05/16 14:59, Deval Shah wrote: On Wed, May 25, 2016 at 3:07 PM, Sebastian Huber > wrote: If you get On 25/05/16 10:19, Deval Shah wrote: I got the following result. nm: 'a.out': No such file from nm `find

Re: Errors while building USB DWC OTG driver

On Wed, May 25, 2016 at 3:07 PM, Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > If you get > > On 25/05/16 10:19, Deval Shah wrote: > >> >> I got the following result. >> >> nm: 'a.out': No such file >> >> >> > from > > nm `find build -name '*bcm283x_dwc_fdt*.o` > > the this is the

Re: RKI Image for Raspberry PI 2

As suggested by Alan, I did copy the image, rki.bin to kernel7.img, However rtems doesn't boot in RPi 2 . For the same firmware I tried with the raspbian kernel7.img, That works fine. The attachment contains the commands used for installing RTEMS and logs from RKI image creation for RPI2 log.25.

Re: [rtems commit] cpukit, testsuite: Add rtems_printf and rtems_printer support.

I get now an undefined reference error: Making all in loopback gmake[6]: Entering directory `/build/git-build/b-sis/sparc-rtems4.12/c/sis/testsuites/samples/loopback' sparc-rtems4.12-gcc -B../../../../../sis/lib/ -specs bsp_specs -qrtems -mcpu=cypress -O2 -g -ffunction-sections -fdata-sections

Re: Errors while building USB DWC OTG driver

If you get On 25/05/16 10:19, Deval Shah wrote: I got the following result. nm: 'a.out': No such file from nm `find build -name '*bcm283x_dwc_fdt*.o` the this is the first issue you have to resolve. Read the man pages of nm and find to figure out what these commands do. You must have

Re: Errors while building USB DWC OTG driver

This might help for debugging. 1. Code on which I am building raspberrypi BSP https://github.com/deval-maker/rtems-libbsd 2. Testsuits whcih contains #include or #include are having this redefination error. On Wed, May 25, 2016 at 1:49 PM, Deval Shah wrote: > I got the following result. > > n

Re: Errors while building USB DWC OTG driver

I got the following result. nm: 'a.out': No such file I searched a bit. And got to know that DWG OTG was already ported to RTEMS by this commit https://github.com/RTEMS/rtems-libbsd/commit/ba446132d4e9efbc1ffd7f4dc4fbfde7f531b740 . So when I cherry-picked, somewhere, some devices or resources a

Re: Errors while building USB DWC OTG driver

On 25/05/16 09:12, Deval Shah wrote: That is here in this commit https://github.com/gtament/rtems-libbsd/commit/173af003ef084acd2391269e3dcabb0954053289. I don't see an obvious error. What gives an nm `find build -name '*bcm283x_dwc_fdt*.o` ? -- Sebastian Huber, embedded brains GmbH Add

Re: Errors while building USB DWC OTG driver

That is here in this commit https://github.com/gtament/rtems-libbsd/commit/173af003ef084acd2391269e3dcabb0954053289 . On Wed, May 25, 2016 at 10:58 AM, Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > Hello Deval, > > where is this DWC OTG driver code? The driver must have the right