CDCI6214: TDA4VM

xi xiao

Prodigy 150 points

Part Number: CDCI6214
Other Parts Discussed in Thread: , CDCE6214, USB2ANY

Tool/software:

Hi expert,

Hardware platform:J721EXSOMG01EVM + J721EXCP01EVM

Software:ti-processor-sdk-linux-adas-j721e-evm-09_02_00_05

1. The hardware schematic show EEPROMSEL pin pullup to high, as CDCI6214 manual document show the address should be 0x77, but can't find 0x77(find 0x76), why 0x76?

2. what should I do to generate 156.25MHz at Y3?

Are arrows 1 and 2 pointing to the same address?

Can I use i2c-tool to read the register 0x18?

Thanks a lot.
Best Regards!

over 1 year ago

0 Kadeem Samuel over 1 year ago

TI__Mastermind 22140 points

Xi,

We do not recommend the CDCI6214 for new applications, we instead recommend the CDCE6214.

For the I2C address, this appears to be a typo. These tables show that the I2C address bit (bit 7 of the EEPROM words, bit 15 of the registers) is 0 in the EEPROM on both pages:

From the default configuration, changing pll_psfb to /5 (01b), changing pll_ndiv to 10, and the ch3_iod_div value to 4 results in 156.25MHz outputs:

Your arrows are pointing to the same memory space.

The Revision ID register is a readable register using I2C.

Thanks,
Kadeem

0 xi xiao over 1 year ago in reply to Kadeem Samuel

Prodigy 150 points

Hi Kadeem,
Thanks for your reply.

1. What you mean is no matter EEPROMSEL pin pull up or pull down, the device‘s(CDCI6214) address is 0x76, then how to choose page0 or page1?
2. Are these configurations achieved by i2c write? If use TICS Pro tool, how to write these configs into CDCI6214 on J721EXCP01EVM?

Kadeem Samuel said:
From the default configuration, changing pll_psfb to /5 (01b), changing pll_ndiv to 10, and the ch3_iod_div value to 4 results in 156.25MHz outputs:

3. Can you give an example? Such as 'i2cget -y -f 1 0x76 0x18 w', is this command right?

Kadeem Samuel said:
The Revision ID register is a readable register using I2C.

4. In the EEPROM Direct Access flow, is EEPROMSEL pin have to be floating (target address is 0x74)?

5. Arrow 1 address content is 32bits, arrow 2 address content is 16bits, I'm confused that it's the same memory space.
Arrow 2 address range from 0x0 to 0x3f, arrow 1 address range from 0x0-0x46, why arrow 2 address just 0x3f?

Kadeem Samuel said:
Your arrows are pointing to the same memory space.

Thanks a lot.

0 xi xiao over 1 year ago in reply to Kadeem Samuel

Prodigy 150 points

Hi Kadeem,

Help, please.
Thanks!

0 xi xiao over 1 year ago in reply to Kadeem Samuel

Prodigy 150 points

HI,

One more question: how to generate .hxt file with Tics pro software for the CDCI6214, don't have CDCI6214EVM.

Thanks!

0 vicente flores prado over 1 year ago in reply to xi xiao

TI__Mastermind 28802 points

Hi Xi,
Kadeem is currently OoO so I will assist you.

xi xiao said:
1. What you mean is no matter EEPROMSEL pin pull up or pull down, the device‘s(CDCI6214) address is 0x76, then how to choose page0 or page1?

To chose page0 or 1 refer to the following snippet - it also includes the corresponding I2C address:

xi xiao said:
2. Are these configurations achieved by i2c write? If use TICS Pro tool, how to write these configs into CDCI6214 on J721EXCP01EVM?

I looked up the documentation & found the following - looks like the J721E SoC can figure the device via I2C.

xi xiao said:
3. Can you give an example? Such as 'i2cget -y -f 1 0x76 0x18 w', is this command right?

We do not help with programming/drivers - as Kadeem mentioned we have TICSpro which is the GUI we use for our clock generator EVMs.

