Carlos, On Mon, Aug 18, 2014 at 6:10 AM, Carlos Rafael Giani <[email protected]> wrote:
> I rebuilt the image, with the proper layers, but still I get an incorrect > u-boot environment. Full u-boot serial output and boot log follow below. > uname -a prints: Linux beaglebone 3.14.16 #1 Thu Aug 14 18:00:21 CEST > 2014 armv7l GNU/Linux > (the kernel was built by the linux-ti-staging recipe) > > The u-boot problem bootfile is set to uImage, and mmcboot uses bootm > instead of bootz. > Your u-boot (2013.04-rc1-14237-g90639fe-dirty) is not the one provided for meta-ti (2014.07). Issue these commands: bitbake virtual/bootloader -ccleansstate bitbake virtual/bootloader -f > > Furthermore, once I correct these two values, it boots, but I see this > eventually: > > Error opening /dev/fb0: No such file or directory > > After a bit of investigation, it turned out that omaplfb wasn't loading > due to missing symbols: > > root@beaglebone:~# modprobe omaplfb > [ 83.010309] omaplfb: Unknown symbol register_vsync_cb (err 0) > [ 83.016642] omaplfb: Unknown symbol unregister_vsync_cb (err 0) > > Searching for this, I found > https://groups.google.com/forum/#!topic/beagleboard/dcLtpK7ZsX0 . > According to this, in the kernel log, I should set CONFIG_FB_DA8XX to "y". > Is this still correct for linux-ti-staging 3.14.16 ? > To use DRM driver you should set: CONFIG_DRM=y CONFIG_DRM_I2C_NXP_TDA998X=y CONFIG_DRM_TILCDC=y To use de FB driver: CONFIG_FB_DA8XX=y CONFIG_FB_DA8XX_TDA998X=y Here is a reference: http://processors.wiki.ti.com/index.php/Linux_Core_LCD_Controller_User_Guide Regards, -- *dS Diego Sueiro Administrador do Embarcados www.embarcados.com.br <http://www.embarcados.com.br/?utm_source=assinatura_diego&utm_medium=e-mail&utm_campaign=Assinatura%20Email%20Diego> /*long live rock 'n roll*/
-- _______________________________________________ meta-ti mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-ti
