> -Original Message-
> From: users On Behalf Of Sebastian Huber
> Sent: Donnerstag, 1. Februar 2024 07:48
> To: John Howard ; users@rtems.org
> Subject: Re: “AW:” ?
>
> On 31.01.24 18:20, John Howard wrote:
> > Lost in translation.
> >
> > Anybody here know what “AW:” in the Subject mea
> -Ursprüngliche Nachricht-
> Von: John Howard
> Gesendet: Dienstag, 30. Januar 2024 22:59
> An: Sommer, Jan
> Betreff: Re: AW: NOOBS
>
> Hi Jan,
>
> Thanks for your reply.
>
> I think the RTEMS dynamic loader can load other ELF’s. DL supports loading
> libraries from several differe
> -Ursprüngliche Nachricht-
> Von: Frank Kühndel
> Gesendet: Dienstag, 30. Januar 2024 11:03
> An: Sommer, Jan ; j...@rtems.org
> Cc: dwaine.s.mol...@nasa.gov; users@rtems.org
> Betreff: Re: AW: Rust on RTEMS
>
> Hello Jan,
>
> thanks for the info and all your efforts.
>
> Are you plan
Hi John,
> -Ursprüngliche Nachricht-
> Von: users Im Auftrag von John Howard
> Gesendet: Dienstag, 30. Januar 2024 02:56
> An: users@rtems.org
> Betreff: NOOBS
>
> I used RSB 5.3 to build RTEMS 5.3 for Raspberry Pi Zero W.
>
> (At least I think I did. Untested yet.)
>
> Several questio
Hi everyone,
Sorry for the delayed response.
Yes, that’s me. I am responsible for the RTEMS related work-package in the
“cRustacea in Space” project.
One of the goals is to create a prototypical port of Rust to RTEMS for our
example target platform (Xilinx Zynq).
The status is currently the foll
Hi Joel,
One of our colleagues was involved with the SW-PA for the GALA
(https://www.dlr.de/pf/en/desktopdefault.aspx/tabid-10617/18438_read-43017/)
and Janus (https://space.leonardo.com/en/juice) instruments of Juice.
Both instruments use RTEMS internally.
Fingers crossed…
Jan
From: user
> -Original Message-
> From: users On Behalf Of Sebastian Huber
> Sent: Freitag, 10. Februar 2023 14:23
> To: martinerikwerner@gmail.com; users@rtems.org
> Subject: Re: Determining resource usage for BSP drivers
>
> On 10.02.23 14:19, martinerikwerner@gmail.com wrote:
> > Some B
Ah, thanks for the clarification.
If I can be of any help with the porting, let me know.
From: Joel Sherrill
Sent: Mittwoch, 11. Januar 2023 14:08
To: Sommer, Jan
Cc: rtems-us...@rtems.org
Subject: Re: C++ math functions not available in namespace std
This happens on the architectures where s
Hello and happy New Year,
I stumbled upon a slightly weird problem with the current cross-compilers.
According to https://en.cppreference.com/w/cpp/numeric/math/fmax std::fmax
should be part of for >= C++11.
However, if I try to use it, I sometimes get "error: 'fmax' is not a member of
'std';
Hi Jens,
Is there a real need to have the telescope driver twice in memory?
Would it be enough to implement the driver as “object oriented” in C?
Then you would just need to create a context struct during initialization based
on the hartid with the correct interrupt assignment and base address of
> -Original Message-
> From: Sebastian Huber
> Sent: Wednesday, June 23, 2021 11:47 AM
> To: Sommer, Jan ; users@rtems.org
> Subject: Re: Heap allocation for libbsd overwrites IMFS
>
>
>
> On 23/06/2021 10:32, jan.som...@dlr.de wrote:
> > One of our applications for the Zedboard fails
Hello,
One of our applications for the Zedboard fails with fatal error after the setup
of the network stack in libbsd.
So far I traced it down to the point that the memory allocation for libbsd
overwrites parts of the IMFS of rtems.
When opening device files later this will lead to the crash.
Th
Unfortunately, this didn’t help:
Transfer rate: 4462 KB/sec, 236 bytes/write.
(gdb) run
The "remote" target does not support "run". Try "help target" or "continue".
I also tried target extended-remote and the -r option in SIS, but so far
without success.
Best regards,
Jan
From: jiri
Sen
Hello,
I tried to follow the example for using SIS, but use RISCV as the target
platform instead of SPARC
(https://docs.rtems.org/branches/master/user/tools/tester.html#building-rtems-tests).
However, while I can run ticker.exe of the griscv BSP perfectly in SIS, the
same application does not r
Thanks. I will have a look.
> -Original Message-
> From: Sebastian Huber
> Sent: Thursday, April 29, 2021 1:46 PM
> To: Sommer, Jan ; users@rtems.org
> Subject: Re: libbsd: React to link status change events
>
> On 29/04/2021 13:43, jan.som...@dlr.de wrote:
>
> > is there an easy way to
Hello,
is there an easy way to register a callback function or block until a link
status change of an Ethernet device occurs in the libbsd stack?
Searching for it, I found some references for EV_NETDEV in kqueue, but this
seems to be a legacy function which has been removed years ago.
In the co
> -Original Message-
> From: Sebastian Huber
> Sent: Friday, March 19, 2021 6:25 AM
> To: Sommer, Jan ; users@rtems.org
> Subject: Re: rtems-record-lttng: Corrupted timestamps after translating to
> CTF
>
> On 18/03/2021 23:06, jan.som...@dlr.de wrote:
>
> >>> The to_bt_scaler is quite
> -Original Message-
> From: Sebastian Huber
> Sent: Friday, March 5, 2021 5:46 PM
> To: Sommer, Jan ; users@rtems.org
> Subject: Re: rtems-record-lttng: Corrupted timestamps after translating to
> CTF
>
> On 05/03/2021 16:11, jan.som...@dlr.de wrote:
>
> > Some of the resulting CTF ev
> -Original Message-
> From: users On Behalf Of Chris Johns
> Sent: Thursday, March 11, 2021 6:07 AM
> To: Ida Delphine
> Cc: rtems-us...@rtems.org
> Subject: Re: Offline download of sources fails
>
>
>
> On 11/3/21 3:34 pm, Ida Delphine wrote:
> > Hello again,
> >
> > So I started o
Hello,
I try to do some performance measurements with the rtems-record functionality.
Since the target doesn't have Ethernet, but a lot of RAM, I collect all events
in a large buffer during runtime and flush the events via the
"record_dump_zlib_base64" method in the end.
This RTEMS side works we
Hi Rick,
I found some time to debug the driver on hardware today.
I submitted the driver to the devel mailinglist
(https://lists.rtems.org/pipermail/devel/2021-February/064525.html).
I didn't have a SPI device ready for testing, so I checked via an oscilloscope
and through loopback.
Both worked.
Hi Rick,
> -Original Message-
> From: users On Behalf Of Rick VanderWal
> Sent: Tuesday, February 9, 2021 9:21 PM
> To: users@rtems.org
> Subject: SPI Driver Implementation
>
> Hey All,
>
> I am looking for guidance in regards to the implementation of a SPI bus driver
> for my Zynq-700
Yes, I found the commit which fixes that.
I will prepare a ticket and a patch for backporting.
From: Joel Sherrill
Sent: Tuesday, February 9, 2021 1:16 PM
To: Sommer, Jan
Cc: rtems-us...@rtems.org
Subject: Re: Zynq: Reading from stdin returns immediately
Thia is related to the set method for
I stand corrected.
It works with current master.
That should make searching easier.
> -Original Message-
> From: users On Behalf Of jan.som...@dlr.de
> Sent: Tuesday, February 9, 2021 10:58 AM
> To: users@rtems.org
> Subject: Zynq: Reading from stdin returns immediately
>
> Hello,
>
> I
Hello,
I tried to read data from stdin via scanf in RTEMS5.1 for some user input for a
Zynq based board, but it returns immediately with 0.
Also fscanf, read or fgetc do not block and return immediately. The flags for
stdin show that the O_NONBLOCK flag is not set.
I tried to check with the term
From: Joel Sherrill
Sent: Friday, January 29, 2021 3:33 PM
To: Sommer, Jan
Cc: Jiri Gaisler ; rtems-us...@rtems.org
Subject: Re: riscv: gdb cannot connect to rtems runnin in qemu
On Fri, Jan 29, 2021 at 8:29 AM mailto:jan.som...@dlr.de>>
wrote:
Just tried again with the rv32imac BSP.
With
Just tried again with the rv32imac BSP.
With this gdb works.
Best regards,
Jan
> -Original Message-
> From: users On Behalf Of jan.som...@dlr.de
> Sent: Friday, January 29, 2021 3:10 PM
> To: j...@rtems.org; j...@gaisler.se
> Cc: users@rtems.org
> Subject: RE: riscv: gdb cannot conn
> From: Joel Sherrill
>
>On Fri, Jan 29, 2021 at 7:20 AM wrote:
>> Hello
>>
>> I just tried to debug a riscv test program running in qemu.
>> However, gdb could not establish a connection to qemu and produced the
>> following error:
>> /tmp/rtems/riscv❯ riscv-rtems6-gdb ticker.exe
>> GNU gd
Hello
I just tried to debug a riscv test program running in qemu.
However, gdb could not establish a connection to qemu and produced the
following error:
/tmp/rtems/riscv❯ riscv-rtems6-gdb ticker.exe
GNU gdb (GDB) 10.1.90.20210125-git
[..]
For help, type "help".
Type "apropos word" to search for
Thanks, Jiri.
Qemu worked fine for the rv32imafdc test binaries.
For the record, both qemu command lines worked well:
qemu-system-riscv32 -nographic -machine virt -m 2G -nographic -net none -serial
mon:stdio -bios ticker.exe
qemu-system-riscv32 -nographic -machine virt -m 2G -nographic -net non
>On Wed, 25 Nov 2020 at 15:41, wrote:
>> Hello,
>>
>> I tried to experiment a bit with the riscv BSPs.
>> I could run them using the SIS simulator, but failed with qemu.
>> Regarding qemu I found this ticket:
>> https://devel.rtems.org/ticket/3608
>>
>> In one mailinglist thread (from 2018) some
Hello,
I tried to experiment a bit with the riscv BSPs.
I could run them using the SIS simulator, but failed with qemu.
Regarding qemu I found this ticket:
https://devel.rtems.org/ticket/3608
In one mailinglist thread (from 2018) someone said it worked with a current
master version of qemu.
I ha
Hi Sebastian,
I tried to follow the implementation of the small tables, but had some troubles
understanding how it works.
> BSP_START_TEXT_SECTION static inline void
> arm_cp15_start_set_translation_table_entries(
> uint32_t *ttb,
> const arm_cp15_start_section_config *config
> )
> {
Hi Jonathan,
Thank you very much for the tip.
I did overwrite the translation table with an additional entry and can now
successfully access the device.
Cheers,
Jan
From: Jonathan Brandmeyer
Sent: Wednesday, November 18, 2020 5:01 PM
To: Sommer, Jan
Cc: RTEMS
Subject: Re: Acessing PL de
Hello,
We try to use the xilinx_zynq_zedboard BSP with some devices synthesized to the
PL, e.g. a Xilinx NS16550 Uart.
If I try to access any of the AXI registers, I get a fatal error with a vector
number 0x04 (undefined instruction).
Accessing the same register address from within a Xilinx stan
> -Original Message-
> From: users On Behalf Of Peter Dufault
> Sent: Thursday, November 5, 2020 3:11 PM
> To: rtems-us...@rtems.org
> Subject: Need help cleaning up git repository
>
> I'm not as good at "git" as I should be. I'd like some help cleaning up my
> git
> repository so t
> -Original Message-
> From: Sebastian Huber
> Sent: Wednesday, November 4, 2020 4:00 PM
> To: Sommer, Jan ; users@rtems.org
> Subject: Re: When to register termios devices?
>
> Hello Jan,
>
> if it is a custom BSP, why don't you add it to the console driver of this BSP?
>
> If you ad
Hello,
I try to register several termios devices in a custom BSP (based on RTEMS 5.1).
I tried to do this in the bsp_start function, but this fails.
My guess is, that it is because too early in the system initialization as the
rtems_filesystem_umask is set, so that no device nodes can be added by
Hello,
If colleagues have RTEMS related questions, I like to direct them to
docs.rtems.org to read the fine manual.
I noticed that in the releases section of the page 5.1 is not yet included.
Since with the work on RTEMS 6 the active branch documentation is diverging,
could you please also add t
Hi Karel,
> -Original Message-
> From: users On Behalf Of Karel Gardas
> Sent: Tuesday, September 8, 2020 7:32 PM
> To: Christian Mauderer ; Christian Mauderer
> ; users@rtems.org
> Subject: Re: How to use lvgl on pc386 BSP.
>
>
> Hello Christian,
>
> On 9/7/20 6:22 PM, Christian Maude
> I followed this tutorial from a GSOC student.
> https://medium.com/@mritunjaysharma394/installing-rtems-ecosystem-and-building-your-first-bsp-993d1cf38902
>
> This is how i've configured it.
> $HOME/development/rtems/rtems-5/configure --target=i386-rtems5
> --enable-rtemsbsp=pc386 --enable-t
> -Original Message-
> From: users [mailto:users-boun...@rtems.org] On Behalf Of Gedare Bloom
> Sent: Tuesday, August 25, 2020 9:15 PM
> To: Zacchaeus Liang
> Cc: RTEMS Users RTEMS
> Subject: Re: BSP missing
>
> Hi Zack,
>
> On Tue, Aug 25, 2020 at 1:02 PM Zacchaeus Liang
> wrote:
> >
> -Original Message-
> From: Chris Johns [mailto:chr...@rtems.org]
> Sent: Thursday, August 20, 2020 5:43 AM
> To: Sommer, Jan; j...@rtems.org
> Cc: users@rtems.org
> Subject: Re: Corrupted test marker with u-boot and zynq
>
> On 19/8/20 5:30 pm, jan.som...@dlr.de wrote:
> >> -Origi
> -Original Message-
> From: Chris Johns [mailto:chr...@rtems.org]
> Sent: Wednesday, August 19, 2020 1:25 AM
> To: Sommer, Jan; j...@rtems.org
> Cc: users@rtems.org
> Subject: Re: Corrupted test marker with u-boot and zynq
>
> On 18/8/20 6:26 pm, jan.som...@dlr.de wrote:
> >> -Origi
> -Original Message-
> From: Chris Johns [mailto:chr...@rtems.org]
> Sent: Monday, August 17, 2020 6:38 AM
> To: j...@rtems.org; Sommer, Jan
> Cc: rtems-us...@rtems.org
> Subject: Re: Corrupted test marker with u-boot and zynq
>
> On 17/8/20 12:48 am, Joel Sherrill wrote:
> > On Sun, Aug
Hello,
I try to create a setup to run the rtems testsuite on a Xilinx Zynq device with
u-boot.
I built everything with the 5.0.0-m2006-2 pre-release.
It now works in general, but quite a number of tests have a corrupted begin
test marker (see below).
This way, rtems-test does not recognize the t
> -Original Message-
> From: users [mailto:users-boun...@rtems.org] On Behalf Of Heinz Junkes
> Sent: Thursday, June 25, 2020 5:26 PM
> To: rtems-us...@rtems.org
> Subject: xilinx_zync_zedboard u-boot tftp load and run issue
>
> Hallo,
>
> i just can't get it to load and start a rtems-ex
Hi,
I tried to run some of the smptests on the RPi2 with the current 5-0 snapshot.
I built everything from scratch, but running the smp01.exe on our RPi2 v1.1
does not produce any output after:
RTEMS RPi 2B 1.1 (1GB) [00a01041]
I tried first to load the program via u-boot. Then I tried using t
> -Original Message-
> From: users [mailto:users-boun...@rtems.org] On Behalf Of
> jan.som...@dlr.de
> Sent: Tuesday, June 9, 2020 3:01 PM
> To: users@rtems.org
> Subject: RaspberryPi with U-Boot and FDT
>
> Hello,
>
> I recently updated my RaspberryPi2-Setup to a more recent version.
Hello,
I recently updated my RaspberryPi2-Setup to a more recent version.
So far we used u-boot and ran the ELF-binary directly using the "bootelf"
command.
Now with the commit "362cf319d4 - bsp/raspberrypi: Updated the console API" it
seems the console driver has been changed to require a FDT t
> Hi Jan,
>
>> Do you have the cross-compiler generated with rtems-source-builder in your
>> PATH?
>
> Yes
>
> I’m installing the RTEMS 5 with the Quick start on
> https://docs.rtems.org/branches/master/user/installation/kernel.html
>
> Then the step 5.3.4 Building a BSP with configure co
> -Ursprüngliche Nachricht-
> Von: Chris Johns [mailto:chr...@rtems.org]
> Gesendet: Mittwoch, 8. April 2020 02:57
> An: Sommer, Jan; users@rtems.org
> Betreff: Re: rtems-test with serial device and run.cfg
>
[...]
> > Which seems to be caused by this:
> >
> > Traceback (most recent call
> -Ursprüngliche Nachricht-
> Von: Chris Johns [mailto:chr...@rtems.org]
> Gesendet: Mittwoch, 8. April 2020 02:57
> An: Sommer, Jan; users@rtems.org
> Betreff: Re: rtems-test with serial device and run.cfg
>
> On 2020-04-07 23:37, jan.som...@dlr.de wrote:
> > I have trouble figuring out
Hello,
I have trouble figuring out how to run rtems-test with a custom command where
the output is captured through a serial console.
In my ini-file I used
bsp_tty_dev= /dev/ttyUSB2
tester = %{_rtscripts}/run.cfg
bsp_run_cmd= i386-run
target_off_command = i386-
> -Ursprüngliche Nachricht-
> Von: users [mailto:users-boun...@rtems.org] Im Auftrag von Sebastian Huber
> Gesendet: Mittwoch, 11. März 2020 09:17
> An: mojtaba nadi; users@rtems.org
> Betreff: Re: write a network driver
>
> Hello Mojtaba,
>
> On 11/03/2020 06:44, mojtaba nadi wrote:
> >
> -Ursprüngliche Nachricht-
> Von: Joel Sherrill [mailto:j...@rtems.org]
> Gesendet: Montag, 16. Dezember 2019 15:33
> An: Sommer, Jan
> Cc: rtems-us...@rtems.org
> Betreff: Re: Building rtems-libbsd for pc686
>
>
>
> On Mon, Dec 16, 2019 at 7:37 AM wrote:
>
>
> Hello,
>
>
> -Ursprüngliche Nachricht-
> Von: Sebastian Huber [mailto:sebastian.hu...@embedded-brains.de]
> Gesendet: Montag, 16. Dezember 2019 15:37
> An: j...@rtems.org; Sommer, Jan
> Cc: rtems-us...@rtems.org
> Betreff: Re: Building rtems-libbsd for pc686
>
[...]
> >
> > The code worked on the p
Hello,
I tried to build the branch 5-freebsd-12 for the pc686 BSP of the current RTEMS
master.
The compilation stops at:
[ 64/1156] Compiling freebsd/sbin/sysctl/sysctl.c
../../freebsd/sbin/sysctl/sysctl.c:72:10: fatal error: machine/pc/bios.h: No
such file or directory
#include
^~
Thanks,
I think I get it now.
So for example the
https://git.rtems.org/rtems/tree/bsps/arm/atsam/net/if_atsam.c is the legacy
one.
And https://git.rtems.org/rtems-libbsd/tree/rtemsbsd/sys/dev/atsam/if_atsam.c
is the newer version ported to libbsd.
Best regards,
Jan
-Ursprüngliche Nac
Hello everyone,
Since I just read the question from Fernando, I was wondering if the
(recommended) Ethernet stack of rtems-libbsd does work with the greth driver of
the drvmgr as well?
The greth driver, as most of the other Ethernet drivers of other BSPs, calls
the ether_ifattach function at s
Hi Chris,
> -Ursprüngliche Nachricht-
> Von: Chris Johns [mailto:chr...@rtems.org]
> Gesendet: Freitag, 26. Juli 2019 02:26
> An: Nils Hölscher
> Cc: Sebastian Huber; Sommer, Jan; users@rtems.org
> Betreff: Re: Problems running RTEMS on Raspberry Pi2
>
> Hi Nils,
>
> Many thanks for taki
Hello,
We are having troubles getting RTEMS to run on the RPi2.
We built the BSP from current master and used the firmware of a recent Raspbian
on the SD-Card, but could not manage to get any output on the UART.
We also tried to use an older version of the firmware as mentioned here by Alan
(htt
Hi Joel,
Thank you for the hint.
It worked and the testsuite runs through again now.
I attached a patch for the master branch.
Best regards,
Jan
Von: Joel Sherrill [mailto:j...@rtems.org]
Gesendet: Donnerstag, 18. April 2019 15:43
An: Sommer, Jan
Cc: rtems-us...@rtems.org
Betreff: Re: pc686:
Hello,
if I build the pc686 BSP with --enable-rtems-debug activated I can't run any of
the testsuites examples, but get the following error:
$ qemu-system-i386 -append --console=/dev/com1 -no-reboot -serial stdio
-monitor none -nographic -kernel
./build/i386-rtems5/c/pc686/testsuites/samples/
Hi Christian,
If your change is only regarding to the clock frequency then it should be
possible to simply pass the value to configure:
configure --target=arm-rtems4.12 --enable-rtemsbsp=altera-cyclone-v
BSP_ARM_A9MPCORE_PERIPHCLK=1000U
At least that is what we do with the microzed board.
Hello everyone,
Next Monday is the launch date for DLR's Eu:CROPIS satellite. Currently the
launch is scheduled for 18:48 UTC.
Its main task is to test a new life-support system in space which processes
(artificial) urine to create fertilizer and water for growing tomatoes.
You can find more in
Hello,
we will have access to a Xilinx Zynq ultrascale+ soon.
It has 4xA53 cores.
If I understand it correctly they are based on AArch64 which is currently not
supported by RTEMS.
However, running the processors in 32bit mode would be sufficient.
I have some problems determining what is already
Hi Leon,
I am not sure if that is something for your use case, but DLR recently
published the core-parts of its OS-abstraction layer as FOSS.
You can find it here: https://github.com/DLR-RY
Depending on build system configuration it builds for RTEMS (classic API),
Linux (POSIX-API) and FreeRTOS
TOFU:
Thank you for the fast fix, Joel.
All i386 bsps compile again with the traditional bootstrapping.
Best regards,
Jan
From: Joel Sherrill [mailto:j...@rtems.org]
Sent: Friday, January 05, 2018 6:04 PM
To: Sommer, Jan
Cc: rtems-us...@rtems.org
Subject: Re: [i386] Invalid BSP-Error
Hello,
We found some unexpected behavior when rebuilding the current RTEMS master for
i386.
If we run the update as usual: pull current master, bootstrap, configure and
finally make for i386 the compilation fails with the error
checking for RTEMS_BSP... pc386
checking for perl... /usr/bin/perl
Hello,
I was wondering if there has been any experience with the CAN bus on RTEMS
before?
It turns out that searching for "can" results in quite poor results. So far I
had little luck to find out if there are drivers for CAN bus controllers
available in freebsd and which devices are supported.
> -Original Message-
> From: yaron o [mailto:jaron0...@gmail.com]
> Sent: Monday, October 23, 2017 4:17 PM
> To: Sommer, Jan
> Cc: users@rtems.org
> Subject: Re: interrupt example leon3
>
> Ok thank you ,
>
> i succeeded to implement the interrupt on leon 3 ,thats what i added if some
>
Hi Yaron,
> -Original Message-
> From: users [mailto:users-boun...@rtems.org] On Behalf Of yaron o
> Sent: Monday, October 23, 2017 10:21 AM
> To: users@rtems.org
> Subject: interrupt example leon3
>
> Hello all
>
> I want to add a new interrupt in my program , i check the rtems sample f
Hello Sebastian,
> -Original Message-
> From: Sebastian Huber [mailto:sebastian.hu...@embedded-brains.de]
> Sent: Thursday, October 19, 2017 7:05 AM
> To: Sommer, Jan; users@rtems.org
> Subject: Re: MIssing pci/cfg.h during PCI configuration
>
> the libpci is currently only available on
Hello,
I try to create a simple rtems4.12 setup using the pc486 bsp with the
PCI-library enabled.
Following the user guide I added
#define RTEMS_PCI_CONFIG_LIB
#define CONFIGURE_INIT
#define CONFIGURE_PCI_LIBPCI_LIB_AUTO
to my configuration.
If I try to compile the project I get the
> -Original Message-
> From: mfg [mailto:m...@ugr.es]
> Sent: Wednesday, September 06, 2017 8:42 AM
> To: Sommer, Jan
> Cc: users@rtems.org
> Subject: RE: How to change UARTs RTEMS
>
> Thanks for the reply Jan.
>
> In your path you have xilinx_scosa, is it some xilinx's board?
>
Yes it
I think I encountered this problem as well.
I found this patch in my history. Maybe it helps:
diff --git a/c/src/lib/libbsp/arm/xilinx_scosa/console/console-config.c
b/c/src/lib/libbsp/arm/xilinx_scosa/console/console-config.c
index 94e5e4f799..6db8d0da88 100644
--- a/c/src/lib/libbsp/arm/xilinx_
77 matches
Mail list logo