The revision ID is found in R24[7:0] thus you will need to read this register back using the controller.
For help regarding the syntax of the the SoC please reach out to that team.

xi xiao said:
4. In the EEPROM Direct Access flow, is EEPROMSEL pin have to be floating (target address is 0x74)?

That is correct.

Arrow 1 is just listing each register and the the corresponding register default values.

Arrow two is providing the register name and descriptions.

So effectively yes they're pointing to the same thing but arrow one just gives you the register and its default contents where as in arrow two you have descriptions.

Regards,

Vicente

0 xi xiao over 1 year ago in reply to vicente flores prado

Prodigy 150 points

Hi Vicente,
Thanks a lot for your reply.

1. How to generate .hxt file with TICS Pro software for the CDCI6214, don't have CDCI6214EVM board.
2. Want to confirm again: no matter in the Register Commit flow or in the EEPROM Direct Access flow, the target address has to be 0x74? Is target address 0x76(0x77) also works?

Best Regards!

0 vicente flores prado over 1 year ago in reply to xi xiao

TI__Mastermind 28802 points

Hi Xi,

You only need TICSpro GUI to generate the .hxt file - you do not require the EVM.
according to the documentation for the reference design you’re using the I2C address for CDCI6214 should be 0x76:

0 xi xiao over 1 year ago in reply to vicente flores prado

Prodigy 150 points

Hi Vicente,

Thanks a lot for your reply.

More questions to ask:

1. Can you show how to generate .hxt file with TICS Pro software, follow 'File --> Save' can only have .tcs file, how to have .hxt file?

2. So I can use target address 0x76 to do EEPROM Direct Access flow, the CDCI6214 doesn't have to be 0x74 to do this?

3. As this thread show "Note that it lacks one procedure at the end. You need to relock the EEPROM to 0x0 after programming."
Is this have to be done?(+) CDCI6214: CDCI6214's waveform is is extremely unstable. - Clock & timing forum - Clock & timing - TI E2E support forums

4. I download a .hxt file from the Forums, then flow the EEPROM Direct Access flow with target address 0x76, after programming relock the EEPROM to 0x0.

Then repower, Y0 has 25MHz, but Y1-Y4 have no output. Can you tell what's wrong?

.hxt file as follow show:

----- CDCI6214 EEPROM HEX TEXT FILE ------
Header Info	Thu Sep 07 16:15:59 2023
nvmbusy	0x0000
nvmcrcerr	0x0001
nvm_wr_error	0x0000
nvm_rd_error	0x0000
nvmlcrc	0x6e86
nvmscrc	0x0000
nvm_rd_addr	0x0000
nvm_rd_data	0xee02
nvm_wr_addr	0x003f
nvm_wr_data	0x6e86

----- BASE   PAGE   ------
00	0xee02	60930
01	0x490f	18703
02	0x0362	866
03	0x0e00	3584
04	0x1400	5120
05	0x4104	16644
06	0x0c20	3104
07	0x5000	20480
08	0x0825	2085
09	0x8421	33825
10	0x0006	6
11	0x0000	0

----- CONFIG PAGE 0 ------
12	0x6500	25856
13	0x5369	21353
14	0xaa80	43648
15	0x4382	17282
16	0x1001	4097
17	0x0028	40
18	0xf501	62721
19	0x79cb	31179
20	0x8000	32768
21	0x0800	2048
22	0x0a00	2560
23	0x2904	10500
24	0x0002	2
25	0x2002	8194
26	0x2800	10240
27	0xa410	42000
28	0x0008	8
29	0x8008	32776
30	0xa000	40960
31	0x1044	4164
32	0x0033	51
33	0x0020	32
34	0x8002	32770
35	0x4102	16642
36	0x3fca	16330
37	0x0000	0

