Hi Andrew thanks for all your hard work can you assist me to add a new
4dcape-70ct cbl
works with 4dcape-70t but not with the new 4dcape-70ct cbl
Regards
Andre
On Sunday, 28 September 2014 17:14:24 UTC+2, Andrew Henderson wrote:
>
> Hello all. I have released a new port of Android for the
Hi,
I need to build AOSP kikat 4.4 for beaglebone black and linux kernel is 4.1
for my BLE integration.
Do you have any reference build for guide to do such build
regards
venkat
baytech
On Tuesday, March 1, 2016 at 6:42:10 AM UTC+5:30, dariush.ab...@gmail.com
wrote:
>
>
>
> On Sunday,
On Sunday, September 28, 2014 at 6:44:24 PM UTC+3:30, 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
>
I recently followed the instruction to build my own image(Android 4.4.4 +
kernel 3.8.13), the ADB doesn't work no matter whether I replaced the three
file you upload in the response.
Any suggestions.
Thanks
-yin
在 2014年9月28日星期日 UTC-4上午11:14:24，Andrew Henderson写道：
>
> Hello all. I have
Hi,
Can any body help me out to automount(mmc or usb) supports to BBB or not
with android kitkat 4.4.4. If it supports can help me how to add support.
Thanks & Regards,
Narasimha.
On Saturday, April 18, 2015 at 1:13:53 AM UTC+5:30, cam...@gmail.com wrote:
>
> Seems to work now. I made sure
Seems to work now. I made sure udev had the correct entries and I was able
to boot into Android and toggle an LED once I modified a few pertinent
files.
Thanks!
On Thursday, April 9, 2015 at 5:43:00 PM UTC-4, Keith Conger wrote:
I can confirm it works fine with MacOSX, my guess its a
Was this ever resolved? I am experiencing a similar issue.
On Tuesday, March 31, 2015 at 2:06:14 PM UTC-4, jimmy...@gmail.com wrote:
Hi Andrew,
Please you help me with the USB ADB.
I downloaded bbbandroid_111514.img.xz image, and I wrote this image to my
Beaglebone Black.
I use Ubuntu
Hi Andrew,
Please you help me with the USB ADB.
I downloaded bbbandroid_111514.img.xz image, and I wrote this image to my
Beaglebone Black.
I use Ubuntu 14.04, I have made /etc/udev/rules.d file with content:
#adb protocol on BeagleBone Black (BBB 1)
SUBSYSTEM==usb, ATTR{idVendor}==18d1,
Since this took me a few days to figure out, I figured I'd post how I got
Wifi working in bbbandroid. Hope this saves a few days of your life :)
Obviously swap the kernel modules with the ones appropriate for your
device.
# Add to
Hey Andrew,
I'm able to boot the 3.14 kernel now with usb and proper hdmi support.
I then started to include the bluetooth modules. The modules seem to load
fine.
However, now when I'm seeing the boot animation and finally enter to
homescreen a crash happens and the boot animation appears again.
Hi Andrew,
I retried the 3.14 kernel.
I'm getting the following error:
WARNING: CPU: 0 PID: 110 at drivers/usb/gadget/f_fs.c:2595
ffs_ep0_write+0x44d/0x474()
[ 149.939235] Modules linked in:
[ 149.942448] CPU: 0 PID: 110 Comm: adbd Tainted: GW3.14.35+ #6
[ 149.949616]
For the video issue I tried changing the video parameter to 1920x1080-16@60
the native resoltion of my display. However, when I did, I did not see
anything on the display.
Here is a small video of the display so you get what I mean with flicker.
It seems that some video buffer isn't emptied or
OK, this is starting to make more sense. 1920x1080 at 60 Hz is not a
supported mode for the BBB. I've seen screen shearing on 1920x1080 at 24 Hz
before with OpenGL ES on 3.14 with single buffering before. My suggestion
is to use the video= parameter to set a supported resolution lower than
I have not yet tried FunctionFS under 3.14. The only reason it was in the
3.8 kernel was to support ADB, so you can remove it if you wish. I am
unfamiliar with that particular error.
On Wednesday, March 18, 2015 at 6:51:03 AM UTC-4, Michael Gobbers wrote:
Hi Andrew,
I retried the 3.14
Hello Michael. I believe that Keith Conger supplied you with the 3.18
backport drivers for Bluetooth, right? I have Keith's patches sitting in my
review queue, but I haven't yet created a branch with them. The problem
that I'm running into is that the 3.8 kernel has the capemgr in it, but the
Thank you so much Andrew,
you are really kind. I will keep this extra packets for now.. I also
have to include the libs you used in your book to handle spi devices..
will keep in touch.
Gianmaria
Italy
On mar, 2015-03-17 at 13:20 -0700, Andrew Henderson wrote:
Hello Gianmaria. Sorry for the
Are you using an LCD cape? I have seen flickering similar to what you
described with the 3.8 kernel when I forced a video resolution via the
video= kernel command line option (in uEnv.txt in the boot partition) for
the LCD3/4/7 CircuitCo capes and the 4DCAPE-43T/70T capes from 4D Systems.
For
Hi Andrew,
Thanks for the reply. Indeed Keith Conger supplied me with the patches.
I have gotten a bit further now as I'm getting the hand of configuring and
building the kernel for the beaglebone black. I'm now able to boot all the
way to the android home screen.
However, I have major graphical
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
Hello Grayver. Actually, USB cameras on the BBB are not something that I
have any experience with. I do have support for V4L2 enabled in the kernel,
and I have enabled USB camera support in the device/ti/BoardConfig.mk file
for the Android build. But, I haven't given it a try to see how well
Hi Andrew*,*
I am trying to use the BBB for basic picture analysis with OpenCV over
Android OS.
I was wondering, does this release support any basic usb cameras (are there
any drivers for known products)?
So far i have found this
Hi Andrew,
Thanks for the great job you've doing on the beagleboard.
For the project I'm currently working on I included bluetooth support to the
build. However, it seems that the le functionality isn't working because it
relies on some modules not available in the 3.8 kernel.
Some people
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
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
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
Hi Andrew,
Maybe you can help me,I'm trying to use beaglebone black with a custom
touch screen, so i tough that Android O.S would do the job in the best way.
I've downloaded the prebuild Android 4.4.4 image but it didn't support the
touch of the screen.
I Contact the company who made the screen
Hi Andrew,
I'm not sure if I send it already but to make sure I send it again.
I'm trying to connect BBB to custom touch screen, I've tried with the
custom O.S and it didn't work.
I though the best way to achive such a connection would be with Android
O.S, so i've download the AOSP 4.4.4
1. Your repo command for fetching the AOSP code is hanging up, which can be
caused by a few different things. Review the Source sync issues section
of https://source.android.com/source/known-issues.html. Also, ensure that
you are using the latest version of git. This does not mean that you
I realize I am kind of lurking on this thread,but could you posting large
console output please post these console outputs to a pastebin ?
I am interrested in debug information, but pastebin is surely better for
this sort of output.
On Mon, Dec 22, 2014 at 7:19 AM, Andrew Henderson
Hi andrew! i tried you images (old and new) for beagle bone black. But i am
not getting booted into it.
Is it required to connect Display, LAN, and USB mouse.
If I use HDMI CABLE (sony erricsion) to connect my PC monitor, will it
drive.
the FTDI output:
[6.038794] g_ffs: read descriptors
( 583): Initializing input manager, mUseDevInputEventForAudioJack=false
I/SystemServer( 583): Window Manager
I/WindowManager( 583): No existing display settings
/data/system/display_settings.xml; starting empty
I/WindowManager( 583): No keyguard interface!
I/InputManager( 583): Starting
Using the HDMI cable to connect the BBB to your DVI/HDMI display should
work without an issue. You do not need HDMI audio to use the Android
image. I have used it without an issue with the various LCD capes without
audio, for example. Using the ethernet LAN connection and USB mouse are
also
Hi Andrew.
Could you please tell me how can i add dropbear support for android 4.4
running on linux 3.2 kernel.
Looking for a quick response from your end..
On Sunday, 16 November 2014 02:55:58 UTC+5:30, Andrew Henderson wrote:
I have built a new microSD card image for BBBAndroid
Excellent!
--
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 beagleboard+unsubscr...@googlegroups.com.
Hi Robert,
Thanks for the help ..
Finally, I am Successful in booting the u-boot with the blank EEPROM . but
now the kernel booting stopped at certain point, it hangs trying to mount
the rootfs (/dev/mmcblk0p2).
*Waiting for root device /dev/mmcblk0p2...*
after this print it got stuck
In addition to my previous comment (posted on 03/11/2014)
I have also tested with v2014.10 and got the same output as before :
U-Boot SPL 2014.10 (Nov 03 2014 - 15:40:04)
Incorrect magic number (0x) in EEPROM
Could not get board ID.
Incorrect magic number (0x) in EEPROM
Could not
Thanks for the help Robert
I have done all the changes, whatever you have mentioned in the Patch file,
but still the board is not booting up. I think only the *s_init() function
(file:board/ti/am335x/board.c)* is keep on executing repeatedly, as i can
see only this log i.e.* **Unknown board:
Hi Andrew,
Now we are using one customized board based on Beaglebone Black Design. In
case of BBB TI is writing some board type configuration in the EEPROM, so
during the Initial booting process it reads those information and
configures the board accordingly.
As we are using one fresh
On Thu, Oct 30, 2014 at 10:50 PM, nishikantanay...@gmail.com wrote:
Hi Andrew,
Now we are using one customized board based on Beaglebone Black Design. In
case of BBB TI is writing some board type configuration in the EEPROM, so
during the Initial booting process it reads those information
Hi Andrew,
Thanks for the reply.
The only log for zygote that i can see in my FTDI output is:
[ 23.539523] warning: `zygote' uses 32-bit capabilities (legacy support
in use)
Then some other logs like:
[ 44.074598] init: sys_prop: permission denied uid:1003
name:service.bootanim.exit
Yes, that is the expected output. You're through most of the boot process
if zygote is started. Therefore, you aren't experiencing bootloader or
kernel problems.
Can you describe the problem that you are seeing in more detail? Do you
see anything on the screen at all? You should see the
Hi Andrew,
Thanks very much for the great work.
Now i am trying to port AOSP 4.4.4 (KitKat) for the BBB by using your repo
manifest XML file. I built the U-boot, Kernel Successfully and also created
the Filesystem. But the problem is after putting all the built images into
the microSD card,
I don't see any errors that are out of the ordinary in your FTDI output.
How long did you wait before giving up? If there is a failure on the
first boot, you should see some sort of failure beyond that in the log.
You can also run logcat from the FTDI shell to get some more details. If
you
Andrew,
Thanks very much for the very detailed explanation on the character of the
init.generic*.rc files pushing.
In regarding to the navigation bar, I am using an element14 BBB with
Circuito LCD4. So I don't have leisure to change the resolution. However I
can using the LCD panel on-board
Hello,
Great work appreciate.
It would be awesome if you can add USB WiFi Support for Atheros AR9271 or
Realtek RTL8188CUS Based Device
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
BeagleBoard group.
The suggested Wifi support would be awesome, its a common stack that people
can get their hands on easily. ADB over USB would also be greatly
appreciated when you publish a new image :)
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are
I'll have to make the next pre-made image a little smaller than the full
capacity of my microSD cards because so many of the manufacturers are being
very liberal on exactly how many bytes they consider 8GB to be...
I have a Realtek RTL8188CUS USB wifi dongle sitting here (an Edimax EW-7811
of
Hi Andrew,
I rebuild the BBBAndroid and created my own image. The ADB USB does work
after I replaced those (3) files you attached earlier. It is a very good
news.
But I did find out that I couldn't push file thru the ADB push. I tried
both the eclipse ADT and command line. Neither works. I've
The rootfs filesystem (the / filesystem) is set to read-only once you
reach the post-fs phase of boot. This is why you can't ADB push to it.
I've been on the fence as to whether I should remount this as read-write,
and I suppose that I probably should. Since I'm trying to open up this
Andrew,
It seems that the pre-built image size (8,018,460,672 bytes) is slightly
larger than a 8G uSD card size (7,939,784,704 bytes Sandisk HC). I had
difficulty to write the image to the SD.
Win32DiskImager (under Win7) complains; Image Writer (Ubuntu 12.04) also
complains. dd command does
Right now, I don't have any plans to flash the eMMC. BBBAndroid is
currently intended to be a prototyping platform, so I'd prefer to make the
entire OS easily removable in case you need to mount it on a different
machine and fix any changes that you made to .rc, .dtbo, or .ko files in
the
Wow great job Andrew! Just ran with this image with ease. Is there anything
built in that can be used to flash to eMMC? Any plans to integrate with the
SGX drivers for better graphics drivers?
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you
Hi Andrew, I will test it out and let you know the result. Thanks! -lei
On Monday, October 6, 2014 9:14:09 PM UTC-4, Andrew Henderson wrote:
I accidentally attached an incorrect .rc file with some additional testing
material in it. I'm attaching the proper one now.
On Tuesday, October 7,
I have not made a new premade image with USB ADB, but I have it working.
In your current BBBAndroid image, replace your uEnv.txt (/boot partition)
with the one I have attached. Replace your two init.genericam33xx*.rc
files (/rootfs partition) with the two I have attached. In addition to
I accidentally attached an incorrect .rc file with some additional testing
material in it. I'm attaching the proper one now.
On Tuesday, October 7, 2014 1:10:50 AM UTC, Andrew Henderson wrote:
I have not made a new premade image with USB ADB, but I have it working.
In your current
USB ADB is currently being worked on. The image I provided builds in
FunctionFS support, but I have not yet made the modifications to the .rc
files to point ADB to FunctionFS. I'm currently working on a few
modifications to the .rc files to make the image a bit more BBB friendly
for those
56 matches
Mail list logo
