Re: MVME2500 (qoriq_e500) no longer boots with RTEMS6

2021-02-20 Thread Chris Johns 
On 20/2/21 6:17 pm, Heinz Junkes wrote:
> I was totally happy with the Makefile provided by Christian.
> It saved me a lot of typing and made it possible for me to play 
> through different variants in a really structured and consistent way 
> without "forgetting something every now and then".
> Such help is very important for people like me who are not 
> permanently in the RTEMS cloud ;-)
> Thanks to all for the useful hints and support.

This is great to hear and as Christian said it his sandbox to aid him.

If you are interested in having this BSP integrated into the eco-system the
approach Andrew Johnson posted for the m68k/uC5282 is worth a look 

https://lists.rtems.org/pipermail/users/2021-February/068148.html

A bset file like that is all we need to add it to the RSB.

Chris

___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: MVME2500 (qoriq_e500) no longer boots with RTEMS6

2021-02-19 Thread Heinz Junkes 
I was totally happy with the Makefile provided by Christian.
It saved me a lot of typing and made it possible for me to play 
through different variants in a really structured and consistent way 
without "forgetting something every now and then".
Such help is very important for people like me who are not 
permanently in the RTEMS cloud ;-)
Thanks to all for the useful hints and support.
Heinz

> On 19. Feb 2021, at 22:11, Joel Sherrill  wrote:
> 
> 
> 
> On Fri, Feb 19, 2021 at 3:07 PM Christian Mauderer  wrote:
> On 19/02/2021 19:52, junkes wrote:
> > On 2021-02-19 18:40, Gedare Bloom wrote:
> >> Advise how you built. We are starting to see some bitrot breakage in
> >> configuration. The cutover to waf will come soon, and I don't expect
> >> rtems6 release to support autoconf build of rtems itself. I suggest
> >> you change over to waf build of rtems kernel if you haven't yet.
> > 
> > I use a build system from Christian Maurer:
> > https://gitlab.com/c-mauderer/rtems-simulation-environment
> 
> It's not really a build system but only a Makefile that collects the 
> commands so that I can run some quick tests. Please also note that this 
> is no official repo. So don't be surprised if it changes or breaks.
> 
> This is exactly why I haven't been prone to share my rtems-cron-helpers
> which includes a build_bsp script which makes waf and autoconf look the
> same from the command line. It also can run the tester. Saves me a lot of
> keyboarding  :)
> 
> --joel 
> 
> > 
> > define build_toolchain
> >  rm -rf $(RSB)/rtems/build
> >  cd $(RSB)/rtems && ../source-builder/sb-set-builder \
> >  --prefix=$(PREFIX) \
> >  --log=$(RSB)/b-rsb-toolchain-$(1).log \
> >  $(RTEMS_VERSION)/rtems-$(1)
> >  rm -rf $(RSB)/rtems/build
> > 
> > define build_bsp
> >  cd $(SRC_RTEMS) && ./waf clean || true
> >  cd $(SRC_RTEMS) && ./waf bsp_defaults --rtems-bsps=$(1)/$(2) > 
> > config.ini
> >  cd $(SRC_RTEMS) && sed -i \
> >  -e "s|RTEMS_POSIX_API = False|RTEMS_POSIX_API = True|" \
> >  -e "s|CLOCK_DRIVER_USE_FAST_IDLE = 
> > True|CLOCK_DRIVER_USE_FAST_IDLE = False|" \
> >  -e "s|BUILD_TESTS = False|BUILD_TESTS = True|" \
> >  config.ini
> >  cd $(SRC_RTEMS) && ./waf configure --prefix=$(PREFIX)
> >  cd $(SRC_RTEMS) && ./waf
> >  cd $(SRC_RTEMS) && ./waf install
> > endef
> > 
> > define build_libbsd
> >  rm -rf $(SRC_LIBBSD)/build
> >  cd $(SRC_LIBBSD) && ./waf configure \
> >  --prefix=$(PREFIX) \
> >  --rtems-bsps=$(1)/$(2) \
> >  --enable-warnings \
> >  --optimization=2 \
> >  --rtems-version=$(RTEMS_VERSION)
> >  cd $(SRC_LIBBSD) && ./waf
> >  cd $(SRC_LIBBSD) && ./waf install
> > endef
> > 
> > 
> > I would like to switch to waf. But this is not available for the
> > kernel with RTEMS5 and unfortunately it does not work with RTEMS6.
> > Heinz > ___
> > users mailing list
> > users@rtems.org
> > http://lists.rtems.org/mailman/listinfo/users
> > 
> ___
> users mailing list
> users@rtems.org
> http://lists.rtems.org/mailman/listinfo/users



