[U-Boot-Users] U-Boot on ARMEB
I'm looking at using Das U-Boot on a big-endian IXP based system. However, v1.1.4 seems to only come with configuration for the "arm" arch (not the "armeb" arch). Does anybody know what is involved in getting u-boot to work with "armeb"?
Thanks!
Brian ( bcwhite@precidia.com )
------------------------------------------------------------------------------- Only those who dare to fail greatly can ever achieve greatly.
On Jan 18, 2006, at 2:30 PM, Brian White wrote:
I'm looking at using Das U-Boot on a big-endian IXP based system. However, v1.1.4 seems to only come with configuration for the "arm" arch (not the "armeb" arch). Does anybody know what is involved in getting u-boot to work with "armeb"?
It's just a matter of selecting the proper cross tool. The ixdp425 is big endian, so just use that as an example. I recently did a port for an ixp425 big endian wireless router. When we are sure the code actually passes the testing, I'll create a patch, but there is nothing specific to big endian in any of the update.
Thanks.
-- Dan
I'm looking at using Das U-Boot on a big-endian IXP based system. However, v1.1.4 seems to only come with configuration for the "arm" arch (not the "armeb" arch). Does anybody know what is involved in getting u-boot to work with "armeb"?
It's just a matter of selecting the proper cross tool. The ixdp425 is big endian, so just use that as an example. I recently did a port for an ixp425 big endian wireless router. When we are sure the code actually passes the testing, I'll create a patch, but there is nothing specific to big endian in any of the update.
That's what I'm figuring out, but it tried to create a link from "asm-arm" and I wasn't sure if there were endian dependencies there. Can I just link it to "asm-armeb" and have it work?
I think I'm just going to link all my tools so they're available as both "armeb-linux" and "arm-linux". My worry is that something will be specifically little-endian somewhere and will be quietly compiled incorrectly.
Brian ( bcwhite@pobox.com )
------------------------------------------------------------------------------- Only those who dare to fail greatly can ever achieve greatly.
On Jan 18, 2006, at 4:04 PM, Brian White wrote:
That's what I'm figuring out, but it tried to create a link from "asm-arm" and I wasn't sure if there were endian dependencies there. Can I just link it to "asm-armeb" and have it work?
All I did was build some cross tools, called them armeb-gcc, etc. Then: setenv ARCH arm setenv CROSS_COMPILE armeb- make ixdp425_config make
and ended up with a big endian U-Boot. I started hacking from there and haven't seen any problems. If there are any, we have not found them yet.
I think I'm just going to link all my tools so they're available as both "armeb-linux" and "arm-linux". My worry is that something will be specifically little-endian somewhere and will be quietly compiled incorrectly.
I think you worry too much, and naming the same tool by those two different names would seem to be more of a problem than doing it properly. If the tools are built correctly for big endian ARM, it seems everything works fine.
I have no further comments on the subject. Good Luck. :-)
-- Dan
That's what I'm figuring out, but it tried to create a link from "asm-arm" and I wasn't sure if there were endian dependencies there. Can I just link it to "asm-armeb" and have it work?
All I did was build some cross tools, called them armeb-gcc, etc. Then: setenv ARCH arm setenv CROSS_COMPILE armeb- make ixdp425_config make
Perfect! That's exactly what I was looking for. Thanks!
Brian ( bcwhite@pobox.com )
------------------------------------------------------------------------------- Only those who dare to fail greatly can ever achieve greatly.
Hi Dan,
On Wednesday 18 January 2006 20:43, Dan Malek wrote:
endian, so just use that as an example. I recently did a port for an ixp425 big endian wireless router. When we are sure the code actually passes the testing, I'll create a patch, but there is nothing specific to big endian in any of the update.
Did you by any chance enable the interrupts on IXP4xx, so that we could use the "standard" U-Boot timer interface "get_timer()", and not this "reset_timer_masked()" and "get_timer_masked()" stuff?
Best regards, Stefan
participants (3)
-
Brian White -
Dan Malek -
Stefan Roese