> On 11-Apr-2021, at 1:15 AM, Ida Delphine wrote:
>
>
> For some reason I get this:
> rtems-test: command not found
> I've used this command a few times and it worked. I don't know what I am
> doing wrong now...
> Any idea what I am doing wrong?
Did you add the path to the toolchain to your $
Both flagged by CID #1399638.
---
tester/covoar/TargetBase.h | 13 -
1 file changed, 13 deletions(-)
diff --git a/tester/covoar/TargetBase.h b/tester/covoar/TargetBase.h
index d13216d..6db08f2 100644
--- a/tester/covoar/TargetBase.h
+++ b/tester/covoar/TargetBase.h
@@ -122,19 +122,6 @
For some reason I get this:
rtems-test: command not found
I've used this command a few times and it worked. I don't know what I
am doing wrong now...
Any idea what I am doing wrong?
On Sat, Apr 10, 2021 at 12:43 PM Eshan Dhawan
wrote:
> Hi
> You can use rtems-test to run tests in a directory
> E
The following two patches update the Beagle BSP i2c driver to use
device tree based initialization and the documentation related to
it.
G S Niteesh Babu (1):
bsps/beagle: Refactored i2c driver
bsps/arm/beagle/i2c/bbb-i2c.c | 122 ++
bsps/arm/beagle/include/bsp.h
Refactored the i2c driver to parse register values from the device
tree rather than hardcoding them. But still the clocks have to
initialized manually.
---
bsps/arm/beagle/i2c/bbb-i2c.c | 122 ++
bsps/arm/beagle/include/bsp.h | 4 +
bsps/arm/beagle/include/bsp
The new i2c driver in the beagle BSP uses FDT based initialization.
This updates the documentation of the BSP about the same.
---
user/bsps/arm/beagle.rst | 41 +++-
1 file changed, 28 insertions(+), 13 deletions(-)
diff --git a/user/bsps/arm/beagle.rst b/user/
> On Apr 10, 2021, at 08:41 , wrote:
>
> The "powerpc/shared/console" code has the start-up console value fixed
> at 9600 baud. This changes the hard-wired constant "9600" in the code
> to the configuration setting "BSP_CONSOLE_BAUD" and adds configuration
> support in both the "waf" and the
From: Peter Dufault
The "powerpc/shared/console" code has the start-up console value fixed
at 9600 baud. This changes the hard-wired constant "9600" in the code
to the configuration setting "BSP_CONSOLE_BAUD" and adds configuration
support in both the "waf" and the legacy configuration systems.
From: Peter Dufault
The "powerpc/shared/console" code has the start-up console value fixed
at 9600 baud. This changes the hard-wired constant "9600" in the code
to the configuration setting "BSP_CONSOLE_BAUD" and adds configuration
support in both the "waf" and the legacy configuration systems.
From: Peter Dufault
When the PowerPC shared console baud rate starts at anything other than
9600 the termios code will set it to 9600 at the first open.
---
bsps/powerpc/shared/console/uart.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/bsps/powerpc/shared/console/uart.c
b/bsps/powerp
Hi
You can use rtems-test to run tests in a directory
Eg :
rtems-test --rtems-bsp=erc32-run --rtems-tools=$HOME/development/rtems/5
~/development/rtems/kernel/erc32/sparc-rtems5/c/erc32/testsuites/samples
Thanks
Eshan
> On 10-Apr-2021, at 5:01 PM, Ida Delphine wrote:
>
>
> Hello everyone,
Hello everyone,
I'm looking forward to work on automatic style checking and code formatting
for RTEMS as my GSoC project and will need to test that style changes do
not cause any implementation bugs. I will carryout this test by running the
full RTEMS testsuite. I've tried looking in the RTEMS docu
12 matches
Mail list logo
