• State Resolved
  • Locked Locked
  • Replies 20 replies
  • Subscribers 100 subscribers
  • Views 4657 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Beaglebone Black - Android 4.2.2 - Question

James Barkwith
Prodigy 160 points
Part Number: BB-BONE-LCD7-01.Version: 00A3andBB-BONE-LCD4-01.Version: 00A1Maybe the LCD7 00A3 isn't recognised/supported? 
Other Parts Discussed in Thread: DA8XX

Hello,

I was just wanting some assistance with the Beaglebone Black image of Android, which is available from here:

http://downloads.ti.com/sitara_android/esd/TI_Android_DevKit/TI_Android_JB_4_2_2_DevKit_4_1_1/index_FDS.html

This image works correctly. I have a 4DCAPE-43T CAPE from 4D Systems which works well, however the prototype 4DCAPE-70T CAPE does not display at all. The CAPE is based on the latest revision LCD7 cape from CircuitCo, so I wonder if this image has the same sort of problem as the LCD7 cape too?

I was just wanting to know if there was any chance the image could be updated to allow the 7" CAPES to function correctly? It is currently just a blank screen.

On a seperate note, I have been discussing the Android 4.2.2 image with Andrew Henderson from here:

http://icculus.org/~hendersa/android/

He has a 4.2.2 image which uses the 3.8 Kernel. As I understand it, the TI image uses the 3.2 Kernel. One downside to Andrews image is it doesnt use hardware acceleration for the GPU like the TI image does, so it is all in software and is therefore slower, however since it uses the later 3.8 kernel it allows the use of more Capes, access to the device tree to configure SPI/UARTS/I2C etc which the 3.2 kernel I believe does not allow. This makes it more usable for users who wish to 'do' more 'stuff' with Android and other devices.

I am just wondering if TI is still developing this, and if the image will be going to 3.8 at all, while still maintaining the hardware accelerated GPU features it has currently, and also bringing in compatibility for the 7" LCD CAPES?

I have been in touch with Tyler Berryhill and Mark Easley from TI, who pointed me over to this forum.

I am not linux expert myself by any means.

Kind Regards

