My email client has been having difficulty. My sincere apologies if you already received this message. (I am subscribed to the mailing list and did not see this email arrive)
----- Forwarded Message ----- From: William Gibson <william.gib...@harbingerbiotech.com> To: "angstrom-distro-devel@linuxtogo.org" <angstrom-distro-devel@linuxtogo.org> Sent: Tuesday, October 22, 2013 1:44:41 PM Subject: Problem changing built-in LCD4 cape .dts Hello all. I have spent two weeks on this so far, but still very much new to this. I've googled things, read the manuals and attempted to 'use the source, Luke'. I successfully bitbaked cloud9-gnome-image from the instructions here http://www.angstrom-distribution.org/building-angstrom Earlier I also bitbaked systemd-image, which also worked. Everything works! I'm compiling for a beaglebone-black, with MACHINE=beaglebone. I'm working on a Debian VM - was unable to produce working results with Ubuntu VM or Arch VM. I'm using the master branch of the setup scripts, trying to get the latest official release (not bleeding edge) version. I have an LCD4 cape; I'm trying to fix the UART2 misallocation bug since I can't wait until the next release of Angstrom for the fix. However I apparently cannot make changes to this file on the 'bone: /lib/firmware/BB-BONE-LCD4-01-00A1.dts, or the corresponding .dtbo What I've done: 1. bitbaked cloud9-gnome-image and verified it works on my 'bone - before I made any alterations 2. Patched every file BB-BONE-LCD4-01-00A1.dts on my VM 3. Removed every file BB-BONE-LCD4-01-00A1.dtbo on my VM 4. bitbake cloud9-gnome-image -c clean 5. bitbake cloud9-gnome-image -c cleansstate 6. bitbake cloud9-gnome-image -c compile -f 7. bitbake cloud9-gnome-image 8. sudo tar -x the resulting Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.12-beaglebone.rootfs.tar.gz into my /tmp folder, and looked in /lib/firmware. However: A. This set of steps *did not* recreate BB-BONE-LCD4-01-00A1.dtbo from the .dts. B. The .dts in /lib/firmware was the *unchanged* version. Where did it come from? I verified the timestamp on the .tar.gz, it was a new file. I thought maybe it was caching it in the tar (now I'm pulling at straws) and did echo 0 > Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.12-beaglebone.rootfs.tar.gz to empty it. Repeated without success. Then I decided to compile the dtbo manually, so I used dtc, then retried steps 4-7 - again without success. Questions: 1. How is it possible that bitbake can package a file (the .dts) which doesn't exist on my hard drive? I can only assume it must be stored in some other cache - like a uImage or zImage or something. 2. Please verify that /build/tmp-angstrom_v2012_12-elibc/sysroots is where the rootfs is constructed, and what is used to create Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.12-beaglebone.rootfs.tar.gz? 2a. Yes, I did modify the .dts in sysroots as well, but it didn't change the result. 2b. Where is the command to actually create this tar file? I looked for every command starting with "tar" in the setup-scripts folder but there are so many..... I also tried going backwards from the cloud9-gnome-image.bb, but got lost. 3. In what step does bitbake generate .dtbo from .dts? I could only find a makefile for the am335x-bone-common.dtsi file - which predates the cape manager changes (according to Robert Nelson "capes such as the lcd3 came out before all the 3.8 capemgr/eeprom/stuff was written in stone".) There isn't a similarly obvious makefile for the /firmware/ directory. 3a. How can I re-run this step? Do I have to do a make clean/make all, or via bitbake...? Somehow I expected a 'bitbake -c clean' to clean and re-build everything, like it does in make. Is there a way to accomplish this? Should I use cleanall? rm_work? There are so many tasks available and no way (that I see) to find out what they actually *do*. grepping through the sources brings up distantly related files with little to no documentation. 4. Please confirm that the new versions of the capemgr do actually load from /lib/firmware. Old information on the internet says that doesn't work, but seems to be outdated. If not, then from where? And how can I make the changes I need to? 5. Am I using the correct branch of the setup-scripts? I'm not sure how to choose. Can someone point me in the right direction(s)? I very much appreciate your time reading this; William P.s. is there a defined release schedule for Angstrom and/or Beaglebone Black? I couldn't find one. P.p.s. I successfully made the .dts change with Robert Nelson's build scripts, and compiled a working Ubuntu - so I'm confident my dts changes are correct. But I want Angstrom! _______________________________________________ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
