• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 99 subscribers
  • Views 2082 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.

ThreeFive LCD screen trash output

sodjas
Intellectual 830 points

Hi Guys!

We have successfully built a beaglebone based custom terminal expanded with WIFI, custom touch, ThreeFive LCD and RFID.

For the first prototype it performs really good, we already made 20 and 25 days uptime test benchmarks without a single reboot, running a target terminal program on it.

The platform is Android ICS based on TI's branch.

We have only one weird thing which is not familiar to me since I'm not well experienced in hw building and LCD functionality. After some time -in total random way- the terminal'l LCD output is showing trash data lots of color lines.

I don't know whether this is a problem of the FFC/expansion connector or it is a software, for example frame buffer problem?

Could someone more experienced tell me a few hints what is going on here? I attached a video which shows the exact anomaly.

After reboot everything goes well again so I suppose it could be a software based stuff... But please help if someone had similar problems.

Beside this the platform really rocks what you see on the video is an IP65 terminal with shock proof touch interface running Android ICS.

best regards,

sodjas

also have a dmesg output, there is a lot fof irrelevant wifi info but everything seems to be good, maybe this helps someone who had some trouble with this before..

7356.dmesg.rtf

  • 0
    TI__Guru**** 393215 points
    Hi Sodjas,
     
    Could it be the RFID is causing the mess? You could easily check this by disabling it.
  • 0 in reply to Biser Gatchev-XID
    Intellectual 830 points

    Ooooh very good hint, this could be easily the root of the problem. We'll check on it immediately and come back with the results!

    At the start of hw assembling we experienced problems with the RFID reading characteristics and the hw guys told that it could be because of the LCD frame... Maybe this is a vice versa problem and we should put something between them.

    Thanks!

  • 0 in reply to sodjas
    Intellectual 830 points

    Update:

    The problem occurred after shutting down the rfid, Android does not crash it seems that the problem is in the SGX part. The only suspicious thing I was able to find in dmesg after this was:

    <6>[174753.832672] PVR_K: User requested SGX debug info
    <6>[174753.837615] PVR_K: SGX debug (blaze_android_sgx_ogles1_ogles2_GPL sgxddk 18 1.8@789263)
    <6>[174753.846069] PVR_K: Flip Command Complete Data 0 for display device 1:
    <6>[174753.852905] PVR_K: SRC 0: ROC DevVAddr:0xD800054 ROP:0x212d0c ROC:0x212d08, WOC DevVAddr:0xD800044 WOP:0x109686 WOC:0x109685
    <6>[174753.864807] PVR_K: SRC 1: ROC DevVAddr:0xD800034 ROP:0x212d0b ROC:0x212d07, WOC DevVAddr:0xD800024 WOP:0x109686 WOC:0x109684
    <6>[174753.876678] PVR_K: Flip Command Complete Data 1 for display device 1:
    <6>[174753.883514] PVR_K: SRC 0: (Not in use)
    <6>[174753.887603] PVR_K: SRC 1: (Not in use)
    <6>[174753.891693] PVR_K: SGX Host control:
    <6>[174753.895507] PVR_K: (HC-0) 0x00000001 0x0000000C 0x00000000 0x00000001
    <6>[174753.902404] PVR_K: (HC-10) 0x00000000 0x00000000 0x0000000A 0x00030D40
    <6>[174753.909423] PVR_K: (HC-20) 0x00000065 0x00000004 0x00000000 0x00000000
    <6>[174753.916442] PVR_K: (HC-30) 0x0000995F 0x04AF4F5B 0x9DA09A40 0x00000000
    <6>[174753.923431] PVR_K: (HC-40) 0x00000000 0x00000000 0x00000000 0x00000000
    <6>[174753.930419] PVR_K: SGX TA/3D control:
    <6>[174753.934356] PVR_K: (T3C-0) 0x0F003000 0x0F003120 0x0F002000 0x00000000
    <6>[174753.941345] PVR_K: (T3C-10) 0x0F0C4300 0x00000001 0x00000002 0x00000001
    <6>[174753.948455] PVR_K: (T3C-20) 0x0F00AE80 0x00000000 0x00000000 0x00000000
    <6>[174753.955535] PVR_K: (T3C-30) 0x00000000 0x00000000 0x00000000 0x00000000
    <6>[174753.962646] PVR_K: (T3C-40) 0x00000000 0x00000000 0x00000000 0x00000000
    <6>[174753.969726] PVR_K: (T3C-50) 0x00000000 0x0F00AE80 0x00000000 0x00000000
    <6>[174753.976837] PVR_K: (T3C-60) 0x0F00AE80 0x00000000 0x00000000 0x0F00AE80
    <6>[174753.983917] PVR_K: (T3C-70) 0x00000000 0x00000000 0x0F00AE80 0x00000000
    <6>[174753.991027] PVR_K: (T3C-80) 0x00000000 0x00000000 0x00000000 0x0F000000
    <6>[174753.998107] PVR_K: (T3C-90) 0x8F246000 0x0F099900 0x00000000 0x0F08B280
    <6>[174754.005249] PVR_K: (T3C-A0) 0x0F00AE80 0x00000000 0x0F08B4A0 0x00000000
    <6>[174754.012329] PVR_K: (T3C-B0) 0x0F0AD500 0x00000000 0x00000000 0x00000000
    <6>[174754.019439] PVR_K: (T3C-C0) 0x00000000 0x00000000 0x00000000 0x00212D0A
    <6>[174754.026519] PVR_K: (T3C-D0) 0x00212D08 0x0F000000 0x8000B000 0x8004B000
    <6>[174754.033630] PVR_K: (T3C-E0) 0x0F004000 0x0F00A420 0x0F00A740 0x00000000
    <6>[174754.040710] PVR_K: (T3C-F0) 0x00000000 0x00000000 0x0000007A 0x0000007A
    <6>[174754.047821] PVR_K: (T3C-100) 0x00000000 0x00000003 0x00000000 0x00000000
    <6>[174754.055023] PVR_K: (T3C-110) 0x00000001 0x00000000 0x00000000 0x00000000
    <6>[174754.062194] PVR_K: SGX Kernel CCB WO:0xCB RO:0xCB

    I do not really know whether this is a debug or error message. The error looked the same as at the video and dissapeard after a few seconds without reboot... No errors in logcat just this message in dmesg.

    best regards,

    sodjas

  • 0 in reply to sodjas
    Intellectual 830 points

    Hi Guys,

    After surfing some time here on the forums this could be an SGX version issue, but I can't determine whether the lib is responsible or an improper hw design pattern such as RFID (which was proven that it not causes this) or other hw component interferes the video display part.

    Probably hw monitoring and verification is needed here, but I would appreciate if anyone could tell me some hints what is this PVR_K stuff responsible for. This piece of debug info posted in there previous reply occurs several times while the anomaly shown on the video is present, and stops immediately after graphics come back.

    Anyone? Pleeeease :)

    best regards,

    sodjas

  • 0 in reply to sodjas
    Intellectual 830 points

    Further Update:

    Unfortunately I was able to reproduce the issue on Chipsee's stock expansion board and Innolux LCD, so I assume that the bug causing this is in the platform itself.

    I realized some more logs which always occur before the anomaly, I'm talking about binder stuff. Could this be some memory issue? Is this familiar to somebody?:

    <6>[168651.817779] binder: 551:560 refcount change on invalid ref 15
    <6>[168651.845153] binder: 551:560 refcount change on invalid ref 17
    <6>[168651.851379] binder: 551:560 refcount change on invalid ref 18
    <6>[168651.858520] binder: 551:560 refcount change on invalid ref 19
    <6>[168651.865539] binder: 551:560 refcount change on invalid ref 20
    <6>[211851.663482] binder: 551:575 refcount change on invalid ref 15
    <6>[211851.669708] binder: 551:575 refcount change on invalid ref 15
    <3>[211851.675811] binder: transaction release 7427 bad handle 15
    <6>[255051.660919] binder: 551:567 refcount change on invalid ref 17
    <6>[255051.667114] binder: 551:567 refcount change on invalid ref 17
    <3>[255051.673217] binder: transaction release 26918 bad handle 17
    <6>[298251.667633] binder: 551:571 refcount change on invalid ref 18
    <6>[298251.673858] binder: 551:571 refcount change on invalid ref 18
    <3>[298251.679931] binder: transaction release 45938 bad handle 18
    <6>[341451.581542] binder: 551:576 refcount change on invalid ref 19
    <6>[341451.587738] binder: 551:576 refcount change on invalid ref 19
    <3>[341451.593841] binder: transaction release 64892 bad handle 19
    <6>[345694.388092] binder: 551:578 refcount change on invalid ref 20
    <6>[345694.394287] binder: 551:578 refcount change on invalid ref 20
    <3>[345694.400360] binder: transaction release 83910 bad handle 20
    <6>[419070.463897] android_work: sent uevent USB_STATE=CONNECTED
    <6>[419070.685729] gadget: high-speed config #1: android
    <6>[419070.691009] android_work: sent uevent USB_STATE=CONFIGURED
    <3>[424926.249114] binder: release proc 1172, transaction 214508, not freed
    <3>[424926.255950] binder: release proc 1172, transaction 214017, not freed
    <3>[424926.262664] binder: release proc 1172, transaction 214044, not freed
    <3>[424926.274139] binder: release proc 1172, transaction 214071, not freed
    <3>[424926.280883] binder: release proc 1172, transaction 214098, not freed
    <3>[424926.287597] binder: release proc 1172, transaction 214125, not freed
    <3>[424926.294342] binder: release proc 1172, transaction 214152, not freed
    <3>[424926.301055] binder: release proc 1172, transaction 214179, not freed
    <3>[424926.307800] binder: release proc 1172, transaction 214206, not freed
    <3>[424926.314544] binder: release proc 1172, transaction 214233, not freed
    <3>[424926.321258] binder: release proc 1172, transaction 214370, not freed
    <3>[437934.011047] init: untracked pid 1188 exited
    <3>[447615.750732] binder: 2180: binder_alloc_buf, no vma
    <6>[447615.755920] binder: 136:252 transaction failed 29201, size 200-0
    <6>[447615.762298] binder: send failed reply for transaction 294555 to 2180:2180
    <3>[499056.758392] init: untracked pid 1761 exited
    <6>[522251.453491] adb_open
    <6>[522251.456420] android_work: sent uevent USB_STATE=DISCONNECTED
    <6>[522251.694580] musb android_usb gadget disconnected.
    <6>[522251.699676] android_work: did not send uevent (0 0 (null))
    <6>[522251.713287] adb_release
    <3>[522251.760559] init: untracked pid 2900 exited
    <3>[522252.760498] init: untracked pid 2397 exited
    <3>[522252.765167] init: untracked pid 2399 exited
    <6>[523461.587310] adb_open
    <6>[523461.702484] android_work: sent uevent USB_STATE=CONNECTED
    <6>[523464.149627] musb android_usb gadget disconnected.
    <6>[523464.154785] android_work: sent uevent USB_STATE=DISCONNECTED
    <6>[523464.165405] adb_release
    <6>[523464.569671] adb_open
    <6>[523464.710815] android_work: sent uevent USB_STATE=CONNECTED
    <6>[523465.034942] android_work: sent uevent USB_STATE=DISCONNECTED
    <6>[523465.158691] android_work: sent uevent USB_STATE=CONNECTED
    <6>[523465.168945] gadget: high-speed config #1: android
    <6>[523465.174377] android_work: sent uevent USB_STATE=CONFIGURED
    <6>[526183.974517] PVR_K: User requested SGX debug info
    <6>[526183.983856] PVR_K: SGX debug (blaze_android_sgx_ogles1_ogles2_GPL sgxddk 18 1.8@789263)
    <6>[526183.992401] PVR_K: Flip Command Complete Data 0 for display device 1:
    <6>[526183.999481] PVR_K: SRC 0: ROC DevVAddr:0xD800054 ROP:0x12049 ROC:0x12048, WOC DevVAddr:0xD800044 WOP:0x9021 WOC:0x9021
    <6>[526184.010864] PVR_K: SRC 1: ROC DevVAddr:0xD800034 ROP:0x12048 ROC:0x12047, WOC DevVAddr:0xD800024 WOP:0x901c WOC:0x901b
    <6>[526184.022216] PVR_K: Flip Command Complete Data 1 for display device 1:
    <6>[526184.029022] PVR_K: SRC 0: (Not in use)
    <6>[526184.033111] PVR_K: SRC 1: (Not in use)
    <6>[526184.037231] PVR_K: SGX Host control:
    <6>[526184.041046] PVR_K: (HC-0) 0x00000001 0x0000000C 0x00000000 0x00000001
    <6>[526184.047973] PVR_K: (HC-10) 0x00000000 0x00000000 0x0000000A 0x00030D40
    <6>[526184.054962] PVR_K: (HC-20) 0x00000065 0x00000004 0x00000000 0x00000000
    <6>[526184.061981] PVR_K: (HC-30) 0x00002793 0x003F54AB 0x6AD23090 0x00000000
    <6>[526184.068969] PVR_K: (HC-40) 0x00000000 0x00000000 0x85A0040E 0x85B0040E
    <6>[526184.075988] PVR_K: SGX TA/3D control:
    <6>[526184.079895] PVR_K: (T3C-0) 0x0F003000 0x0F003120 0x0F002000 0x00000000
    <6>[526184.086914] PVR_K: (T3C-10) 0x0F0E52C0 0x00000001 0x00000002 0x00000001
    <6>[526184.093994] PVR_K: (T3C-20) 0x0F0D0600 0x00000000 0x00000000 0x00000000
    <6>[526184.101074] PVR_K: (T3C-30) 0x00000000 0x00000000 0x00000000 0x00000000
    <6>[526184.108184] PVR_K: (T3C-40) 0x00000000 0x00000000 0x00000000 0x00000000
    <6>[526184.115264] PVR_K: (T3C-50) 0x00000000 0x00000000 0x00000000 0x00000000
    <6>[526184.122375] PVR_K: (T3C-60) 0x00000000 0x00000000 0x00000000 0x0F00AE80
    <6>[526184.129455] PVR_K: (T3C-70) 0x00000000 0x00000000 0x0F00AE80 0x00000000
    <6>[526184.136566] PVR_K: (T3C-80) 0x00000000 0x00000000 0x00000000 0x0F000000
    <6>[526184.143646] PVR_K: (T3C-90) 0x8F2DA000 0x0F0DDD00 0x00000000 0x0F0F3880
    <6>[526184.150756] PVR_K: (T3C-A0) 0x0F0D0600 0x00000000 0x0F0F3880 0x00000000
    <6>[526184.157836] PVR_K: (T3C-B0) 0x0F0AD500 0x00000000 0x00000000 0x00000000
    <6>[526184.164947] PVR_K: (T3C-C0) 0x00000000 0x00000000 0x00000000 0x0000C5A6
    <6>[526184.172027] PVR_K: (T3C-D0) 0x0000C5A6 0x0F000000 0x8000B000 0x8004B000
    <6>[526184.179107] PVR_K: (T3C-E0) 0x0F004000 0x0F00A420 0x0F00A740 0x00000000
    <6>[526184.186218] PVR_K: (T3C-F0) 0x00000000 0x00000000 0x000000EF 0x000000EF
    <6>[526184.193298] PVR_K: (T3C-100) 0x00000000 0x00000003 0x00000001 0x00000000
    <6>[526184.200500] PVR_K: (T3C-110) 0x00000001 0x00000000 0x8460040E 0x8470040E
    <6>[526184.207672] PVR_K: SGX Kernel CCB WO:0x9 RO:0x9
    <6>[526189.214447] PVR_K: User requested SGX debug info
    <6>[526189.219390] PVR_K: SGX debug (blaze_android_sgx_ogles1_ogles2_GPL sgxddk 18 1.8@789263)
    <6>[526189.227844] PVR_K: Flip Command Complete Data 0 for display device 1:
    <6>[526189.234680] PVR_K: SRC 0: ROC DevVAddr:0xD800054 ROP:0x1204a ROC:0x12048, WOC DevVAddr:0xD800044 WOP:0x9022 WOC:0x9021
    <6>[526189.246063] PVR_K: SRC 1: ROC DevVAddr:0xD800034 ROP:0x12049 ROC:0x12047, WOC DevVAddr:0xD800024 WOP:0x901c WOC:0x901b
    <6>[526189.257415] PVR_K: Flip Command Complete Data 1 for display device 1:
    <6>[526189.264221] PVR_K: SRC 0: (Not in use)
    <6>[526189.268310] PVR_K: SRC 1: (Not in use)
    <6>[526189.272430] PVR_K: SGX Host control:
    <6>[526189.276245] PVR_K: (HC-0) 0x00000001 0x0000000C 0x00000000 0x00000001
    <6>[526189.283142] PVR_K: (HC-10) 0x00000000 0x00000000 0x0000000A 0x00030D40
    <6>[526189.290161] PVR_K: (HC-20) 0x00000065 0x00000004 0x00000000 0x00000000
    <6>[526189.297180] PVR_K: (HC-30) 0x00002794 0x003F5513 0x71241440 0x00000000
    <6>[526189.304168] PVR_K: (HC-40) 0x00000000 0x00000000 0x85A0040E 0x85B0040E
    <6>[526189.311157] PVR_K: SGX TA/3D control:
    <6>[526189.315093] PVR_K: (T3C-0) 0x0F003000 0x0F003120 0x0F002000 0x00000000
    <6>[526189.322082] PVR_K: (T3C-10) 0x0F0E52C0 0x00000001 0x00000002 0x00000001
    <6>[526189.329193] PVR_K: (T3C-20) 0x0F0D0600 0x00000000 0x00000000 0x00000000
    <6>[526189.336273] PVR_K: (T3C-30) 0x00000000 0x00000000 0x00000000 0x00000000
    <6>[526189.343383] PVR_K: (T3C-40) 0x00000000 0x00000000 0x00000000 0x00000000
    <6>[526189.350463] PVR_K: (T3C-50) 0x00000000 0x0F0D0600 0x00000000 0x00000000
    <6>[526189.357574] PVR_K: (T3C-60) 0x0F0D0600 0x00000000 0x00000000 0x0F00AE80
    <6>[526189.364685] PVR_K: (T3C-70) 0x00000000 0x00000000 0x0F00AE80 0x00000000
    <6>[526189.371765] PVR_K: (T3C-80) 0x00000000 0x00000000 0x00000000 0x0F000000
    <6>[526189.378845] PVR_K: (T3C-90) 0x8F2DA000 0x0F091A00 0x00000000 0x0F08B280
    <6>[526189.385955] PVR_K: (T3C-A0) 0x0F00AE80 0x00000000 0x0F0F3880 0x00000000
    <6>[526189.393035] PVR_K: (T3C-B0) 0x0F0AD500 0x00000000 0x00000000 0x00000000
    <6>[526189.400146] PVR_K: (T3C-C0) 0x00000000 0x00000000 0x00000000 0x0001203D
    <6>[526189.407226] PVR_K: (T3C-D0) 0x0000C5A6 0x0F000000 0x8000B000 0x8004B000
    <6>[526189.414337] PVR_K: (T3C-E0) 0x0F004000 0x0F00A420 0x0F00A740 0x00000000
    <6>[526189.421539] PVR_K: (T3C-F0) 0x00000000 0x00000000 0x00000080 0x000000EF
    <6>[526189.428649] PVR_K: (T3C-100) 0x00000000 0x00000003 0x00000000 0x00000000
    <6>[526189.435821] PVR_K: (T3C-110) 0x00000001 0x00000000 0x8460040E 0x8470040E
    <6>[526189.442993] PVR_K: SGX Kernel CCB WO:0xF RO:0xF
    <6>[526194.454467] PVR_K: User requested SGX debug info
    <6>[526194.459411] PVR_K: SGX debug (blaze_android_sgx_ogles1_ogles2_GPL sgxddk 18 1.8@789263)
    <6>[526194.467895] PVR_K: Flip Command Complete Data 0 for display device 1:
    <6>[526194.474731] PVR_K: SRC 0: ROC DevVAddr:0xD800054 ROP:0x1204b ROC:0x12048, WOC DevVAddr:0xD800044 WOP:0x9022 WOC:0x9021
    <6>[526194.486083] PVR_K: SRC 1: ROC DevVAddr:0xD800034 ROP:0x1204a ROC:0x12047, WOC DevVAddr:0xD800024 WOP:0x901d WOC:0x901b
    <6>[526194.497467] PVR_K: Flip Command Complete Data 1 for display device 1:
    <6>[526194.504272] PVR_K: SRC 0: (Not in use)
    <6>[526194.508361] PVR_K: SRC 1: (Not in use)
    <6>[526194.512451] PVR_K: SGX Host control:
    <6>[526194.516296] PVR_K: (HC-0) 0x00000001 0x0000000C 0x00000000 0x00000001
    <6>[526194.523193] PVR_K: (HC-10) 0x00000000 0x00000000 0x0000000A 0x00030D40
    <6>[526194.530212] PVR_K: (HC-20) 0x00000065 0x00000004 0x00000000 0x00000000
    <6>[526194.537231] PVR_K: (HC-30) 0x00002795 0x003F557B 0x71743010 0x00000000
    <6>[526194.544219] PVR_K: (HC-40) 0x00000000 0x00000000 0x85A0040E 0x85B0040E
    <6>[526194.551208] PVR_K: SGX TA/3D control:
    <6>[526194.555145] PVR_K: (T3C-0) 0x0F003000 0x0F003120 0x0F002000 0x00000000
    <6>[526194.562164] PVR_K: (T3C-10) 0x0F0E52C0 0x00000001 0x00000002 0x00000001
    <6>[526194.569244] PVR_K: (T3C-20) 0x0F0D0600 0x00000000 0x00000000 0x00000000
    <6>[526194.576354] PVR_K: (T3C-30) 0x00000000 0x00000000 0x00000000 0x00000000
    <6>[526194.583435] PVR_K: (T3C-40) 0x00000000 0x00000000 0x00000000 0x00000000
    <6>[526194.590515] PVR_K: (T3C-50) 0x00000000 0x0F0D0600 0x00000000 0x00000000
    <6>[526194.597625] PVR_K: (T3C-60) 0x0F00AE80 0x00000000 0x00000000 0x0F00AE80
    <6>[526194.604705] PVR_K: (T3C-70) 0x00000000 0x00000000 0x0F00AE80 0x00000000
    <6>[526194.611816] PVR_K: (T3C-80) 0x00000000 0x00000000 0x00000000 0x0F000000
    <6>[526194.618896] PVR_K: (T3C-90) 0x8F2DA000 0x0F091A00 0x00000000 0x0F08B280
    <6>[526194.626007] PVR_K: (T3C-A0) 0x0F00AE80 0x00000000 0x0F0F3880 0x00000000
    <6>[526194.633087] PVR_K: (T3C-B0) 0x0F0AD500 0x00000000 0x00000000 0x00000000
    <6>[526194.640197] PVR_K: (T3C-C0) 0x00000000 0x00000000 0x00000000 0x0001203D
    <6>[526194.647277] PVR_K: (T3C-D0) 0x0000C5A6 0x0F000000 0x8000B000 0x8004B000
    <6>[526194.654388] PVR_K: (T3C-E0) 0x0F004000 0x0F00A420 0x0F00A740 0x00000000
    <6>[526194.661468] PVR_K: (T3C-F0) 0x00000000 0x00000000 0x00000080 0x000000EF
    <6>[526194.668579] PVR_K: (T3C-100) 0x00000000 0x00000003 0x00000000 0x00000000
    <6>[526194.675750] PVR_K: (T3C-110) 0x00000001 0x00000000 0x8460040E 0x8470040E
    <6>[526194.682922] PVR_K: SGX Kernel CCB WO:0x16 RO:0x16
    <6>[526209.746093] binder: release 212:212 transaction 766507 out, still active
    <6>[526282.280792] binder: 128:133 transaction failed 29189, size 8-0
    <6>[526282.287078] binder: send failed reply for transaction 766507, target dead

    best regards,

    sodjas

  • 0 in reply to sodjas
    TI__Intellectual 1505 points

    The Solution to this issue has been posted in the following thread -

    http://e2e.ti.com/support/embedded/android/f/509/p/244560/856003.aspx#856003

    -Aditya

     Kindly click the verify answer button on this post if it answer your question.

  • 0 in reply to Aditya Nellutla
    Intellectual 565 points
    These links are now dead , how to access patch ?