James

  • 0
    TI__Expert 5400 points

    Hi James,

    As of now there is no plan to migrate to 3.8 kernel.

    LCD7 cape support is available in kernel. Please share the complete bootlog. I want to check why LCD cape is not getting detected on your setup.

    Regards,

    Pankaj Bharadiya

  • 0 in reply to Pankaj Bharadiya
    Prodigy 160 points

    Thanks for the reply

    Sorry you are going to have to spell out to me how to provide you the bootlog, or even how to access it.

    Regards

    James

  • 0 in reply to James Barkwith
    Prodigy 160 points

    Google is my friend.

    I hope I did it correctly.

    ADB from my PC to get logcat. Attached.

    adb logcat -v long > James.txt

    Regards

    James

  • 0 in reply to James Barkwith
    TI__Expert 5400 points

    Hi James,

    Please run adb dmesg > Bootlog.txt and share the file.

    Regards,

    Pankaj

  • 0 in reply to Pankaj Bharadiya
    Prodigy 160 points

    adb shell dmesg > Bootlog.txt seemed to work

    Attached

    Regards

  • 0 in reply to James Barkwith
    Prodigy 160 points

    Did the same thing on the 4DCAPE-43T and that worked and showed in the log.

    Attached.

    Is it possibly due to the revision of the LCD7 that the 4DCAPE-70T is based on?

    The EEPROM of both the 4DCAPE-43 and the 4DCAPE-70 have 2 fields which we were told were critical for the loading of the drivers, so these remained with the LCD4 and LCD7 information, so the correct driver was loaded.

    Part Number: BB-BONE-LCD7-01.
    Version: 00A3

    and

    Part Number: BB-BONE-LCD4-01.
    Version: 00A1

    Maybe the LCD7 00A3 isn't recognised/supported? 

    Just a thought.

    It does however work correctly on Angstrom as well as the other Android 4.2.2 distribution which I mentioned in the first post.

    Regards

    James

  • 0 in reply to James Barkwith
    TI__Expert 5400 points

    Hi James,

    You are right. This SDK is tested with LCD7 REV A1 and A2.  LCD7 REV A3 may not work directly.

    Please refer to blow link (Note section) for more details.

    http://processors.wiki.ti.com/index.php/TI-Android-JB-4.2.2-DevKit-4.1.1_UserGuide#Hardware_Requirements

    Will you please look into working kernel <kernel>/arm/arm/mach-omap2/board-am335xem.c file to figure out  changes needed to add LCD7 REV 3 support and integrate those changes to 3.2 SDK kernel.

    Regards,

    Pankaj Bharadiya

  • 0 in reply to Pankaj Bharadiya
    Prodigy 160 points

    Hi Pankaj

    Ok, good to know what is wrong then.

    I am not sure what you require me to do. I have virtually 0 linux experience so I am not sure where to even begin.

    If you can give some direction I can try and assist...

    If you want to know the changes between A2 and A3 of the LCD7:

    "In revision A3 the Enter button has been moved from GPIO3_19 to GPIO0_3 and LCD_DVDD_EN has moved from GPIO1_31 to GPIO0_2. These changes in GPIOs are to support awake interrupt in sleeping mode."

    I believe those are the only differences.

    Regards

    James

  • 0 in reply to James Barkwith
    Prodigy 160 points

    Hi Pankaj

    Any news? Was there something you wanted me to do?

    To add to this inquiry, is there a way to change the PWM frequency which controls the backlight?

    Currently it is set to 2Khz. Is it possible to reduce this down to say 200-500Hz ?

    Regards

    James

  • 0 in reply to James Barkwith
    Prodigy 160 points

    Hello....

    Can I please get an update to the LCD7 support for 00A3 please?

    It has been some time since I got a reply.

    Ignore the question about the PWM freq above, just needing LCD7 00A3 support on this image.

    Please advise

    Kind Regards

    James

  • 0 in reply to James Barkwith
    TI__Expert 7220 points

    Hi James,

    This is the patch adds support for LCD7 revision A3

    https://gitorious.org/rowboat/kernel/commit/3d25b48e7d1cd797cc8086ce539b3a5947b0aa14

    This is already present in the rowboat-am335x-kernel-3.2 commit log. Can you check if it is present in your kernel sources.

    Regards,

    Arun

  • 0 in reply to Arun Joseph
    Prodigy 160 points

    Hello Arun

    Thanks for the reply

    Sorry I am not sure what you mean by 'your kernel sources'.

    I have simply downloaded the image from TI (Link above in the first post), I have not rebuilt a kernel.

    How does this patch get applied exactly?

    If it is not in the download from TI then I will not have it...

    Can you please explain how to apply the patch?

    Regards

    James 

  • 0 in reply to James Barkwith
    TI__Expert 7220 points

    HI James,

    The boot log shared indicates that there is no display cape found. Can you print the display cape EEPROM contents from the bone_setup_display_daughter_board function. Can you also try to force LCD7 A3 initialization overriding revision check? (To isolate EEPROM issues.)

    Regards,

    Arun

  • 0 in reply to Arun Joseph
    Prodigy 160 points

    Hello Arun

    Sorry you are going to have to spell out how to perform this, I have very little experience with Linux and even less with Android, esp when it comes to editing or retrieving data from the devices.

    The LCD7 and 4DCAPE-70T I have both work on Angstrom and Debian distrubutions with the BBB, so I am surprised this Android release cant find a Cape attached.

    Please be specific about what you want me to do/test and how that test is performed, such as providing commands for me to type in or specific instructions, and I can do it all and provide you the information you need.

    Is this something you need me to do via ADB?

    Kind Regards

    James

  • 0 in reply to James Barkwith
    Prodigy 160 points

    Hello Arun

    Any update for this?

    Regards

    James

  • 0 in reply to James Barkwith
    Prodigy 160 points

    I did some experimenting and change the EEPROM ID from being off to both being ON and the CAPE was detected! However not correctly it seems

    <6>[ 1.286560] Detected a daughter card on BeagleBone..
    <6>[ 1.291564] BeagleBone LCD4 cape board detected
    <6>[ 1.296508] Board Name: BeagleBone LCD7 CAPE............00A3Beagleboardtoys.BB-BONE-LCD4-01.325012LCD40295
    <6>[ 1.306610] Hardware revision: 00A3Beagleboardtoys.BB-BONE-LCD4-01.325012LCD40295
    <4>[ 1.314971] da8xx_lcdc.0: alias fck already exists
    <6>[ 1.320343] da8xx_lcdc da8xx_lcdc.0: GLCD: Found NHD-4.3-ATXI#-T-1 panel
    <6>[ 1.336059] IN : lcd_cape_tsc_init
    <6>[ 1.339904] Setup LCD cape touchscreen

    Seems to be a mixture of LC4 and LCD7

    Display comes up white and weird, as it will have the wrong timing for the display as it thinks its a 4.3"

    Not sure what is going on.

    James

  • 0 in reply to James Barkwith
    Prodigy 160 points

    Ignore the above, working fine now

    What I have discovered is the EEPROM ID cannot be 0x57, as the CAPE is not detected in Android.

    What I changed it to 0x54 it fired up correctly.

    Not sure why that is yet, maybe its used for something else already on Android. Will try and find out.

    James

  • 0 in reply to James Barkwith
    Prodigy 130 points

    OK, you got it working, great!

    Now for the rest of us Android for dummies who would like to get our setup with BBB and LCD7 working.

    And you will need to spell it out for us!

    HOW DID YOU DO IT?

    Please help the rest of us out with a concise answer or just send us the .iso bootable image.

    Thanks in advance.

  • 0 in reply to James Barkwith
    Prodigy 10 points

    James, can you please post your Debian Image that works with the 4DCAPE-70T for me to download.  I am looking for an image to use with Win32DiskImager to write to a micro SD card.  I have been burning tons of hours trying to fix or write work around code for a Jitter issue for the 4DCape-70T.  Please let me know if you can help.  Thanks.  I appreciate it.

     

    Dan

  • 0 in reply to Daniel Renne
    Prodigy 160 points

    Hi Dan

    Not 'my' image, but its a Debian image with the latest kernel which has the fixes for the jitter issues.

    http://rcn-ee.net/deb/testing/2014-02-24/

    Check that testing folder periodically to see if there is a later version released.

    Its from Robert Nelson.

    I have tested one a month or so ago and the touch was working great.

    Regards

    James