Now the ctrace command returns the following error:
trace read failed: RTEMS_UNSATISFIED.
I think the problem lies in rtems_capture_read function call in
capture_support.c file. Im trying to debug the capture engine code. Does anyone
how to resolve this?
> On 26-May-2016, at 23:56, vivek kukreja
On 26/05/16 16:06, Mudit Jain wrote:
Hi Sebastian & Andre,
In the last IRC meeting, Gedare had mentioned that you have previously
worked on the SD card driver.
I was working on the SD Card driver for Rpi.
I was going through the driver code that has been ported. I was able
to browse and g
On Thu, May 26, 2016 at 5:55 PM, Martin Galvan
wrote:
> On Thu, May 26, 2016 at 5:42 PM, Olufowobi, Habeeb
> wrote:
>> Hi Martin,
>>
>> I am using the Qemu version defined in the RSB which is
>> 42d58e7c6760cb9c55627c28ae538e27dcf2f144.
>
> That seems to be fairly recent; I'll give it a shot myse
On Thu, May 26, 2016 at 5:42 PM, Olufowobi, Habeeb
wrote:
> Hi Martin,
>
> I am using the Qemu version defined in the RSB which is
> 42d58e7c6760cb9c55627c28ae538e27dcf2f144.
That seems to be fairly recent; I'll give it a shot myself and get back to you.
__
Hi Martin,
I am using the Qemu version defined in the RSB which is
42d58e7c6760cb9c55627c28ae538e27dcf2f144.
I haven't tried the current Qemu master since all suggestions have been
pointing to the older versions.
I will try the current master and will update you with my findings.
Regards,
Habee
Hello all,
it seems that Raspberry Pi QEMU emulation cannot work
with current RTEMS BSP because it uses BCM2835_TIMER_
as the main clock source, see
rtems/c/src/lib/libbsp/arm/raspberrypi/clock/clockdrv.c
which is mapped to
#define RPI_PERIPHERAL_BASE 0x3F00
#define BCM2835_TIMER_BASE
That's odd, I've used that BSP many times before and it always worked fine.
The BSP README (and patches) are quite old, and IIRC their purpose was to
actually make Qemu
emulate the board properly. Any fairly recent version of Qemu shouldn't need
any additional
patching; I was running RTEMS on it
That's odd, I've used that BSP many times before and it always worked fine.
The BSP README (and patches) are quite old, and IIRC their purpose was to
actually make Qemu
emulate the board properly. Any fairly recent version of Qemu shouldn't need
any additional
patching; I was running RTEMS on it
Hello,
I have forgot to include START_ADDR=0x8000 definition in the last e-mail
EXE_NAME=rtems/arm-rtems4.12/c/raspberrypi2/testsuites/samples/ticker/ticker.exe
START_ADDR=0x8000
arm-rtems4.12-objcopy -R -S --strip-debug -O
binary "$EXE_NAME" "$EXE_NAME.bin" || exit 1
cat "$EXE_NAME.bin
Hello Mudit and others,
On Thursday 26 of May 2016 17:57:21 Pavel Pisa wrote:
>
> ~/repo/qemu/qemu-build/arm-softmmu/qemu-system-arm \
> -M raspi2 \
> -serial stdio \
> -s -S
>
> The last two options enable GDB support and stop QEMU
> after initialization. I redirect serial line I/O
> to con
On Thu, May 26, 2016 at 6:16 PM, vivek kukreja wrote:
>
> Hello all,
>
> I'm facing a problem with function tracing. I made changes to rtems-tld
> command to ouput a CTF metadata file but i need sizes of arguments and return
> values at compile-time to be put in the metadata file.
> For now i ha
hello Alan,
thanks much for testing.
On Thursday 26 of May 2016 18:04:47 Alan Cudmore wrote:
> Hi Pavel,
> Here is what I have been able to try so far:
> rtems git head:
>“old” firmware - what I have been using for tests
>Works on RPI A+
>Works on RPI 2
> latest firmware f
Hi Sebastian,
The Qemu version mentioned in the ReadMe file does not exist in the Qemu
repository. I have tried several old version of Qemu (1.0.1, 1.0, 1.0-rc3,
1.0-rc4, 1.1-rc1, 1.1) with and without the patches. Some build
successfully but got the same error message as above while other builds
Hello mudit,
Às 15:06 de 26-05-2016, Mudit Jain escreveu:
Hi Sebastian & Andre,
In the last IRC meeting, Gedare had mentioned that you have previously
worked on the SD card driver.
I was working on the SD Card driver for Rpi.
I was going through the driver code that has been ported. I was a
Hi Pavel,
Here is what I have been able to try so far:
rtems git head:
“old” firmware - what I have been using for tests
Works on RPI A+
Works on RPI 2
latest firmware from raspberry pi github
Works on RPI A+
Does not work on RPI 2
Your rtems-rpi-devel
Hello Mudit,
On Thursday 26 of May 2016 16:06:52 Mudit Jain wrote:
> This mail is also a follow up from the IRC chat yesterday, in context of
> configuring QEMU to emulate RPi2. This email thread can be used to
> communicate the information regarding the same.
I have used my build of qemu-system-
Hi Sebastian & Andre,
In the last IRC meeting, Gedare had mentioned that you have previously
worked on the SD card driver.
I was working on the SD Card driver for Rpi.
I was going through the driver code that has been ported. I was able to
browse and get a top level overview regarding the ported
Hello all,
I'm facing a problem with function tracing. I made changes to rtems-tld
command to ouput a CTF metadata file but i need sizes of arguments and
return values at compile-time to be put in the metadata file.
For now i have yet to put actual variable sizes. Any recommendations how to
go abo
I am sorry Gedare i couldn't appear for the meeting. I was travelling and i
couldn't check my mail. I will be present for the next meeting or if you
could schedule another meeting this week itself. I'm maintaining a few
documents on Google docs and will upload a blog by tomorrow.
Also i'm facing so
Hello Alan,
thanks for the report.
On Thursday 26 of May 2016 04:03:21 Alan Cudmore wrote:
> 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 t
20 matches
Mail list logo
