Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 23 Mar 2015 22:04:00 -0700
From:      Russell Haley <russ.haley@gmail.com>
To:        Rui Paulo <rpaulo@me.com>
Cc:        freebsd-arm <freebsd-arm@freebsd.org>
Subject:   Re: Digi-CCWMX53 - u-boot
Message-ID:  <CABx9NuQD=tapnsueRQO-mQq5=sRZ4RLPg7fRyuyk237HH=8vDA@mail.gmail.com>
In-Reply-To: <F33D2637-1D5D-431F-89D4-D9C051582A57@me.com>
References:  <CABx9NuQZe3k%2BAtRxtUg5k3=5jM20RQdgnwpuKr9uc07VY1C1EQ@mail.gmail.com> <622469F8-C245-4E84-B5E1-FE360D3C9B4C@me.com> <CABx9NuRhwfW=AZ%2BLUnQ4f2yzO-cf%2BbNX28BZqP6KCs5xKf-G-g@mail.gmail.com> <F33D2637-1D5D-431F-89D4-D9C051582A57@me.com>

next in thread | previous in thread | raw e-mail | index | archive | help
No, I've never had this work. It's also a fresh-ish jail and a
straight clone from your github repo (note: I just deleted and
re-cloned it with the same results). Could it be a problem using newer
versions of the tools? Have you had this work recently? I was really
hoping to get this working with Crochet, but right now I'd settle for
a binary that has a working USB driver.

I've really become hung up on this step. I used to have a copy of
u-boot that had a working USB driver but I can't find it anymore (and
that was 2 virtual machines ago!)  so I haven't been able to mount
rootfs for some time.

I think this picture is an accurate reflection of my experience with
FreeBSD/Arm development so far (I am currently in the later stage):

https://plus.google.com/u/0/+Danokellz/posts/JjSAAV4DNgp

lolz.

On Mon, Mar 23, 2015 at 8:19 PM, Rui Paulo <rpaulo@me.com> wrote:
> On Mar 21, 2015, at 14:31, Russell Haley <russ.haley@gmail.com> wrote:
>>
>> Thanks for getting back to me Rui,
>>
>> I have done the following bit of flailing around:
>>
>> - updated my userland to 1100065
>> - Installed arm-none-eabi from pkgng as Mr. Lepore has indicated
>> - installed the latest gcc (gcc48?)
>> - I have since built the xdev target as well.
>> - Installed mpc
>> - setenv LD_LIBRARY_PATH "/usr/local/lib"
>> - ldconfig
>>
>>
>> So after much faffing about I've tried a whole bunch of combinations:
>> gmake HOSTCC=gcc48 CROSS_COMPILE=arm-none-eabi-
>> gmake HOSTCC=gcc48 CROSS_COMPILE=armv6-freebsd-
>> gmake SED=gsed HOSTCC=cc CROSS_COMPILE=armv6-freebsd-
>> gmake SED=gsed HOSTCC=gcc48 CROSS_COMPILE=arm-none-eabi-
>>
>>
>> All with the same result:
>>
>> for dir in tools examples/standalone examples/api ; do gmake -C $dir
>> _depend ; done
>> gmake[1]: Entering directory '/usr/uboot/tools'
>> gmake[1]: Nothing to be done for '_depend'.
>> gmake[1]: Leaving directory '/usr/uboot/tools'
>> gmake[1]: Entering directory '/usr/uboot/examples/standalone'
>> gmake[1]: Nothing to be done for '_depend'.
>> gmake[1]: Leaving directory '/usr/uboot/examples/standalone'
>> gmake[1]: Entering directory '/usr/uboot/examples/api'
>> gmake[1]: Nothing to be done for '_depend'.
>> gmake[1]: Leaving directory '/usr/uboot/examples/api'
>> gmake -C tools all
>> gmake[1]: Entering directory '/usr/uboot/tools'
>> gcc48 -g -Wall -idirafter /usr/uboot/include -idirafter
>> /usr/uboot/include2 -idirafter /usr/uboot/include -I /usr/uboot/libfdt
>> -I /usr/uboot/tools -DTEXT_BASE=0x77800000 -DUSE_HOSTCC
>> -D__KERNEL_STRICT_NAMES -O -c -o fdt.o
>> gcc48: fatal error: no input files
>> compilation terminated.
>> Makefile:231: recipe for target 'fdt.o' failed
>> gmake[1]: *** [fdt.o] Error 1
>> gmake[1]: Leaving directory '/usr/uboot/tools'
>> Makefile:402: recipe for target 'tools' failed
>> gmake: *** [tools] Error 2
>
> It looks like Makefile rules are broken in your system.  Did this ever work for you?
>
> --
> Rui Paulo
>
>
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CABx9NuQD=tapnsueRQO-mQq5=sRZ4RLPg7fRyuyk237HH=8vDA>