Hello,
the region name REGION_VECTOR is a bit misleading. For ARMv-7M the
vector table is in the .bsp_start_text section, see
"bsps/arm/shared/start/start.S". In the REGION_VECTOR there is only the
interrupt stack.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178
On 08/01/2020 20:09, Gedare Bloom wrote:
On Wed, Jan 8, 2020 at 9:33 AM Joel Sherrill wrote:
On Wed, Jan 8, 2020 at 8:03 AM Sebastian Huber
wrote:
On 03/01/2020 17:52, Gedare Bloom wrote:
Hello all,
Vijay noted in another thread that:
"For RTEMS, I don't see any preference mentioned
Hello Utkarsh,
On 08/01/2020 18:52, Utkarsh Rai wrote:
> So, finally after resetting almost every configuration on my system ,
> and rebasing the changes on the latest libsd commit I was able to build
> the libbsd successfully on my host for beagle BSP.
Great.
> I have been trying to get a
On 08/01/2020 19:31, Gedare Bloom wrote:
I agree completely on the proposed approach with Python tools.
Yes. Reading it I'm actually reminded about Google's approach toward
Python which includes many of the elements mentioned. Although their
guide is probably more comprehensive and verbose
Hello,
the introduction of specification items and generator tools has some
benefits. However, it makes things more complex. You also need to know
how things are connected. Instead of having a single hand written
content which you can immediately edit to do a modification, have to
know about
On 08/01/2020 19:49, Gedare Bloom wrote:
On Wed, Jan 8, 2020 at 7:55 AM Sebastian Huber
wrote:
Hello,
for the RTEMS pre-qualification activity we need a specification of
RTEMS. I would like to use this opportunity to move structured
information which is present in hand written and hand
I've been working on a Cortex-M4 BSP and its Qemu model has some
peculiarities requiring me to relocate the vector table to the end of the
available storage, at least temporarily. In the process of doing this, I
noticed that .rtemsstack is placed in REGION_VECTOR in the shared
linkcmds.base
On 03/01/2020 17:52, Gedare Bloom wrote:
Hello all,
Vijay noted in another thread that:
"For RTEMS, I don't see any preference mentioned in the docs for the
order or includes:
https://docs.rtems.org/branches/master/eng/coding-conventions.html
In libbsd, however, the FreeBSD style guide is
The Debian Linux variant for the Raspberry Pi (Raspbian) is still 32 bit
for both the Pi 3 and 4, so I would think 32 bit ports would run on both.
The Raspberry Pi 4 has a Quad Core A72, 1 to 4 Gigabytes of LPDDR4 SDRAM,
Gigabit ethernet, USB 3, Wi-fi and bluetooth. I have not looked into it
Hello,
for the RTEMS pre-qualification activity we need a specification of
RTEMS. I would like to use this opportunity to move structured
information which is present in hand written and hand formatted content
in the RTEMS documentation into a structured data format (YAML).
Documentation
Hi
Can the Pi Zero boot with TFTP like the wired versions? We are wondering as
this is how the automated testing for the Pi's is done.
We are hoping to setup at least one Pi from each basic generation (1, 2, 3,
4, and Zero) for automated testing.
Thanks.
--joel
On 03/01/2020 19:52, Gedare Bloom wrote:
OK must be something that got leftover on my filesystem during
bootstrapping and switching branches between 4.10 and master. Sorry
about the noise.
No, I added this file recently do document how the sptest.adb is generated:
Unfortunately, The Raspberry Pi Zero (1.3) does not have a network
interface, it just has the MicroSD card and the interfaces exposed on the
40 Pin GPIO header. (SPI, I2C, GPIO, UART, etc)
The Raspberry Pi Zero W adds the Wi-Fi/bluetooth module that the RPi 3 has,
but I'm guessing that won't work
So, finally after resetting almost every configuration on my system , and
rebasing the changes on the latest libsd commit I was able to build the
libbsd successfully on my host for beagle BSP.
I have been trying to get a test app to work for PRU drivers , as of now
the app cannot read the IRQs
On Tue, Jan 7, 2020 at 11:34 PM Sebastian Huber
wrote:
>
>
>
> On 07/01/2020 17:21, Gedare Bloom wrote:
> > On Tue, Jan 7, 2020 at 2:09 AM Sebastian Huber
> > wrote:
> >> On 03/01/2020 18:16, Joel Sherrill wrote:
> >>>
> >>> On Fri, Jan 3, 2020, 10:22 AM Gedare Bloom >>>
On Fri, Jan 3, 2020 at 7:26 AM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
> Hello Jose,
>
> On 03/01/2020 11:52, Jose Valdez wrote:
> Should be in rtems-tools? If so, in which place?
> >>> I think this is the best place given the information I have. I would
> >>> need to
On Wed, Jan 8, 2020 at 9:47 AM Joel Sherrill wrote:
>
>
>
> On Fri, Jan 3, 2020 at 7:26 AM Sebastian Huber
> wrote:
>>
>> Hello Jose,
>>
>> On 03/01/2020 11:52, Jose Valdez wrote:
>> Should be in rtems-tools? If so, in which place?
>> >>> I think this is the best place given the
On Wed, Jan 8, 2020 at 8:03 AM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
> On 03/01/2020 17:52, Gedare Bloom wrote:
> > Hello all,
> >
> > Vijay noted in another thread that:
> > "For RTEMS, I don't see any preference mentioned in the docs for the
> > order or includes:
> >
On Wed, Jan 8, 2020 at 7:55 AM Sebastian Huber
wrote:
>
> Hello,
>
> for the RTEMS pre-qualification activity we need a specification of
> RTEMS. I would like to use this opportunity to move structured
> information which is present in hand written and hand formatted content
> in the RTEMS
On Wed, Jan 8, 2020 at 9:33 AM Joel Sherrill wrote:
>
>
>
> On Wed, Jan 8, 2020 at 8:03 AM Sebastian Huber
> wrote:
>>
>> On 03/01/2020 17:52, Gedare Bloom wrote:
>> > Hello all,
>> >
>> > Vijay noted in another thread that:
>> > "For RTEMS, I don't see any preference mentioned in the docs for
On Wed, Jan 8, 2020 at 12:36 PM Gedare Bloom wrote:
> On Tue, Jan 7, 2020 at 11:34 PM Sebastian Huber
> wrote:
> >
> >
> >
> > On 07/01/2020 17:21, Gedare Bloom wrote:
> > > On Tue, Jan 7, 2020 at 2:09 AM Sebastian Huber
> > > wrote:
> > >> On 03/01/2020 18:16, Joel Sherrill wrote:
> > >>>
>
21 matches
Mail list logo