smime.p7s
Description: S/MIME cryptographic signature
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: MVME2500 (qoriq_e500) no longer boots with RTEMS6

2021-02-19 Thread Christian Mauderer 



On 19/02/2021 22:11, Joel Sherrill wrote:



On Fri, Feb 19, 2021 at 3:07 PM Christian Mauderer > wrote:


On 19/02/2021 19:52, junkes wrote:
 > On 2021-02-19 18:40, Gedare Bloom wrote:
 >> Advise how you built. We are starting to see some bitrot breakage in
 >> configuration. The cutover to waf will come soon, and I don't expect
 >> rtems6 release to support autoconf build of rtems itself. I suggest
 >> you change over to waf build of rtems kernel if you haven't yet.
 >
 > I use a build system from Christian Maurer:
 > https://gitlab.com/c-mauderer/rtems-simulation-environment


It's not really a build system but only a Makefile that collects the
commands so that I can run some quick tests. Please also note that this
is no official repo. So don't be surprised if it changes or breaks.


This is exactly why I haven't been prone to share my rtems-cron-helpers
which includes a build_bsp script which makes waf and autoconf look the
same from the command line. It also can run the tester. Saves me a lot of
keyboarding  :)

--joel


The repository is based on a Makefile that we used for a customer in an 
open source project:


  https://github.com/grisp/grisp2-rtems-toolchain/

So it's out in the wild anyway ;-)




 >
 > define build_toolchain
 >  rm -rf $(RSB)/rtems/build
 >  cd $(RSB)/rtems && ../source-builder/sb-set-builder \
 >      --prefix=$(PREFIX) \
 >      --log=$(RSB)/b-rsb-toolchain-$(1).log \
 >      $(RTEMS_VERSION)/rtems-$(1)
 >  rm -rf $(RSB)/rtems/build
 >
 > define build_bsp
 >  cd $(SRC_RTEMS) && ./waf clean || true
 >  cd $(SRC_RTEMS) && ./waf bsp_defaults --rtems-bsps=$(1)/$(2) >
 > config.ini
 >  cd $(SRC_RTEMS) && sed -i \
 >      -e "s|RTEMS_POSIX_API = False|RTEMS_POSIX_API = True|" \
 >      -e "s|CLOCK_DRIVER_USE_FAST_IDLE =
 > True|CLOCK_DRIVER_USE_FAST_IDLE = False|" \
 >      -e "s|BUILD_TESTS = False|BUILD_TESTS = True|" \
 >      config.ini
 >  cd $(SRC_RTEMS) && ./waf configure --prefix=$(PREFIX)
 >  cd $(SRC_RTEMS) && ./waf
 >  cd $(SRC_RTEMS) && ./waf install
 > endef
 >
 > define build_libbsd
 >  rm -rf $(SRC_LIBBSD)/build
 >  cd $(SRC_LIBBSD) && ./waf configure \
 >      --prefix=$(PREFIX) \
 >      --rtems-bsps=$(1)/$(2) \
 >      --enable-warnings \
 >      --optimization=2 \
 >      --rtems-version=$(RTEMS_VERSION)
 >  cd $(SRC_LIBBSD) && ./waf
 >  cd $(SRC_LIBBSD) && ./waf install
 > endef
 >
 >
 > I would like to switch to waf. But this is not available for the
 > kernel with RTEMS5 and unfortunately it does not work with RTEMS6.
 > Heinz > ___
 > users mailing list
 > users@rtems.org 
 > http://lists.rtems.org/mailman/listinfo/users

 >
___
users mailing list
users@rtems.org 
http://lists.rtems.org/mailman/listinfo/users



___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: MVME2500 (qoriq_e500) no longer boots with RTEMS6

2021-02-19 Thread Christian Mauderer 

