CRUX-ARM running on a BeagleBone Black
pitillo at ono.com
Tue Nov 10 10:15:15 UTC 2015
> El 09/11/2015 22:03, Bernd Eggink <monoped at sudrala.de> escribió:
> > On 09.11.2015 10:17, Víctor Martínez wrote:
> > > El 09/11/2015 10:01, Bernd Eggink <monoped at sudrala.de> escribió:
> > >>
> > >> On 09.11.2015 08:27, Víctor Martínez wrote:
> > >>> ...
> > >>> Hey Bernd,
> > >>> which release did you deploy into the BBB? Generic or optimized for the cubieboard1?
> > >>
> > >> Victor,
> > >>
> > >> I used the generic release. What kind of optimization has been made for
> > >> the cubieboard? Compiler options? Kernel config?
> > >>
> > > All releases aren't related to kernels, they are just rootfs optimized for devices. In this case, they are optimized for the compiler.
> > >
> > > The generic release hasn't any kind of optimization.
> > Hi Victor,
> > are you sure? The generic release I downloaded has exactly the same
> > compiler flags as the cubieboard release.
I'm sure CFLAGS aren't the same for the generic release (crux-arm-rootfs-3.1.tar.xz) which are CFLAGS="-O2 -pipe -mfloat-abi=hard" vs cubieboard optimIzed release (crux-arm-rootfs-3.1-cubieboard.tar.xz) which has CFLAGS="-O2 -pipe -mfloat-abi=hard -fpu=neon -mcpu=cortex-a8 -mtune=cortex-a8".
> > > You can take a look into development section in the ports/core-arm repository, the overlayed pkgutils port has pkgmk.conf where you'll see only hard float support.
> > > In your case, in ports/cubieboard-arm repository you can verify its cflags and see if they fit to the ones used by the BBB (probably they'll do).
> > >> Presently I'm preparing a kernel update to 4.3. and will appreciate any
> > >> hints concerning the parameters (not knowing anything about ARM, I can
> > >> only guess them).
> > >>
> > > You shouldn't get any problems upgrading your kernel, but if you do, feel free to share them to take a look.
> > Problems, indeed... After compiling the kernel I realized that simply
> > replacing the zImage (like with x86 machines) isn't enough; the beagle
> > doesn't boot. I've never done that for an ARM system before, and
> > apparently am missing something fundamental. Is there a simple receipt,
> > or could you point me to a concise documentation of that process?
All devices has its own process for booting the device. I'd take a look to the BBB boot process to verify if it needs something special (building uImage instead of zImage, changing addresses, adding dtb to the image, ...)
Without more info related to the problem is hard to give a hand. Is it reading the image? Does it boot but it halts in the middle of the process (file system used for the root partition is compiled in the kernel instead of a module, CONFIG_DEVTMPFS enabled inside the kernel)?...
It'd be great to move this thread to CRUX-ARM mailing list to avoid noise here.
> > Regards,
> > Bernd
Victor Martinez | Learning bit by bit
More information about the CRUX