Humm let me post the outcomes I got so far. For some reason the I2C channel gets lots of "noisy" when SOME monitors are connected to it. We believe that some monitors have a protocol (Enhanced Display Data Channel) that introduces this noisy into the IC that is in charge of linking the MX53 and the VGA, which includes the I2C channel.
Using other monitors it works fine. Maybe it's a hardware design issue. On Monday, November 5, 2012 10:15:42 AM UTC-2, Rafael Coutinho wrote: > > Hey Alan, > > thanks for your inputs. I'm trying here to identify this issue. I found > the i2ctools but i was working on the migration to android, so this package > you sent me is of great help. > > We are working on a board based on the imx53 but with our own project. > Will let you know about the progress. > > Thanks again. > > On Saturday, November 3, 2012 2:42:11 PM UTC-2, ACASSIS wrote: >> >> Hi Rafael, >> >> There are many possible causes for this issue: >> >> 1) I2C pin mux wrong; >> 2) SGTL5000 damage; >> 3) SGTL5000 in a different channel than this you are trying to >> communicate; >> 4) Another chip on I2C is disturbing the communication, etc. >> >> In my case the problem was caused by other chip on same bus blocking >> the communication with SGTL5000. This other chip was a TLV320AIC3110, >> we used 2 audio codecs: SGTL5000 for main processor audio and >> TLV320AIC3110 for baseband audio. >> >> The solution was easy, we just initialized TLV320AIC3110 first and >> then enable SGTL5000. >> >> I suggest you to use i2ctools to scan the i2c bus to help you to find >> out what is wrong. >> >> Please find attached the i2ctools modified to use android makefiles. >> >> Best Regards, >> >> Alan >> >> P.S.: Rafael, você está tentando rodar o Android numa placa de >> avaliação da Freescale ou numa placa desenvolvida por vocês? >> >> On 10/31/12, Rafael Coutinho <[email protected]> wrote: >> > Hi Alan, >> > >> > I'm having the same issue with imx53. So now i'm investigating if the >> i2c >> > channels is correctly pointing to SGTL5000. Do you have any suggestions >> of >> > tools to make this configuration or check the conf of the io mux pins? >> > >> > >> > On Friday, October 1, 2010 7:26:59 AM UTC-3, ACASSIS wrote: >> >> >> >> Hi Vinay, >> >> >> >> On 10/1/10, Vinay <[email protected] <javascript:>> wrote: >> >> > Hi All, >> >> > >> >> > I'm trying to port android to iMx51. The boot process hangs at the >> >> > splash screen. A portion of the log is here as below. Kindly let me >> >> > know if any of have any idea about what is going wrong.. Thanks for >> >> > all suggestions.. >> >> > >> >> > A portion of log files: >> >> > >> >> > (Initial some lines skipped) >> >> > >> >> > android init >> >> > android_probe pdata: c044d0dc >> >> > android_bind >> >> > mass_storage_function_add >> >> > android_usb gadget: Number of LUNs=3 >> >> > adb_function_add >> >> > android_usb gadget: android_usb ready >> >> > Suspend udc for OTG auto detect >> >> > udc run >> >> > USB Gadget resumed >> >> > fsl-usb2-udc: bind to driver android_usb >> >> > input: mxc_ts as /devices/virtual/input/input1 >> >> > mxc input touchscreen loaded >> >> > pmic_rtc pmic_rtc.1: setting system clock to 1970-01-02 14:05:31 UTC >> >> > (137131) >> >> > Freeing init memory: 152K >> >> > usb 1-1.2: configuration #1 chosen from 1 choice >> >> > input: Dell Dell USB Keyboard as /devices/platform/fsl-ehci.0/ >> >> > usb1/1-1/1-1.2/1-1.2:1.0/input/input2 >> >> > generic-usb 0003:413C:2003.0001: input: USB HID v1.10 Keyboard [Dell >> >> > Dell USB Keyboard] on usb-fsl-ehci.0-1.2/input0 >> >> > init: cannot open '/initlogo.rle' >> >> > kjournald starting. Commit interval 5 seconds >> >> > EXT3 FS on mmcblk0p2, internal journal >> >> > EXT3-fs: mounted filesystem with ordered data mode. >> >> > EXT3-fs warning: maximal mount count reached, running e2fsck is >> >> > recommended >> >> > kjournald starting. Commit interval 5 seconds >> >> > EXT3 FS on mmcblk0p5, internal journal >> >> > EXT3-fs: recovery complete. >> >> > EXT3-fs: mounted filesystem with ordered data mode. >> >> > kjournald starting. Commit interval 5 seconds >> >> > EXT3-fs warning: maximal mount count reached, running e2fsck is >> >> > recommended >> >> > EXT3 FS on mmcblk0p6, internal journal >> >> > EXT3-fs: recovery complete. >> >> > EXT3-fs: mounted filesystem with ordered data mode. >> >> > init: cannot find '/system/etc/install-recovery.sh', disabling >> >> > 'flash_recovery' >> >> > enabling adb >> >> > adb_open >> >> > # gpu_z430: module license 'Proprietary' taints kernel. >> >> > warning: `rild' uses 32-bit capabilities (legacy support in use) >> >> > usb 1-1.6: new high speed USB device using fsl-ehci and address 4 >> >> > usb 1-1.6: configuration #1 chosen from 1 choice >> >> > scsi0 : SCSI emulation for USB Mass Storage devices >> >> > scsi 0:0:0:0: Direct-Access USB TO I DE/SATA Device 0041 PQ: 0 >> >> > ANSI: 0 >> >> > FAT: unable to read boot sector >> >> > sd 0:0:0:0: [sda] Attached SCSI disk >> >> > pmem: request for physical address of pmem region from process 1994. >> >> > Not all allocated memory blocks were freed. Doing it now. >> >> > Freeing list entry #0 >> >> > Freeing list entry #1 >> >> > Freeing list entry #2 >> >> > Freeing list entry #3 >> >> > Freeing list entry #4 >> >> > Freeing list entry #7 >> >> > Freeing list entry #8 >> >> > Freeing list entry #9 >> >> > Freeing list entry #147 >> >> > request_suspend_state: wakeup (3->0) at 64064825004 (1970-01-02 >> >> > 14:06:32.281579093 UTC) >> >> > i2c-adapter i2c-1: Data not transmitted >> >> > sgtl5000_hw_read: read reg error : Reg 0x0e >> >> > i2c-adapter i2c-1: Data not transmitted >> >> > sgtl5000_write: write reg error : Reg 0x0e = 0x000c >> >> > i2c-adapter i2c-1: Data not transmitted >> >> > sgtl5000_write: write reg error : Reg 0x02 = 0x0020 >> >> > i2c-adapter i2c-1: Data not transmitted >> >> > sgtl5000_write: write reg error : Reg 0x06 = 0x0130 >> >> >> >> Look here, your audio codec chip was not detected correctly. >> >> >> >> Android will not start up until you fix the audio chip and get it >> >> working. >> >> >> >> We also realized the same issue in our iMX51 board, just fix audio and >> >> Android will go on. >> >> >> >> > init: untracked pid 1946 exited >> >> > pmem: request for physical address of pmem region from process 2045. >> >> > binder: release proc 2039, transaction 648, not freed >> >> > Not all allocated memory blocks were freed. Doing it now. >> >> > Freeing list entry #0 >> >> > Freeing list entry #1 >> >> > Freeing list entry #2 >> >> > Freeing list entry #3 >> >> > Freeing list entry #4 >> >> > Freeing list entry #7 >> >> > Freeing list entry #8 >> >> > Freeing list entry #9 >> >> > request_suspend_state: wakeup (0->0) at 73082715878 (1970-01-02 >> >> > 14:06:41.299472092 UTC) >> >> > i2c-adapter i2c-1: Data not transmitted >> >> > sgtl5000_hw_read: read reg error : Reg 0x0e >> >> > i2c-adapter i2c-1: Data not transmitted >> >> > sgtl5000_write: write reg error : Reg 0x0e = 0x000c >> >> > i2c-adapter i2c-1: Data not transmitted >> >> > sgtl5000_write: write reg error : Reg 0x02 = 0x0020 >> >> > i2c-adapter i2c-1: Data not transmitted >> >> > Freeing list entry #62 >> >> > sgtl5000_write: write reg error : Reg 0x06 = 0x0130 >> >> > init: untracked pid 2033 exited >> >> > pmem: request for physical address of pmem region from process 2096. >> >> > Not all allocated memory blocks were freed. Doing it now. >> >> > Freeing list entry #0 >> >> > Freeing list entry #1 >> >> > Freeing list entry #2 >> >> > Freeing list entry #3 >> >> > Freeing list entry #4 >> >> > Freeing list entry #7 >> >> > Freeing list entry #8 >> >> > Freeing list entry #9 >> >> > Freeing list entry #50 >> >> > (This repeats…………..) The spalsh screen blinks and boot does not >> >> > proceed. >> >> >> >> I think you can see it trying to communicate with SGTL5000 over I2C-1 >> >> bus, make sure your audio codec is really on I2C-1 bus. Otherwise >> >> change the config to right bus. >> >> >> >> Best Regards, >> >> >> >> Alan >> >> >> >> >> > >> > -- >> > unsubscribe: [email protected] >> > website: http://groups.google.com/group/android-porting >> > >> > -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