On 19/02/2021 17:30, Heinz Junkes wrote:

When I use the kernel from RTEMS6 my MVME2500 (qoriq_e500)
does not boot anymore and hangs:

VME2500=> run rtems_myTests
reading mvme2500.dtb
12363 bytes read in 13 ms (928.7 KiB/s)
Speed: 1000, full duplex
Using eTSEC1 device
TFTP from server 141.14.128.9; our IP address is 141.14.128.89
Filename 'ticker.img'.
Load address: 0x1000
Loading: #
 6.4 MiB/s
done
Bytes transferred = 60182 (eb16 hex)
WARNING: adjusting available memory to 3000
## Booting kernel from Legacy Image at 1000 ...
   Image Name:   RTEMS
   Created:  2021-02-18  20:18:21 UTC
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:60118 Bytes = 58.7 KiB
   Load Address: 4000
   Entry Point:  4000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 2000
   Booting using the fdt blob at 0x2000
   Uncompressing Kernel Image ... OK
   Loading Device Tree to 03ff9000, end 03fff04a ... OK
…

no more output


Just a wild guess: Can you compare the addresses of the binaries. Maybe 
for some reason a wrong linkcmds is used. arm-rtems6-objdump -h app.exe 
should give you the relevant information.





Heinz


___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users


___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: MVME2500 (qoriq_e500) no longer boots with RTEMS6

2021-02-19 Thread Joel Sherrill 
On Fri, Feb 19, 2021 at 3:07 PM Christian Mauderer 
wrote:

> On 19/02/2021 19:52, junkes wrote:
> > On 2021-02-19 18:40, Gedare Bloom wrote:
> >> Advise how you built. We are starting to see some bitrot breakage in
> >> configuration. The cutover to waf will come soon, and I don't expect
> >> rtems6 release to support autoconf build of rtems itself. I suggest
> >> you change over to waf build of rtems kernel if you haven't yet.
> >
> > I use a build system from Christian Maurer:
> > https://gitlab.com/c-mauderer/rtems-simulation-environment
>
> It's not really a build system but only a Makefile that collects the
> commands so that I can run some quick tests. Please also note that this
> is no official repo. So don't be surprised if it changes or breaks.
>

This is exactly why I haven't been prone to share my rtems-cron-helpers
which includes a build_bsp script which makes waf and autoconf look the
same from the command line. It also can run the tester. Saves me a lot of
keyboarding  :)

--joel

>
> >
> > define build_toolchain
> >  rm -rf $(RSB)/rtems/build
> >  cd $(RSB)/rtems && ../source-builder/sb-set-builder \
> >  --prefix=$(PREFIX) \
> >  --log=$(RSB)/b-rsb-toolchain-$(1).log \
> >  $(RTEMS_VERSION)/rtems-$(1)
> >  rm -rf $(RSB)/rtems/build
> >
> > define build_bsp
> >  cd $(SRC_RTEMS) && ./waf clean || true
> >  cd $(SRC_RTEMS) && ./waf bsp_defaults --rtems-bsps=$(1)/$(2) >
> > config.ini
> >  cd $(SRC_RTEMS) && sed -i \
> >  -e "s|RTEMS_POSIX_API = False|RTEMS_POSIX_API = True|" \
> >  -e "s|CLOCK_DRIVER_USE_FAST_IDLE =
> > True|CLOCK_DRIVER_USE_FAST_IDLE = False|" \
> >  -e "s|BUILD_TESTS = False|BUILD_TESTS = True|" \
> >  config.ini
> >  cd $(SRC_RTEMS) && ./waf configure --prefix=$(PREFIX)
> >  cd $(SRC_RTEMS) && ./waf
> >  cd $(SRC_RTEMS) && ./waf install
> > endef
> >
> > define build_libbsd
> >  rm -rf $(SRC_LIBBSD)/build
> >  cd $(SRC_LIBBSD) && ./waf configure \
> >  --prefix=$(PREFIX) \
> >  --rtems-bsps=$(1)/$(2) \
> >  --enable-warnings \
> >  --optimization=2 \
> >  --rtems-version=$(RTEMS_VERSION)
> >  cd $(SRC_LIBBSD) && ./waf
> >  cd $(SRC_LIBBSD) && ./waf install
> > endef
> >
> >
> > I would like to switch to waf. But this is not available for the
> > kernel with RTEMS5 and unfortunately it does not work with RTEMS6.
> > Heinz > ___
> > users mailing list
> > users@rtems.org
> > http://lists.rtems.org/mailman/listinfo/users
> >
> ___
> users mailing list
> users@rtems.org
> http://lists.rtems.org/mailman/listinfo/users
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: MVME2500 (qoriq_e500) no longer boots with RTEMS6