----- CONFIG PAGE 1 ------
38	0x6500	25856
39	0x5369	21353
40	0xaa80	43648
41	0x4382	17282
42	0x1001	4097
43	0x0028	40
44	0xf501	62721
45	0x79cb	31179
46	0x8000	32768
47	0x0800	2048
48	0x0a00	2560
49	0x2904	10500
50	0x0002	2
51	0x2002	8194
52	0x2800	10240
53	0xa410	42000
54	0x0008	8
55	0x8008	32776
56	0xa000	40960
57	0x1044	4164
58	0x0033	51
59	0x0020	32
60	0x8002	32770
61	0x4102	16642
62	0x3fca	16330
63	0x6e86	28294
----- END EEPROM HEX TEXT FILE ------

eeprom read as follow show:

root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0f r2
0xa0 0x37
root@j7-evm:~# i2ctransfer -y 3 w4@0x76 0x00 0x0b 0x00 0x00
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0xee 0x02
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x49 0x0f
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x03 0x62
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x0e 0x00
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x14 0x00
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x41 0x04
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x0c 0x20
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x50 0x00
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x08 0x25
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x84 0x21
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x00 0x06
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x00 0x00
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x65 0x00
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x53 0x69
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0xaa 0x80
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x43 0x82
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x10 0x01
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x00 0x28
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0xf5 0x01
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x79 0xcb
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x80 0x00
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x08 0x00
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x0a 0x00
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x29 0x04
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x00 0x02
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x20 0x02
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x28 0x00
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0xa4 0x10
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x00 0x08
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x80 0x08
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0xa0 0x00
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x10 0x44
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x00 0x33
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x00 0x20
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x80 0x02
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x41 0x02
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x3f 0xca
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x00 0x00
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x65 0x00
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x53 0x69
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0xaa 0x80
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x43 0x82
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x10 0x01
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x00 0x28
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0xf5 0x01
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x79 0xcb
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x80 0x00
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x08 0x00
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x0a 0x00
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x29 0x04
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x00 0x02
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x20 0x02
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x28 0x00
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0xa4 0x10
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x00 0x08
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x80 0x08
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0xa0 0x00
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x10 0x44
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x00 0x33
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x00 0x20
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x80 0x02
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x41 0x02
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x3f 0xca
root@j7-evm:~# i2ctransfer -y 3 w2@0x76 0x00 0x0c r2
0x6e 0x86

Thanks!

0 vicente flores prado over 1 year ago in reply to xi xiao

TI__Mastermind 28802 points

Hi Xi,
What is the third output frequency and it's type?
I see from the schematic OU1/2/4 are all 100MHz HCSL?

I will generate the EEPROM file for you but I want to know which outputs and what output formats you require exactly.

Also let me know what you input is and format.

As Kadeem mentioned - we do not recommend CDCI6214 for new designs. We recommend CDCE6214 which is p2p.

Regards,

Vicente

0 xi xiao over 1 year ago in reply to vicente flores prado

Prodigy 150 points

Hi Vicente,

We've already used several CDCI6214 on ourselves designed board, so have to know how to have different configs and how to generate .hxt file.

I would really appreciate it if you could show me the details about how to use TICS Pro software to generate a .hxt file.

vicente flores prado said:
I will generate the EEPROM file for you but I want to know which outputs and what output formats you require exactly.

Also let me know what you input is and format.

1. The input is 25MHz crystal, Y1/2/4 are all need to be 100MHz HCSL, Y3 is need to be 156.25MHz LVDS.

Our board schematic is:

2. Could you please also post the EEPROM file of U17/U22 on J721ECPB and U4 on quad-port ethernet expansion board?(three .hxt files)

Thanks a million.
Waiting for your reply!

0 xi xiao over 1 year ago in reply to vicente flores prado

Prodigy 150 points

Hi Vicente,

Help,please.

Thanks a million.

0 vicente flores prado over 1 year ago in reply to xi xiao

TI__Mastermind 28802 points

Hi Xi,

I Can generate the hex file for question one

I don’t follow your frequency plan requirements for question 2 - can you please elaborate?

Regards,

Vicente

0 vicente flores prado over 1 year ago in reply to vicente flores prado

TI__Mastermind 28802 points

