Hi Stephen,
On 16 February 2015 at 21:19, Stephen Warren swarren@wwwdotorg.org wrote:
On 02/16/2015 09:15 PM, Simon Glass wrote:
Hi Stephen,
On 16 February 2015 at 21:09, Stephen Warren swarren@wwwdotorg.org wrote:
On 02/16/2015 06:03 PM, Tom Rini wrote:
On Mon, Feb 16, 2015 at 12:16:15PM -0700, Stephen Warren wrote:
USB doesn't seem to work yet; the controller detects the on-board Hub/ Ethernet device but can't read the descriptors from it. I haven't investigated yet.
Signed-off-by: Stephen Warren swarren@wwwdotorg.org --- v3: Rebased on top of u-boot-dm merge. v2: Implement new board_rev decoding scheme, to avoid hard-coding the board revision onthe RPi 2.
+(rpi_2) make[3]: *** No rule to make target `arch/arm/cpu/armv7/bcm2835/../../arm1176/bcm2835//init.o', needed by `arch/arm/cpu/armv7/bcm2835/built-in.o'. Stop. +(rpi_2) make[2]: *** [arch/arm/cpu/armv7/bcm2835] Error 2 +(rpi_2) make[1]: *** [arch/arm/cpu/armv7] Error 2
When I try and build it with buildman. Something get left out somewhere? Thanks!
It works fine for me using make:
export CROSS_COMPILE=arm-linux-gnueabi- make ARCH=arm rpi_2_defconfig && make ARCH=arm -j8 -s
git status doesn't think I forgot to check anything in. The build works after git clean -f -d -x.
I can't remember how to run buildman, and the help text doesn't really clue me in. I guess I'll go wade through the README.
Well worth it :-)
Something like this might work for you:
buildman --fetch-arch arm buildman rpi_2
or if you want to build the whole branch:
buildman -b <local_branch> rpi_2
What do I put into ~/.buildman's toolchain section (and why can't it just automatically pick it up from the CROSS_COMPILE environment variable)? I usually set CROSS_COMPILE to arm-linux-gnueabi- to point at Ubuntu's system packaged compiler. However, none of the following works, since buildman seems to require a compiler that's placed into its own directory rather than /usr/bin:
[toolchain] xxx1: /usr/bin/arm-linux-gnueabi-gcc xxx2: arm-linux-gnueabi-gcc xxx3: /usr/bin/arm-linux-gnueabi- xxx4: arm-linux-gnueabi- xxx5: /usr/bin/arm-linux-gnueabi xxx6: arm-linux-gnueabi
[swarren@dart u-boot.git]$ ./tools/buildman/buildman --list-tool-chains Scanning for tool chains
- scanning path '/usr/bin/arm-linux-gnueabi-gcc'
- looking in '/usr/bin/arm-linux-gnueabi-gcc/.'
- looking in '/usr/bin/arm-linux-gnueabi-gcc/bin'
- looking in '/usr/bin/arm-linux-gnueabi-gcc/usr/bin'
- scanning path 'arm-linux-gnueabi-gcc'
- looking in 'arm-linux-gnueabi-gcc/.'
- looking in 'arm-linux-gnueabi-gcc/bin'
- looking in 'arm-linux-gnueabi-gcc/usr/bin'
- scanning path '/usr/bin/arm-linux-gnueabi-'
- looking in '/usr/bin/arm-linux-gnueabi-/.'
- looking in '/usr/bin/arm-linux-gnueabi-/bin'
- looking in '/usr/bin/arm-linux-gnueabi-/usr/bin'
- scanning path 'arm-linux-gnueabi-'
- looking in 'arm-linux-gnueabi-/.'
- looking in 'arm-linux-gnueabi-/bin'
- looking in 'arm-linux-gnueabi-/usr/bin'
- scanning path '/usr/bin/arm-linux-gnueabi'
- looking in '/usr/bin/arm-linux-gnueabi/.'
- looking in '/usr/bin/arm-linux-gnueabi/bin'
- looking in '/usr/bin/arm-linux-gnueabi/usr/bin'
- scanning path 'arm-linux-gnueabi'
- looking in 'arm-linux-gnueabi/.'
- looking in 'arm-linux-gnueabi/bin'
- looking in 'arm-linux-gnueabi/usr/bin'
List of available toolchains (0): None
I'm not going to download a whole new toolchain just to use a different build tool. I thought I had this working on my work machine before, but I have no idea how I had that configured.
That's up to you, just trying to help.
You probably want:
xxx1: /
$ ./tools/buildman/buildman -H ... This selects the available toolchain paths. Add the base directory for each of your toolchains here. Buildman will search inside these directories and also in any '/usr' and '/usr/bin' subdirectories. ...
Regards, Simon