2021-02-19 Thread Christian Mauderer 

On 19/02/2021 19:52, junkes wrote:

On 2021-02-19 18:40, Gedare Bloom wrote:

Advise how you built. We are starting to see some bitrot breakage in
configuration. The cutover to waf will come soon, and I don't expect
rtems6 release to support autoconf build of rtems itself. I suggest
you change over to waf build of rtems kernel if you haven't yet.


I use a build system from Christian Maurer:
https://gitlab.com/c-mauderer/rtems-simulation-environment


It's not really a build system but only a Makefile that collects the 
commands so that I can run some quick tests. Please also note that this 
is no official repo. So don't be surprised if it changes or breaks.




define build_toolchain
 rm -rf $(RSB)/rtems/build
 cd $(RSB)/rtems && ../source-builder/sb-set-builder \
     --prefix=$(PREFIX) \
     --log=$(RSB)/b-rsb-toolchain-$(1).log \
     $(RTEMS_VERSION)/rtems-$(1)
 rm -rf $(RSB)/rtems/build

define build_bsp
 cd $(SRC_RTEMS) && ./waf clean || true
 cd $(SRC_RTEMS) && ./waf bsp_defaults --rtems-bsps=$(1)/$(2) > 
config.ini

 cd $(SRC_RTEMS) && sed -i \
     -e "s|RTEMS_POSIX_API = False|RTEMS_POSIX_API = True|" \
     -e "s|CLOCK_DRIVER_USE_FAST_IDLE = 
True|CLOCK_DRIVER_USE_FAST_IDLE = False|" \

     -e "s|BUILD_TESTS = False|BUILD_TESTS = True|" \
     config.ini
 cd $(SRC_RTEMS) && ./waf configure --prefix=$(PREFIX)
 cd $(SRC_RTEMS) && ./waf
 cd $(SRC_RTEMS) && ./waf install
endef

define build_libbsd
 rm -rf $(SRC_LIBBSD)/build
 cd $(SRC_LIBBSD) && ./waf configure \
     --prefix=$(PREFIX) \
     --rtems-bsps=$(1)/$(2) \
     --enable-warnings \
     --optimization=2 \
     --rtems-version=$(RTEMS_VERSION)
 cd $(SRC_LIBBSD) && ./waf
 cd $(SRC_LIBBSD) && ./waf install
endef


I would like to switch to waf. But this is not available for the
kernel with RTEMS5 and unfortunately it does not work with RTEMS6.
Heinz > ___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users


___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: MVME2500 (qoriq_e500) no longer boots with RTEMS6

2021-02-19 Thread junkes 

On 2021-02-19 18:40, Gedare Bloom wrote:

Advise how you built. We are starting to see some bitrot breakage in
configuration. The cutover to waf will come soon, and I don't expect
rtems6 release to support autoconf build of rtems itself. I suggest
you change over to waf build of rtems kernel if you haven't yet.


I use a build system from Christian Maurer:
https://gitlab.com/c-mauderer/rtems-simulation-environment

define build_toolchain
rm -rf $(RSB)/rtems/build
cd $(RSB)/rtems && ../source-builder/sb-set-builder \
--prefix=$(PREFIX) \
--log=$(RSB)/b-rsb-toolchain-$(1).log \
$(RTEMS_VERSION)/rtems-$(1)
rm -rf $(RSB)/rtems/build

define build_bsp
cd $(SRC_RTEMS) && ./waf clean || true
	cd $(SRC_RTEMS) && ./waf bsp_defaults --rtems-bsps=$(1)/$(2) > 
config.ini

