I'm trying to implement yocto project in imx51.I followed the attached document as given below,
$ mkdir ~/bin
$ curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
$ chmod a+x ~/bin/repo
$ mkdir fsl-community-bsp
$ cd fsl-community-bsp
fsl-community-bsp $ repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b dylan
fsl-community-bsp $ repo sync
$MACHINE=imx51evk source setup-environment build
Now i got the u-boot,uImage&qt-in-use rootfs images in deploy/images folder.
Then i flashed u-boot to the i.mx51 using peedi programmer as,
imx51>flash program card://u-boot.imx bin 0x00000000
But when i tried booting with the flashed u-boot.its not booting. Anything i'm missing in u-boot?
I have the source of working u-boot for the kit i'm using. Is it possible to add that source to the yocto as recipe, if yes how to integrate the u-boot into project.
Create a layer and create a .bb file (this is the recipe) IF your u-boot is new (new version?). In case you need to change an existing recipe, then create a .bbappend. Check the development manual under the Yocto documentation page, lots of info related to this task is explained.
And, it would be very-very nice if you created your board machine file, with some basic configuration. As you´re not using a supported board.
And, only to let you know. I tested imx51evk with dora and it´s working like a charm.
Dear Daiane & Leonardo,
I built yocto bsp for my kit using bitbake qte-in-use-image (because i want qt embedded with qws server) and its booting now.
But its not completely booting.Its hangs when it reaches Configuring: update-modules as below,
Caching udev devnodes
ALSA: Restoring mixer settings...
Configuring network interfaces... Starting portmap daemon...
kernel.printk = 4 4 1 7
vm.lowmem_reserve_ratio = 1 1
In display it says Please wait:booting...
complete booting sequence is in https://dl.dropboxusercontent.com/u/12382973/errorLog.txt
Help me with this.
I need to update the document, but the latest stable branches are the dora ones. Make sure you MACHINE is correct and try baking a smaller image for the moment (core-image-minimal, for example).
please try to use dd command to copy u-boot images into SD , then reboot your board.
# sudo dd if=u-boot.imx of=/dev/mmcblk0 bs=512
Yes i tried,
$sudo dd if=tmp/deploy/images/qte-in-use-image-imx51evk.sdcard of=/dev/sdb bs=1M
it created two partitions in sd card.one with uImage and other with rootfs.but its not booting in the development kit.
You are using mx51EVK, right? or a custom mx51 ?
Pls don't forget to sync the data after copying images.
$sudo dd if=tmp/images/qte-in-use-image-imx51evk.sdcard of=/dev/sdb bs=1M & sync
what's the u-boot version? legacy chips mx5 and mx2 use u-boot-2009.08.
Could you deploy only the u-boot into the SD card? Just have a try.
$sudo dd if=u-boot-XXXXXX.imx of=/dev/sdb bs=512 seek=2
I found the difference in ../fsl-community-bsp/sources/meta-fsl-arm/conf/machine/include/imx-base.inc
I changed the entrypoint and load address as below as in digi embedded yocto's u-boot's source file which worked fine.
UBOOT_ENTRYPOINT_mx51 = "0x94000000"
UBOOT_LOADADDRESS_mx51 = "0x94000000"
also i changed the serial console to,
SERIAL_CONSOLE = "38400 ttymxc1" as required.
Then i commited the git and bitbaked.but still i'm not able to boot the u-boot after flash.
i hereby given the sources,
freescale meta source for comparsion,
I'm not using freescale's evalution kit. i'm using digi's i.mx kit.(http://www.digi.com/products/model?mid=3402). The previous digi's yocto i used has the SERIAL_CONSOLE = "38400 ttymxc1".
I´m not sure if I got everything from your description. But, if you´re using the default configuration from meta-fsl-arm (as I think you are), the u-boot you should have in your sdcard is 2013.10, not 2009.08. But, last time I tested this board it was working.
I´m going to start a build over here and test it on my board. Then we can double check. And it would be better to use dora instead, as it´s the latest stable branch now