Hi Xi,
Attached you will find the EEPROM file.
To load the EEPROM file Do the following
1. Load the CDCI6214 device profile and navigate to the EEPROM tab: :

2. Press the Select file to write button

3. Choose which EEPROM page you wish to write

4. Press "write to EEPROM button"

Regards,

Vicente

https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/48/CDCI6214_5F00_EEPROM.hxt

0 xi xiao over 1 year ago in reply to vicente flores prado

Prodigy 150 points

Hi Vicente,
The attached CDCI6214_EEPROM.hxt is not right, all EEPROM's datas are zero.

We don't have a CDCI6214 EVM board, don't have a USB2ANY tool, and we have to write EEPROM's datas to ourselves designed board.
So what I want to ask is: if we a .tcs file, can we changed it to .hxt file with TICS Pro software?

Thanks a million.

Beat Regards!

0 vicente flores prado over 1 year ago in reply to xi xiao

TI__Mastermind 28802 points

Hi Xi,
That's def odd - I too see your point the EEPROM file I attached is full of just zeroes - I believe the EVM needs to be connected but I will not be able to verify this till next week.
But yes you can create the .tcs file yourselves and then save the EEPROM file via TICS.

Regards,

Vicente

0 xi xiao over 1 year ago in reply to vicente flores prado

Prodigy 150 points

Hi Vicente,

vicente flores prado said:
But yes you can create the .tcs file yourselves and then save the EEPROM file via TICS.

How to do? I've tried " Read EEPROM to file", since we don't have a CDCI6214EVM and USB2ANY, the file is same as you attached, all zeroes.

Please help to check out whether it's possible to get actual right .hxt file without EVM.

Thanks a million.

Best Regards!

0 Kadeem Samuel over 1 year ago in reply to xi xiao

TI__Mastermind 22140 points

All,

An EVM is required for generating the .hxt file, otherwise the result will be entirely zeroes. This is because the file actually reads the contents from the EEPROM of the connected device. The settings must be loaded onto a connected device, the EEPROM programmed, and the contents read back after a power cycle.

I will check on this and respond by tomorrow with the .hxt file.

Thanks,
Kadeem

0 xi xiao over 1 year ago in reply to Kadeem Samuel

Prodigy 150 points

Hi Kadeem,

Thanks a lot for your reply.

I really need your help to solve the problem that Y0 has no output.

I configured ref_mux=0h, ref_mux_src=0h, ip_byp_mux=0h, ip_byp_en_y0=1h, ch0_lvcoms_drv=1h, REFDEL pin pull down, and confirmed that 25MHz crystal oscillator works.

I read that the value of register 0x07 is 0x0424, it shows that the pll is unlocked and calibration is not done.

What else may i check to figure out why Y0 is no output.

Best Regards!

0 Kadeem Samuel over 1 year ago in reply to xi xiao

TI__Mastermind 22140 points

Xi,

Please refer to the below two files for the .tcs and .hxt for this configuration. In both of these, Y0 is active.

Xi_Xiao_6_25_24_Configuration.tcs

https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/48/Xi_5F00_Xiao_5F00_6_5F00_25_5F00_24_5F00_Configuration.hxt
Please let me know if you have issues with this configuration.
Thanks,
Kadeem

0 xi xiao over 1 year ago in reply to Kadeem Samuel

Prodigy 150 points

Hi Kadeem,

I used the file Xi_Xiao_6_25_24_Configuration.hxt, as the file configured ref_mux=0h, ref_mux_src=1h, ip_byp_mux=0h, ip_byp_en_y0=1h, ch0_lvcoms_drv=1h, confirmed that 25MHz crystal oscillator works, the Y0 still has no output.

Read back the value of register 0x07 is 0x0404, it shows that the pll is unlocked and calibration is not done.

The read back of EEPROM's value attached(xixiao.txt), all values are same as the configuration file.

Fullscreen xixiao.txt Download

