Hi all,
My project proposal
https://docs.google.com/document/d/1CN3ri7g6NJeFPb5h8y4smr1aziGWyXbiiXUsFMhdUu4/edit?usp=sharing
I tried to set up the JTAG Environment for the Beaglebone Black.
But I couldn't find the hardware anywhere in my country (Sri Lanka).
I tried to,
1. Find TI XDS
Hi Robin,
On Fri, Apr 30, 2021 at 2:36 AM Robin Müller wrote:
>
> Issue can be reproduced by doing the quickstart application build on Windows
> 10. The issue are backslashes in the absolute paths of the dependency paths
> which were not stripped from dependency paths on Windows,
> causing waf
On Sat, May 1, 2021 at 8:31 PM Joel Sherrill wrote:
>
>
> On Sat, May 1, 2021, 8:53 AM Niteesh G. S. wrote:
>
>> Just to provide more context,
>> When the CONFIGURE_APPLICATION_NEEDS_CONSOLE_DRIVER option is used
>> and no --console option is provided, the console driver defaults to PL011.
>>
On Sat, May 1, 2021, 8:53 AM Niteesh G. S. wrote:
> Just to provide more context,
> When the CONFIGURE_APPLICATION_NEEDS_CONSOLE_DRIVER option is used
> and no --console option is provided, the console driver defaults to PL011.
> In raspberry pi 3 and other models whose primary UART is not
Just to provide more context,
When the CONFIGURE_APPLICATION_NEEDS_CONSOLE_DRIVER option is used
and no --console option is provided, the console driver defaults to PL011.
In raspberry pi 3 and other models whose primary UART is not PL011, we get
no output.
This patch fixes that by linking the
When no console argument is given, the driver defaults to pl011
this results in no output in case of Rpi3 whose primary uart is
miniuart.
This patch fixes that by defaulting to the primary uart when no
console option is provided.
---
bsps/arm/raspberrypi/console/console-config.c | 12 +---
Hi,
I run rtems6 on my imx6ull board, just initialize a GPT timer to flash
a LED. I load rtems with barebox, after output some initialized messages,
system enters shell and stalls, interrupt(GPT timer, arch7 timer for tick) do
not happen again. Shell (connect to UART1,interrupt mode) still
This patch adds asserts to fix coverity defects
1) CID 1474437 (Out-of-bounds access)
2) CID 1474436 (Out-of-bounds access)
>From manual inspection, out of bounds access cannot occur due to
bounds checking but coverity fails to detect the checks.
We are adding asserts as a secondary check.
---
On Thu, Apr 29, 2021 at 9:25 PM Gedare Bloom wrote:
> On Wed, Apr 28, 2021 at 9:04 PM Niteesh G. S.
> wrote:
> >
> >
> >
> > On Thu, Apr 29, 2021 at 12:50 AM Gedare Bloom wrote:
> >>
> >> On Wed, Apr 28, 2021 at 11:30 AM G S Niteesh Babu
> wrote:
> >> >
> >> > This patch adds asserts to fix
