Beagleboard xm + Beadaframe + Touch problem

Discuss TI Beagleboard, Pandaboard, their related extensions and accessories
esky-sh
Posts: 1435
Joined: Sat Dec 20, 2008 4:21 am

Re: Beagleboard xm + Beadaframe + Touch problem

Post by esky-sh » Fri Jul 25, 2014 7:47 pm

Hi,

you do not need any patch if you want boundle beadaframe with your beagleboard-xm . please refer to our release notes:

2011-11-16 Android update
===========================
- TI Android GingerBread-2.3.4-DevKit-2.1 ports on BeagleBoard xM Rev. B w/ Beada Frame.
- Backlight switching support
- PWM backlight support(need new cpld firmware)
- RTC support(need new cpld firmware)

esky-sh
Posts: 1435
Joined: Sat Dec 20, 2008 4:21 am

Re: Beagleboard xm + Beadaframe + Touch problem

Post by esky-sh » Fri Jul 25, 2014 8:09 pm

2.5 –xM Revision B vs. –xM Revision C

There were seven changes made to the BeagleBoard-xM Rev C version over the Rev B design.
  • o Resistor loading was changed to allow for the reading of the Rev C revision by the SW. GPIO171=0, GPIO_172=1, and GPIO_173=0.
    o Replacement of the processor from ES1.1 to ES1.2. For a detailed description of the issues present in the ES1.2 revision, please refer to http://focus.ti.com/lit/er/sprz319a/sprz319a.pdf . There are no issues resolved by ES1.2 that are anticipated to have any impact on the operation of the BeagleBoard-xM. ES1.2 is the latest revision.
    o Fixed capacitor footprint in the PCB layout.
    o Replaced the microSD connector with a new part. The current part was targeted for EOL and a new one was required. This required a PCB footprint change.
    o Redesigned the overvoltage protection circuit. We were seeing issues with a small number of boards being damaged on the TPS2054 USB power FET, so a new design was implemented. Overall operation is the same as the original version with te exception that it is now possible to power the entire board over the USB OTG port. This includes the HUB. Care should be taken not to add high current devices on the USB ports as that will cause the host to shut down the USB port,
    o Changed the default power state of the USB HUB to OFF as an added layer of protection to make sure the USB power rails are off on initial power up. This will minimize the initial current drain on the board. SW can turn on the HUB power as needed by setting the TPS65950 LEDA/VIBRA.P pin LO to turn it on.
    o Added the ability for the SW to detect when the board is powered from the DC supply or the OTG supply. Status is read from GPIO.6 pin on the TPS65950. If LO, then the board is powered from the DC jack. The HUB will only work in the DC powered mode so this change allows the board to know not to try and initialize the USB Host when under OTG power..

esky-sh
Posts: 1435
Joined: Sat Dec 20, 2008 4:21 am

Re: Beagleboard xm + Beadaframe + Touch problem

Post by esky-sh » Fri Jul 25, 2014 8:13 pm

so your beagleboard-xm will work well with android images on our ftp.

esky-sh
Posts: 1435
Joined: Sat Dec 20, 2008 4:21 am

Re: Beagleboard xm + Beadaframe + Touch problem

Post by esky-sh » Sat Jul 26, 2014 3:27 am

You need to install android runtime images on our ftp which we customeriezed touch screen driver and other stuffs for beadaframe.
Please upload your serial logs if you still with problem.

esky-sh
Posts: 1435
Joined: Sat Dec 20, 2008 4:21 am

Re: Beagleboard xm + Beadaframe + Touch problem

Post by esky-sh » Thu Aug 07, 2014 7:42 pm

Can you run 'getevent' command under your serial console of BB?

admin
Site Admin
Posts: 56
Joined: Fri Dec 19, 2008 11:11 pm

Re: Beagleboard xm + Beadaframe + Touch problem

Post by admin » Fri Aug 08, 2014 2:29 am

please touch your beadaframe touch panel when you execute getevent, and watch if any touch screen events sending out.

Post Reply

Who is online

Users browsing this forum: No registered users and 3 guests