root@j7-evm:~# i2ctransfer -y 3 w4@0x77 0x00 0x0b 0x00 0x00
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0xee 0x02
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x49 0x0f
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x03 0x62
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x0e 0x00
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x14 0x00
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x41 0x04
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x0c 0x20
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x50 0x00
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x08 0x25
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x84 0x21
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x00 0x06
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x00 0x00
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x47 0x80
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x53 0x6a
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0xaa 0x80
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x44 0x00
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x10 0x01
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x00 0x28
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x45 0x05
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x79 0xc9
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x80 0x00
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x0a 0x00
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x12 0x00
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x29 0x04
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x00 0x02
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x28 0x02
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x48 0x00
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0xa4 0x10
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x00 0x08
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x80 0x08
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0xa8 0x00
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x10 0x44
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x00 0x33
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x80 0x20
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x80 0x02
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x41 0x04
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x3b 0xca
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x00 0x00
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x47 0x80
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x53 0x6a
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0xaa 0x80
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x44 0x00
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x10 0x01
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x00 0x28
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x45 0x05
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x79 0xc9
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x80 0x00
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x0a 0x00
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x12 0x00
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x29 0x04
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x00 0x02
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x28 0x02
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x48 0x00
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0xa4 0x10
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x00 0x08
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x80 0x08
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0xa8 0x00
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x10 0x44
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x00 0x33
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x80 0x20
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x80 0x02
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x41 0x04
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0x3b 0xca
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x0c r2
0xd6 0x4a
root@j7-evm:~# i2ctransfer -y 3 w2@0x77 0x00 0x07 r2
0x04 0x04
root@j7-evm:~#

The schematic show as below:

1. What should I do to figure out why Y0 is no output?

2. What's the meaning if gpio4_dir_sel=input, gpio4_input_sel=OE1(or OE2 or OE4), gpio1_dir_sel=input, gpio1_input_sel=OE4(or OE or OE1)?

Best Regards!

0 Kadeem Samuel over 1 year ago in reply to xi xiao

TI__Mastermind 22140 points

Xi,

Are you asserting the recal bit after writing this configuration to your device? You may need to remove the 27pF capacitors and then adjust the on-chip capacitive loading for your configuration:

The GPIO fields that you have listed control whether the GPIO1 and GPIO4 pins function as inputs or outputs, as well as their behavior. The configuration options are listed here:

Thanks,
Kadeem

0 xi xiao over 1 year ago in reply to Kadeem Samuel

Prodigy 150 points

Hi Kaddem,

I really appreciate your reply.

I've done some tests:

a. After writing these configurations, assert the recal bit to re-calibration, nothing changed, the value of register 0x07 is still 0x0404.

b. Pull down RESETN(pin8) then pull up, the value of register 0x07 changed to 0x0c04, pll locked but calibration didn't done.

c. Remove the 27pF capacitors and then adjust the on-chip capacitive loading from 3.0pF to 9.0pF(ip_xo_cload from 0x00 to 0x1f), every single one value i've tried, the value of register 0x07 always be 0x0c24, pll locked but calibration didn't done.

d. Set STARTUP0 register bypass_cal to 1h, cal_mute to 0h, there is still no output at Y0.

ps:I used oscilloscope measure the crystal oscillator, it works, can capture 25MHz.

Can you tell why calibration can't be done?

Thanks a lot.

Best Regards！

0 Kadeem Samuel over 1 year ago in reply to xi xiao

TI__Mastermind 22140 points

Xi,

Can you try bringing out SECREF to the output on the outputs page, and seeing if you can see the clock on one of the outputs?

Are you able to provide a capture of your power-up sequence with the 3.3V and 1.8V sources?

Are you able to also try this with the CDCE6214, and see if you have the same issue?

Thanks,
Kadeem

0 xi xiao over 1 year ago in reply to Kadeem Samuel

Prodigy 150 points

Hi Kadeem,

We used three CDCI6214 on our board, the other two works fine, just this one doesn't work.

There maybe some chip welding problem. We'll look into it, Thanks a lot for your help, it really helped a lot.

Wish everything goes well.

Best Regards!