DS90UB948-Q1: When customer accessing DS90UB948 remotely through DS90UB947, the lock will become low and the screen will go black.

Jon,

Can you please share more detail here so we can help provide debug advice? Do you have schematics for both sides to share? What kind of cable connection are you using here? Do you have pictures of the setup?

Best Regards,

Casey 

Casey,

   Customer init the Ds90uB947+Ds90UB948  as below. And the lcd can dispaly normal, Customer dump the Ds90UB947's reg is ok .  But when customer  accessing DS90uB948 or TouchPanel address remotely through Ds9oUB947,the lock will become low and the screen will go black, Customer dump the Ds90UB947's as picture0 .They try to i2c tools  dump the regs through  Ds90UB948's  I2c Pin, and it can be dump as picture1 ,and it not go black .

TI947
0xc  0x1  0x3
0xc  0x3  0x5e
0xc  0x6  0x58
0xc  0x7  0xba
0xc  0x8  0xba
0xc  0x1e  0x5
0xc  0xd  0x3
0xc  0xe  0x33
0xc  0xf  0x3
0xc  0x1e  0x7
0xc  0xe  0x33
0xc  0xf  0x3
0xc  0x17  0x8e
0xc  0x4f  0x80
0xc  0x51  0xa0

TI948
0x2c 0x1  0x7
0x2c 0x3  0xfa
0x2c 0x5  0xe
0x2c 0x7  0x18
0x2c 0x28  0x14
0x2c 0x34  0x41
0x2c 0x49  0xe2
0x2c 0x1d  0x5
0x2c 0x1e  0x55
0x2c 0x1f  0x5
0x2c 0x34  0x43
0x2c 0x1e  0x55
0x2c 0x1f  0x5
0x2c 0x1f  0x5
0x2c 0x20  0x9

2133.pdf5756.pdf

Hello Jon,

If communication to the 948 through the 947 is not working, then how are the settings for 948 above being programmed? Is there a local MCU attached to the 948 which is configuring the 948?

I see a few issues:

- Customer is disabling the I2C SDA hold time which is not recommended. Suggest to change the following commands:

0xc  0x17  0x8e -> 0xc  0x17  0x9e

0x2c 0x5  0xe -> 0x2c 0x5  0x1e

- BC CRC is being disabled which is not recommended - change the below:

0xc  0x3  0x5e -> 0xc  0x3  0xda

- The customer is writing to 0x51 on the 947 which is a reserved command. remove the following:

0xc  0x51  0xa0 -> Delete 

- The datapath controls are being overridden in the 948 which should be just auto-detected. Suggest to remove:

0x2c 0x28  0x14 -> Delete 

- If the desire is to reset the part with registers, then you only need to program 0x01 bit 1, not both bit 1 and bit 0. Suggest the following changes:

0xc  0x1  0x3 -> 0xc  0x1  0x2

0x2c 0x1  0x7 -> 0x2c 0x1  0x6

- Lastly, I don't know why the secondary I2C address is being enabled in register 0x1E of the 947 (bit 2). It seems like they are not utilizing the secondary address anywhere in the init script. Instead, since they are just accessing the SER through address 0x0C for everything, then I would suggest to set PORT1_I2C_EN = 0

0xc  0x1e  0x1 -> Access Port 0 Registers 

0xc  0x1e  0x2 -> Access Port 1 Registers 

Best Regards,

Casey 

Casey,

Customer had followed your suggest to change  the  commands.But when customer  accessing DS90uB948 or TouchPanel address remotely through Ds9oUB947,the lock will become low and the screen will go black too.

DEBUG: bridge_probe: Enter !
DEBUG: bridge_i2c_write: addr:0xc reg:0x1 val:0x2
DEBUG: bridge_i2c_write: addr:0xc reg:0x3 val:0xda
DEBUG: bridge_i2c_write: addr:0xc reg:0x6 val:0x58
DEBUG: bridge_i2c_write: addr:0xc reg:0x7 val:0xba
DEBUG: bridge_i2c_write: addr:0xc reg:0x8 val:0xba
DEBUG: bridge_i2c_write: addr:0xc reg:0x1e val:0x5
DEBUG: bridge_i2c_write: addr:0xc reg:0xd val:0x3
DEBUG: bridge_i2c_write: addr:0xc reg:0xe val:0x33
DEBUG: bridge_i2c_write: addr:0xc reg:0xf val:0x3
DEBUG: bridge_i2c_write: addr:0xc reg:0x1e val:0x1
DEBUG: bridge_i2c_write: addr:0xc reg:0xe val:0x33
DEBUG: bridge_i2c_write: addr:0xc reg:0xf val:0x3
DEBUG: bridge_i2c_write: addr:0xc reg:0x17 val:0x9e
DEBUG: bridge_i2c_write: addr:0xc reg:0x4f val:0x80
DEBUG: bridge_i2c_write: addr:0x2c reg:0x1 val:0x6
DEBUG: bridge_i2c_write: addr:0x2c reg:0x3 val:0xfa
DEBUG: bridge_i2c_write: addr:0x2c reg:0x5 val:0x1e
DEBUG: bridge_i2c_write: addr:0x2c reg:0x7 val:0x18
DEBUG: bridge_i2c_write: addr:0x2c reg:0x34 val:0x41
DEBUG: bridge_i2c_write: addr:0x2c reg:0x49 val:0xe2
DEBUG: bridge_i2c_write: addr:0x2c reg:0x1d val:0x5
DEBUG: bridge_i2c_write: addr:0x2c reg:0x1e val:0x55
DEBUG: bridge_i2c_write: addr:0x2c reg:0x1f val:0x5
DEBUG: bridge_i2c_write: addr:0x2c reg:0x34 val:0x43
DEBUG: bridge_i2c_write: addr:0x2c reg:0x1e val:0x55
DEBUG: bridge_i2c_write: addr:0x2c reg:0x1f val:0x5
DEBUG: bridge_i2c_write: addr:0x2c reg:0x1f val:0x5
DEBUG: bridge_i2c_write: addr:0x2c reg:0x20 val:0x9

Could you pls help?Thanks.

Jon,

The issue description sounds quite strange and I’m not sure what could cause the behavior you are describing. Can you please share a picture of the total setup as well as pictures of the top side markings of the 947 and 948? 

Best Regards,

Casey

Casey,

       fyi

Jon,

I am not sure what you are trying to show here. Can you please respond to my previous inquiry?

Casey McCrea said:

Can you please share a picture of the total setup as well as pictures of the top side markings of the 947 and 948? 

Best Regards,

Casey