Hello Andrew, just a question, I'm continuing to work with your bbbandroid using a 4gb microSD card. This will not the same if I use eMMC onboard? this is also 4 gb. Next.. what packets i can easly remove without damages? and how to do it?
Ciao, gianmaria Il giorno martedì 17 marzo 2015 21:20:10 UTC+1, Andrew Henderson ha scritto: > > Hello Gianmaria. Sorry for the delay in getting back to you on this. The > .img files for the various Android partitions are generated as part of the > BBBAndroid build process. But, the makefile installs the kernel, firmware, > and modules into the file system after the .img files are generated. I stay > away from installing Android into the eMMC because I don't want to limit > the size of the partitions to fit within the 2GB/4GB eMMC. That is why I > target the microSD card for the BBBAndroid build scripts. You can use the > .img files that are generated during the BBBAndroid build process and use > fastboot to place the images onto the eMMC (as Chris's instructions show in > the link that you mentioned). But, you may have to shrink the size of the > images because I include a few extra packages (such as the i2ctools) that > aren't in the usual AOSP packages. Because of this, my images are bigger > than normal and may not fit onto a 4GB eMMC as-is. > > > On Monday, March 2, 2015 at 1:04:39 PM UTC-5, [email protected] wrote: >> >> >> Hi Andrew, >> i found your git very usefull. Can you give me some information on how to >> create .img files and boot android copletly from eMMC? Something like >> 2net.co does here: >> >> https://github.com/csimmonds/bbb-android-device-files/tree/kk4.4-fastboot >> >> Thank you in advance. >> >> Regards, >> Gianmaria >> >> Il giorno giovedì 15 gennaio 2015 05:01:32 UTC+1, Andrew Henderson ha >> scritto: >>> >>> I don't have the various cape .dtbo overlay files copied into the image >>> (aside from those statically built into the am335x-boneblack.dtb file in >>> the "dtbs" directory of the boot (first) partition. To add any overlays to >>> your system, copy the necessary .dtbo files into /system/vendor/firmware >>> directory of the rootfs (second) partition. You can automatically load the >>> overlay on boot by adding the appropriate commands to the >>> init.{ro.hardware}.rc file in the root directory of the rootfs partition. >>> Just look in that file for the "BBBAndroid" comments and read them to see >>> how to do this. >>> >>> After the overlay loading command, you can add commands to chmod the >>> permissions on the appropriate files in the /dev filesystem to relax the >>> permissions on the UART tty files to allow apps to access them. Just look >>> in the init.{ro.hardware}.rc file for some examples (I chmod /dev/spidev* >>> and the /dev/i2c* devices, for example). Ideally, you'd have a manager >>> access such hardware resources on your behalf via the Android HAL. But, >>> for prototyping, it isn't a big deal to open these devices up and let apps >>> talk to them directly via JNI. >>> >>> This is probably a good time to mention that I've recently put together >>> a book which covers all the details involved in creating Android apps that >>> talk directly to hardware. It is "Android Hardware Interfacing with the >>> BeagleBone Black" from Packt Publishing, and it is scheduled to go to print >>> next month: >>> https://www.packtpub.com/hardware-and-creative/android-hardware-interfacing-beaglebone-black >>> >>> So, if you're still fighting with the details a few weeks from now, >>> there will actually be a reference book to help you out (using BBBAndroid, >>> too!). >>> >>> On Tuesday, January 13, 2015 at 4:29:20 PM UTC-5, [email protected] >>> wrote: >>>> >>>> Thanks a lot for creating this. >>>> I have got this image and the BBB now is running using a 4DLcd 7". >>>> For my experiments, i'm trying to use UART4 (as it's available in the >>>> headers of the LCD) so i installed an apk for serial testing >>>> http://code.google.com/p/android-serialport-api/ but when I try to >>>> send some info I get the error "You do not have read/write permission to >>>> the serial port" >>>> >>>> I read that i have to enable muxing on the pins to enable uart4. How >>>> can I do that in you image? >>>> >>>> Any info is appreciated. >>>> >>>> Thx >>>> >>>> On Saturday, November 15, 2014 at 3:25:58 PM UTC-6, Andrew Henderson >>>> wrote: >>>>> >>>>> I have built a new microSD card image for BBBAndroid >>>>> (bbbandroid_111514.img), and it is now available for download. Just >>>>> follow >>>>> the link at bbbandroid.org to download it. >>>>> >>>>> In this build, USB ADB support is working just fine. I've been able >>>>> to connect with the BBB using both command-line ADB and ADB through the >>>>> Eclipse ADT under both Windows and Linux. You can push/pull files, >>>>> install/reinstall apps, get logcat output, shell, etc. using the USB >>>>> cable >>>>> that came with your BBB board. If you want a root shell on Android, the >>>>> ADB shell is the way to go. >>>>> >>>>> I changed the USB ID to 18D1:4E23 for the BBB device when BBBAndroid >>>>> is being used. These are the same USB vendor and device IDs as a Google >>>>> Nexus S. The reason that I changed this is to make life much easier for >>>>> the Windows users. Each phone vendor provides their own drivers for USB >>>>> ADB, and it was difficult for the Windows users to get the drivers set up >>>>> properly. This should make things much easier for them. Linux users >>>>> never >>>>> had a problem with it, since their USB ADB worked right out of the box. >>>>> >>>>> I also shrunk the image to 7.6 GB to accommodate everyone that was >>>>> having difficulty writing the 8 GB image to their microSD cards that were >>>>> actually a little bit smaller than 8 GB. >>>>> >>>>> Andrew >>>>> >>>>> >>>>> On Sunday, September 28, 2014 11:14:24 AM UTC-4, Andrew Henderson >>>>> wrote: >>>>>> >>>>>> Hello all. I have released a new port of Android for the BBB. This >>>>>> version uses AOSP 4.4.4 (KitKat) and the 3.8 Linux kernel. I have made >>>>>> build instructions and a pre-made image available at >>>>>> http://www.bbbandroid.org. I use a combination of AOSP repos and >>>>>> Rowboat build scripts, and I have a few custom repos for the kernel, >>>>>> bootloader, and additional "external" tools (such as i2c-tools). You >>>>>> can >>>>>> view the repo manifest XML file for the project here: >>>>>> >>>>>> >>>>>> https://github.com/hendersa/bbbandroid-manifest/blob/master/bbbandroid-aosp-4.4.4_r1-3.8.xml >>>>>> >>>>>> Because this Android image uses the 3.8 kernel, you should be able to >>>>>> just plug in your capes and go without any hassle: >>>>>> >>>>>> Built-in HDMI cape: >>>>>> http://i.imgur.com/q4AZQ95.jpg >>>>>> >>>>>> 4D Systems LCD capes: >>>>>> 4DCAPE-43T: http://i.imgur.com/6qHmgqX.jpg >>>>>> 4DCAPE-70T: http://i.imgur.com/UZLG7Or.jpg >>>>>> >>>>>> CircuitCo LCD capes: >>>>>> LCD3: http://i.imgur.com/LC7SrBB.jpg >>>>>> LCD4: http://i.imgur.com/1xBQ8R6.jpg >>>>>> LCD7: http://i.imgur.com/vxoqROE.jpg >>>>>> >>>>>> Andrew >>>>>> >>>>> -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