cd $(SRC_RTEMS) && sed -i \
-e "s|RTEMS_POSIX_API = False|RTEMS_POSIX_API = True|" \
		-e "s|CLOCK_DRIVER_USE_FAST_IDLE = True|CLOCK_DRIVER_USE_FAST_IDLE = 
False|" \

-e "s|BUILD_TESTS = False|BUILD_TESTS = True|" \
config.ini
cd $(SRC_RTEMS) && ./waf configure --prefix=$(PREFIX)
cd $(SRC_RTEMS) && ./waf
cd $(SRC_RTEMS) && ./waf install
endef

define build_libbsd
rm -rf $(SRC_LIBBSD)/build
cd $(SRC_LIBBSD) && ./waf configure \
--prefix=$(PREFIX) \
--rtems-bsps=$(1)/$(2) \
--enable-warnings \
--optimization=2 \
--rtems-version=$(RTEMS_VERSION)
cd $(SRC_LIBBSD) && ./waf
cd $(SRC_LIBBSD) && ./waf install
endef


I would like to switch to waf. But this is not available for the
kernel with RTEMS5 and unfortunately it does not work with RTEMS6.
Heinz
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: MVME2500 (qoriq_e500) no longer boots with RTEMS6

2021-02-19 Thread Gedare Bloom 
Advise how you built. We are starting to see some bitrot breakage in
configuration. The cutover to waf will come soon, and I don't expect
rtems6 release to support autoconf build of rtems itself. I suggest
you change over to waf build of rtems kernel if you haven't yet.

On Fri, Feb 19, 2021 at 9:30 AM Heinz Junkes  wrote:
>
> When I use the kernel from RTEMS6 my MVME2500 (qoriq_e500)
> does not boot anymore and hangs:
>
> VME2500=> run rtems_myTests
> reading mvme2500.dtb
> 12363 bytes read in 13 ms (928.7 KiB/s)
> Speed: 1000, full duplex
> Using eTSEC1 device
> TFTP from server 141.14.128.9; our IP address is 141.14.128.89
> Filename 'ticker.img'.
> Load address: 0x1000
> Loading: #
> 6.4 MiB/s
> done
> Bytes transferred = 60182 (eb16 hex)
> WARNING: adjusting available memory to 3000
> ## Booting kernel from Legacy Image at 1000 ...
>   Image Name:   RTEMS
>   Created:  2021-02-18  20:18:21 UTC
>   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
>   Data Size:60118 Bytes = 58.7 KiB
>   Load Address: 4000
>   Entry Point:  4000
>   Verifying Checksum ... OK
> ## Flattened Device Tree blob at 2000
>   Booting using the fdt blob at 0x2000
>   Uncompressing Kernel Image ... OK
>   Loading Device Tree to 03ff9000, end 03fff04a ... OK
> …
>
> no more output
>
> Heinz
>
> ___
> users mailing list
> users@rtems.org
> http://lists.rtems.org/mailman/listinfo/users
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

MVME2500 (qoriq_e500) no longer boots with RTEMS6

2021-02-19 Thread Heinz Junkes 
When I use the kernel from RTEMS6 my MVME2500 (qoriq_e500) 
does not boot anymore and hangs:

VME2500=> run rtems_myTests
reading mvme2500.dtb
12363 bytes read in 13 ms (928.7 KiB/s)
Speed: 1000, full duplex
Using eTSEC1 device
TFTP from server 141.14.128.9; our IP address is 141.14.128.89
Filename 'ticker.img'.
Load address: 0x1000
Loading: #
6.4 MiB/s
done
Bytes transferred = 60182 (eb16 hex)
WARNING: adjusting available memory to 3000
## Booting kernel from Legacy Image at 1000 ...
  Image Name:   RTEMS
  Created:  2021-02-18  20:18:21 UTC
  Image Type:   PowerPC Linux Kernel Image (gzip compressed)
  Data Size:60118 Bytes = 58.7 KiB
  Load Address: 4000
  Entry Point:  4000
  Verifying Checksum ... OK
## Flattened Device Tree blob at 2000
  Booting using the fdt blob at 0x2000
  Uncompressing Kernel Image ... OK
  Loading Device Tree to 03ff9000, end 03fff04a ... OK
…

no more output

Heinz



smime.p7s
Description: S/MIME cryptographic signature
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users