RTEMS-BSP testing
Hello New Guy Here, I was going through the Gsoc getting started page and I got a bit stuck on the Test a Board Support Package section.I went through the steps provided prior to this. However, when I ran the command cd $HOME/quick-start/build/b-erc32 rtems-test --rtems-bsp=erc32-sis --rtems-tools=$HOME/quick-start/rtems/5 . I received the message RTEMS Testing - Tester, 5.0.not_released Command Line: /home/kingkong/Coding-Projects/rtems/5/bin/rtems-test --rtems-bsp=sis-run --rtems-tools=/home/kingkong/Coding-Projects/rtems/5 Host: Linux kingkong-ThinkPad-X390-Yoga 5.3.0-28-generic #30~18.04.1-Ubuntu SMP Fri Jan 17 06:14:09 UTC 2020 x86_64 Python: 3.6.9 (default, Nov 7 2019, 10:44:02) [GCC 8.3.0] Host: Linux-5.3.0-28-generic-x86_64-with-Ubuntu-18.04-bionic (Linux kingkong-ThinkPad-X390-Yoga 5.3.0-28-generic #30~18.04.1-Ubuntu SMP Fri Jan 17 06:14:09 UTC 2020 x86_64 x86_64) error: no executables supplied I looked online and the only similar error I ran across was someone who didn't run the make correctly , so I double checked running both make && make install and I still received the same error. I'm positive it has something to do with my development setup. If anyone could point me in the right direction regarding this it would be greatly appreciated. Thank you, ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: RTEMS-BSP testing
Hello again, DIfferent problem though it's more minor. I was running the test files and at the end of them I always got this message *** FATAL *** fatal source: 5 (RTEMS_FATAL_SOURCE_EXIT) fatal code: 0 (0x) RTEMS version: 5.0.0.486829b2766119275f74e7a2a11d7bf3a9561f54 RTEMS tools: 7.5.0 20191114 (RTEMS 5, RSB 5 (22135c9a7612), Newlib d14714c69) executing thread ID: 0x08a010001 executing thread name: UI1 cpu 0 in error mode (tt = 0x101) 113807 0200a080: 91d02000 ta 0x0 . Is this message normal, because I didn't see it in the other runs of this program. I still get the expected output otherwise , just with this appended. For context the command run was , sparc-rtems5-sis ticker.exe run Thank you, On Sun, Feb 23, 2020 at 4:47 AM John kongtcheu wrote: > Hello New Guy Here, > I was going through the Gsoc getting started page and I got a bit stuck on > the Test a Board Support Package section.I went through the steps provided > prior to this. However, when I ran the command > > cd $HOME/quick-start/build/b-erc32 > rtems-test --rtems-bsp=erc32-sis --rtems-tools=$HOME/quick-start/rtems/5 . > > I received the message > RTEMS Testing - Tester, 5.0.not_released > Command Line: /home/kingkong/Coding-Projects/rtems/5/bin/rtems-test > --rtems-bsp=sis-run --rtems-tools=/home/kingkong/Coding-Projects/rtems/5 > Host: Linux kingkong-ThinkPad-X390-Yoga 5.3.0-28-generic #30~18.04.1-Ubuntu > SMP Fri Jan 17 06:14:09 UTC 2020 x86_64 > Python: 3.6.9 (default, Nov 7 2019, 10:44:02) [GCC 8.3.0] > Host: Linux-5.3.0-28-generic-x86_64-with-Ubuntu-18.04-bionic (Linux > kingkong-ThinkPad-X390-Yoga 5.3.0-28-generic #30~18.04.1-Ubuntu SMP Fri Jan > 17 06:14:09 UTC 2020 x86_64 x86_64) > error: no executables supplied > > I looked online and the only similar error I ran across was someone who > didn't run the make correctly , so I double checked running both make && make > install and I still received the same error. > > I'm positive it has something to do with my development setup. If anyone > could point me in the right direction regarding this it would be greatly > appreciated. > > Thank you, > > ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: RTEMS-BSP testing
Hey, I also witnessed this, My host was Ubuntu as well, I was trying out Hello world task using sis. Considering myself naive and new to this, I am trying to look into this as well. Thank You On Sun, Feb 23, 2020 at 9:23 PM John kongtcheu wrote: > Hello again, > DIfferent problem though it's more minor. I was running the test files and > at the end of them I always got this message > *** FATAL *** > fatal source: 5 (RTEMS_FATAL_SOURCE_EXIT) > fatal code: 0 (0x) > RTEMS version: 5.0.0.486829b2766119275f74e7a2a11d7bf3a9561f54 > RTEMS tools: 7.5.0 20191114 (RTEMS 5, RSB 5 (22135c9a7612), Newlib > d14714c69) > executing thread ID: 0x08a010001 > executing thread name: UI1 > cpu 0 in error mode (tt = 0x101) >113807 0200a080: 91d02000 ta 0x0 > . Is this message normal, because I didn't see it in the other runs of > this program. I still get the expected output otherwise , just with this > appended. > For context the command run was , > sparc-rtems5-sis ticker.exe > run > Thank you, > > On Sun, Feb 23, 2020 at 4:47 AM John kongtcheu > wrote: > >> Hello New Guy Here, >> I was going through the Gsoc getting started page and I got a bit stuck >> on the Test a Board Support Package section.I went through the steps >> provided prior to this. However, when I ran the command >> >> cd $HOME/quick-start/build/b-erc32 >> rtems-test --rtems-bsp=erc32-sis --rtems-tools=$HOME/quick-start/rtems/5 . >> >> I received the message >> RTEMS Testing - Tester, 5.0.not_released >> Command Line: /home/kingkong/Coding-Projects/rtems/5/bin/rtems-test >> --rtems-bsp=sis-run --rtems-tools=/home/kingkong/Coding-Projects/rtems/5 >> Host: Linux kingkong-ThinkPad-X390-Yoga 5.3.0-28-generic #30~18.04.1-Ubuntu >> SMP Fri Jan 17 06:14:09 UTC 2020 x86_64 >> Python: 3.6.9 (default, Nov 7 2019, 10:44:02) [GCC 8.3.0] >> Host: Linux-5.3.0-28-generic-x86_64-with-Ubuntu-18.04-bionic (Linux >> kingkong-ThinkPad-X390-Yoga 5.3.0-28-generic #30~18.04.1-Ubuntu SMP Fri Jan >> 17 06:14:09 UTC 2020 x86_64 x86_64) >> error: no executables supplied >> >> I looked online and the only similar error I ran across was someone who >> didn't run the make correctly , so I double checked running both make && >> make install and I still received the same error. >> >> I'm positive it has something to do with my development setup. If anyone >> could point me in the right direction regarding this it would be greatly >> appreciated. >> >> Thank you, >> >> ___ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Device Tree Blob for Beaglebone Black?
I have been trying to bring up RTEMS with rtems-libbsd on the beaglebone black (latest master). I can run the regular RTEMS samples on the board, and a couple of the rtems-libbsd testsuite examples run as well. The samples such as ping01 and usb01 get a fatal exception in the function fdt_ro_probe_ , leading me to believe that maybe I am not using the correct device tree blob. I'm using the instructions here: https://git.rtems.org/rtems-docs/tree/user/bsps/arm/beagle.rst And I have am loading am335x-boneblack.dtb that I copied from a linux u-boot build. The instructions talk about getting the one from the FreeBSD repository, but there are many other files included in that dts source. What dtb is normally used for the Beaglebone black RTEMS libbsd testing? Is the dtb needed for the non-libbsd BSP? Also, is the ethernet supported on the RTEMS beagle BSP, or do I need libbsd to get ethernet? Thanks, Alan ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: Device Tree Blob for Beaglebone Black?
On 23/02/2020 17:07, Alan Cudmore wrote: > I have been trying to bring up RTEMS with rtems-libbsd on the > beaglebone black (latest master). > > I can run the regular RTEMS samples on the board, and a couple of the > rtems-libbsd testsuite examples run as well. > > The samples such as ping01 and usb01 get a fatal exception in the > function fdt_ro_probe_ , leading me to believe that maybe I am not > using the correct device tree blob. > > I'm using the instructions here: > https://git.rtems.org/rtems-docs/tree/user/bsps/arm/beagle.rst > > And I have am loading am335x-boneblack.dtb that I copied from a linux > u-boot build. The instructions talk about getting the one from the > FreeBSD repository, but there are many other files included in that > dts source. > > What dtb is normally used for the Beaglebone black RTEMS libbsd testing? > > Is the dtb needed for the non-libbsd BSP? > > Also, is the ethernet supported on the RTEMS beagle BSP, or do I need > libbsd to get ethernet? > > Thanks, > Alan Hello Alan, I recommend to use the FreeBSD device trees. libbsd is FreeBSD based and therefore works best with them. Normally I would suggest to use the version matching the FreeBSD commit used in libbsd. But unfortunately in the last commit that doesn't seem to work. Vijay had some problems with it and noted that the version from FreeBSD commit 19a6ceb89dbacf74697d493e48c388767126d418 works fine. Regarding Ethernet support: As far as I know there is no support for the legacy stack. But the one in libbsd worked fine the last time I tested it (which was when I ported it). If you really want to use the legacy stack please note that it is still an IPv4 only one and therefore it is quite limited nowadays. Best regards Christian ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: RTEMS-BSP testing
On Sun, Feb 23, 2020, 10:03 AM Anmol Mishra wrote: > Hey, I also witnessed this, My host was Ubuntu as well, I was trying out > Hello world task using sis. Considering myself naive and new to this, I am > trying to look into this as well. > > Thank You > > > On Sun, Feb 23, 2020 at 9:23 PM John kongtcheu > wrote: > >> Hello again, >> DIfferent problem though it's more minor. I was running the test files >> and at the end of them I always got this message >> *** FATAL *** >> fatal source: 5 (RTEMS_FATAL_SOURCE_EXIT) >> fatal code: 0 (0x) >> > As scary as this appears, it is a normal exit(0). The source is exit() and the code is 0. All RTEMS programs exit through the same place _Terminate and the verbose shutdown handler prints all this out. If it had been a fatal error, the source and value would have pointed you to somewhere like a BSP, the score, or the application itself, etc. > RTEMS version: 5.0.0.486829b2766119275f74e7a2a11d7bf3a9561f54 >> RTEMS tools: 7.5.0 20191114 (RTEMS 5, RSB 5 (22135c9a7612), Newlib >> d14714c69) >> executing thread ID: 0x08a010001 >> executing thread name: UI1 >> cpu 0 in error mode (tt = 0x101) >>113807 0200a080: 91d02000 ta 0x0 >> . Is this message normal, because I didn't see it in the other runs of >> this program. I still get the expected output otherwise , just with this >> appended. >> For context the command run was , >> sparc-rtems5-sis ticker.exe >> run >> Thank you, >> >> On Sun, Feb 23, 2020 at 4:47 AM John kongtcheu >> wrote: >> >>> Hello New Guy Here, >>> I was going through the Gsoc getting started page and I got a bit stuck >>> on the Test a Board Support Package section.I went through the steps >>> provided prior to this. However, when I ran the command >>> >>> cd $HOME/quick-start/build/b-erc32 >>> rtems-test --rtems-bsp=erc32-sis --rtems-tools=$HOME/quick-start/rtems/5 . >>> >>> I received the message >>> RTEMS Testing - Tester, 5.0.not_released >>> Command Line: /home/kingkong/Coding-Projects/rtems/5/bin/rtems-test >>> --rtems-bsp=sis-run --rtems-tools=/home/kingkong/Coding-Projects/rtems/5 >>> Host: Linux kingkong-ThinkPad-X390-Yoga 5.3.0-28-generic >>> #30~18.04.1-Ubuntu SMP Fri Jan 17 06:14:09 UTC 2020 x86_64 >>> Python: 3.6.9 (default, Nov 7 2019, 10:44:02) [GCC 8.3.0] >>> Host: Linux-5.3.0-28-generic-x86_64-with-Ubuntu-18.04-bionic (Linux >>> kingkong-ThinkPad-X390-Yoga 5.3.0-28-generic #30~18.04.1-Ubuntu SMP Fri Jan >>> 17 06:14:09 UTC 2020 x86_64 x86_64) >>> error: no executables supplied >>> >>> I looked online and the only similar error I ran across was someone who >>> didn't run the make correctly , so I double checked running both make && >>> make install and I still received the same error. >>> >>> I'm positive it has something to do with my development setup. If anyone >>> could point me in the right direction regarding this it would be greatly >>> appreciated. >>> >>> Thank you, >>> >>> ___ >> devel mailing list >> devel@rtems.org >> http://lists.rtems.org/mailman/listinfo/devel > > ___ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: Device Tree Blob for Beaglebone Black?
Hi Christian, Thanks for the quick response. I followed the instructions in the docs.rtems.org manual and generated the dtb from the FreeBSD commit that Vijay suggested. It still resulted in an exception in the same function. Do you know if a specific commit of rtems-libbsd is required to work with that dtb? I tried master, and then the "5-freebsd-12" branch. Thanks, Alan On Sun, Feb 23, 2020 at 11:32 AM Christian Mauderer wrote: > > On 23/02/2020 17:07, Alan Cudmore wrote: > > I have been trying to bring up RTEMS with rtems-libbsd on the > > beaglebone black (latest master). > > > > I can run the regular RTEMS samples on the board, and a couple of the > > rtems-libbsd testsuite examples run as well. > > > > The samples such as ping01 and usb01 get a fatal exception in the > > function fdt_ro_probe_ , leading me to believe that maybe I am not > > using the correct device tree blob. > > > > I'm using the instructions here: > > https://git.rtems.org/rtems-docs/tree/user/bsps/arm/beagle.rst > > > > And I have am loading am335x-boneblack.dtb that I copied from a linux > > u-boot build. The instructions talk about getting the one from the > > FreeBSD repository, but there are many other files included in that > > dts source. > > > > What dtb is normally used for the Beaglebone black RTEMS libbsd testing? > > > > Is the dtb needed for the non-libbsd BSP? > > > > Also, is the ethernet supported on the RTEMS beagle BSP, or do I need > > libbsd to get ethernet? > > > > Thanks, > > Alan > > Hello Alan, > > I recommend to use the FreeBSD device trees. libbsd is FreeBSD based and > therefore works best with them. Normally I would suggest to use the > version matching the FreeBSD commit used in libbsd. But unfortunately in > the last commit that doesn't seem to work. Vijay had some problems with > it and noted that the version from FreeBSD commit > 19a6ceb89dbacf74697d493e48c388767126d418 works fine. > > Regarding Ethernet support: As far as I know there is no support for the > legacy stack. But the one in libbsd worked fine the last time I tested > it (which was when I ported it). If you really want to use the legacy > stack please note that it is still an IPv4 only one and therefore it is > quite limited nowadays. > > Best regards > > Christian ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
[PATCH] Hello World
---
testsuites/samples/hello/init.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/testsuites/samples/hello/init.c b/testsuites/samples/hello/init.c
index 34ded37c55..13aa377d95 100644
--- a/testsuites/samples/hello/init.c
+++ b/testsuites/samples/hello/init.c
@@ -22,7 +22,7 @@ static rtems_task Init(
{
rtems_print_printer_fprintf_putc(&rtems_test_printer);
TEST_BEGIN();
- printf( "Hello World\n" );
+ printf( "This is John Kongtcheu's Hello World \n Welcome to RTEMS and Google
Summer of Code 2020" );
TEST_END();
rtems_test_exit( 0 );
}
--
2.17.1
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
Re: [PATCH] Hello World
Hi John,
Thank you. If you're planning to apply for GSoC as a student, please
also send me by email your screenshot, CC to j...@rtems.org and
chr...@rtems.org
Begin to look through the Open Projects for what kinds of projects
might interest you, and ask questions here about whether/which
projects might be good for you to work on an application.
Gedare
On Sun, Feb 23, 2020 at 4:20 PM John Kongtcheu wrote:
>
> ---
> testsuites/samples/hello/init.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/testsuites/samples/hello/init.c b/testsuites/samples/hello/init.c
> index 34ded37c55..13aa377d95 100644
> --- a/testsuites/samples/hello/init.c
> +++ b/testsuites/samples/hello/init.c
> @@ -22,7 +22,7 @@ static rtems_task Init(
> {
>rtems_print_printer_fprintf_putc(&rtems_test_printer);
>TEST_BEGIN();
> - printf( "Hello World\n" );
> + printf( "This is John Kongtcheu's Hello World \n Welcome to RTEMS and
> Google Summer of Code 2020" );
>TEST_END();
>rtems_test_exit( 0 );
> }
> --
> 2.17.1
>
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
ARM Hard Float Support
Hi What's the state of the world on ARM hard float support? I was asked by someone about these options: -march=armv7-a -mfloat-abi=hard -mfpu=vfpv3-d16 -march=armv7-a+simd When I test build a simple main(), I end up with a library mismatch which usually means we are missing a proper multilib variant. I tried this with the rtems6 gcc 10 snapshot. I looked at our gcc t-rtems versus the main one for elf/eabi and those seem to have a LOT more variants. Any insight would be appreciated. --joel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
[PATCH v1] Hello world task done
testsuites/samples/hello/init.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/testsuites/samples/hello/init.c
b/testsuites/samples/hello/init.c
index 34ded37c55..882b9d3838 100644
--- a/testsuites/samples/hello/init.c
+++ b/testsuites/samples/hello/init.c
@@ -22,7 +22,7 @@ static rtems_task Init(
{
rtems_print_printer_fprintf_putc(&rtems_test_printer);
TEST_BEGIN();
- printf( "Hello World\n" );
+ printf( "Hello World, My name is Anmol Mishra\nYou can call me Anmol\n"
);
TEST_END();
rtems_test_exit( 0 );
}
--
2.17.1
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
Re: [PATCH v1] Hello world task done
Hi Anmol,
Thanks. You can send me your screenshot proof, with j...@rtems.org and
chr...@rtems.org in CC.
Please review the list of open projects to identify which one(s)
interest you, and discuss on this mailing list to find out if anyone
is willing to mentor it this year, or has any advice on application.
Gedare
On Sun, Feb 23, 2020 at 7:47 PM Anmol Mishra wrote:
> testsuites/samples/hello/init.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/testsuites/samples/hello/init.c b/testsuites/samples/hello/init.c
> index 34ded37c55..882b9d3838 100644
> --- a/testsuites/samples/hello/init.c
> +++ b/testsuites/samples/hello/init.c
> @@ -22,7 +22,7 @@ static rtems_task Init(
> {
>rtems_print_printer_fprintf_putc(&rtems_test_printer);
>TEST_BEGIN();
> - printf( "Hello World\n" );
> + printf( "Hello World, My name is Anmol Mishra\nYou can call me Anmol\n" );
>TEST_END();
>rtems_test_exit( 0 );
> }
> --
> 2.17.1
>
>
>
>
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
Re: Device Tree Blob for Beaglebone Black?
On Sun, Feb 23, 2020 at 11:46 PM Alan Cudmore wrote: > Hi Christian, > Thanks for the quick response. I followed the instructions in the > docs.rtems.org manual and generated the dtb from the FreeBSD commit > that Vijay suggested. It still resulted in an exception in the same > function. > > Do you know if a specific commit of rtems-libbsd is required to work > with that dtb? > I tried master, and then the "5-freebsd-12" branch. > > Thanks, > Alan > > Hi Alan, I checked with the usb01 and ping01 tests running on libbsd master and the dtb from the commit mentioned by Christian. I can't reproduce the error and it seems to run as expected. I'm not sure where the error might be coming from. Below I'm pasting the contents of my uEnv.txt If the error isn't in the uEnv, I can send you my sd card image(offlist) so that you can try that on your board and that might give some hint on what was going wrong. ``` setenv bootdelay 5 uenvcmd=run boot boot=fatload mmc 0 0x8080 rtems-app.img ; fatload mmc 0 0x8800 am335x-boneblack.dtb ; fdt addr 0x8800; bootm 0x8080 - 0x8800 ``` Best regards, Vijay > On Sun, Feb 23, 2020 at 11:32 AM Christian Mauderer > wrote: > > > > On 23/02/2020 17:07, Alan Cudmore wrote: > > > I have been trying to bring up RTEMS with rtems-libbsd on the > > > beaglebone black (latest master). > > > > > > I can run the regular RTEMS samples on the board, and a couple of the > > > rtems-libbsd testsuite examples run as well. > > > > > > The samples such as ping01 and usb01 get a fatal exception in the > > > function fdt_ro_probe_ , leading me to believe that maybe I am not > > > using the correct device tree blob. > > > > > > I'm using the instructions here: > > > https://git.rtems.org/rtems-docs/tree/user/bsps/arm/beagle.rst > > > > > > And I have am loading am335x-boneblack.dtb that I copied from a linux > > > u-boot build. The instructions talk about getting the one from the > > > FreeBSD repository, but there are many other files included in that > > > dts source. > > > > > > What dtb is normally used for the Beaglebone black RTEMS libbsd > testing? > > > > > > Is the dtb needed for the non-libbsd BSP? > > > > > > Also, is the ethernet supported on the RTEMS beagle BSP, or do I need > > > libbsd to get ethernet? > > > > > > Thanks, > > > Alan > > > > Hello Alan, > > > > I recommend to use the FreeBSD device trees. libbsd is FreeBSD based and > > therefore works best with them. Normally I would suggest to use the > > version matching the FreeBSD commit used in libbsd. But unfortunately in > > the last commit that doesn't seem to work. Vijay had some problems with > > it and noted that the version from FreeBSD commit > > 19a6ceb89dbacf74697d493e48c388767126d418 works fine. > > > > Regarding Ethernet support: As far as I know there is no support for the > > legacy stack. But the one in libbsd worked fine the last time I tested > > it (which was when I ported it). If you really want to use the legacy > > stack please note that it is still an IPv4 only one and therefore it is > > quite limited nowadays. > > > > Best regards > > > > Christian > ___ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel > ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: Device Tree Blob for Beaglebone Black?
> On 24 Feb 2020, at 5:32 am, Christian Mauderer wrote: > > On 23/02/2020 17:07, Alan Cudmore wrote: >> I have been trying to bring up RTEMS with rtems-libbsd on the >> beaglebone black (latest master). >> >> I can run the regular RTEMS samples on the board, and a couple of the >> rtems-libbsd testsuite examples run as well. >> >> The samples such as ping01 and usb01 get a fatal exception in the >> function fdt_ro_probe_ , leading me to believe that maybe I am not >> using the correct device tree blob. >> >> I'm using the instructions here: >> https://git.rtems.org/rtems-docs/tree/user/bsps/arm/beagle.rst >> >> And I have am loading am335x-boneblack.dtb that I copied from a linux >> u-boot build. The instructions talk about getting the one from the >> FreeBSD repository, but there are many other files included in that >> dts source. >> >> What dtb is normally used for the Beaglebone black RTEMS libbsd testing? >> >> Is the dtb needed for the non-libbsd BSP? >> >> Also, is the ethernet supported on the RTEMS beagle BSP, or do I need >> libbsd to get ethernet? >> >> Thanks, >> Alan > > Hello Alan, > > I recommend to use the FreeBSD device trees. libbsd is FreeBSD based and > therefore works best with them. Normally I would suggest to use the > version matching the FreeBSD commit used in libbsd. But unfortunately in > the last commit that doesn't seem to work. Vijay had some problems with > it and noted that the version from FreeBSD commit > 19a6ceb89dbacf74697d493e48c388767126d418 works fine. Is this with 5 branch in Libbsd? I am a little confused about the branch to package in a release and also which FDT files we need for which branch. If different I feel a release will makes things more complicated. This flies into the BSP vertical stack building in the RSB. I am working on releasing and I hope this does not block things. Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: ARM Hard Float Support
Hello Joel, On 24/02/2020 02:55, Joel Sherrill wrote: Hi What's the state of the world on ARM hard float support? I was asked by someone about these options: -march=armv7-a -mfloat-abi=hard -mfpu=vfpv3-d16 -march=armv7-a+simd When I test build a simple main(), I end up with a library mismatch which usually means we are missing a proper multilib variant. I tried this with the rtems6 gcc 10 snapshot. I looked at our gcc t-rtems versus the main one for elf/eabi and those seem to have a LOT more variants. Any insight would be appreciated. GCC 8, 9 and 10 are not supported by the ARM BSPs right now. You can try this with GCC 10: -mthumb -march=armv7-a+simd -mfloat-abi=hard Why do they use -mfpu=vfpv3-d16? This seems to be quite a non-standard ARMv7-A chip. -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +49 89 189 47 41-16 Fax : +49 89 189 47 41-09 E-Mail : sebastian.hu...@embedded-brains.de PGP : Public key available on request. Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: Testing BSP package using beaglebone black
Hii, Can you just check if you have the ARM toolchain installed? The guide that you mentioned is for RTEMS 4.11 and maybe things changed with RTEMS 5. If you don't have it installed you can do in a similar way as you did for sparc $ ../source-builder/sb-set-builder --source-only-download 5/rtems-arm $ ../source-builder/sb-set-builder --prefix=$HOME/quick-start/rtems/5 5/rtems-arm After this, you should be able to build your BSP. Thank you, Niteesh ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: rtems-boot-image tool: Raspberry Pi
Hii, This is a follow-up message since this thread has been unnoticed for a while. Thank you, Niteesh On Fri, Feb 21, 2020 at 8:15 PM G. S. Niteesh wrote: > Hi, > > This is regarding adding RPi support to the boot image generation tool. > > The boot process for Raspberry Pi is very unconventional. The GPU starts > first, initializes RAM, other hardware, loads the bootloaders and then > starts > the ARM CPU. > > The minimum files that are required to boot an RPi are > bootcode.bin, startx.elf, fixup.dat, kernel.img, config.txt > There are also other variants of startx.elf and fixup.dat. > Please have a look at > https://www.raspberrypi.org/documentation/configuration/config-txt/boot.md > for information on the variants. > > From what I have tried on my Rpi3 model b v1.2 the minimum files that are > required are start_x.elf, fixup_x.dat, bootcode.bin, kernel.img, config.txt > But for this to work, we must add start_x=1 to config.txt because by > default > start.elf is loaded. > > So, what should be the values for the first and second stages in > rtems-boot.ini for Rpi? > And also wouldn't it be nice if we could add a files field, which will > copy the specified files > to the image? This would save a lot of typing in case of RPi > > Thank you, > Niteesh. > ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: SPDX License Identifier Only and Full Copy?
Hello, I updated the File Template section: https://docs.rtems.org/branches/master/eng/coding-file-hdr.html Please have a look at it and check if it is all right for you. -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +49 89 189 47 41-16 Fax : +49 89 189 47 41-09 E-Mail : sebastian.hu...@embedded-brains.de PGP : Public key available on request. Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
