• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 21 subscribers
  • Views 640 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.

CDCE6214: CDCE6214 Can't program into EEPROM

YUXUAN CHIANG
Prodigy 155 points
Part Number: CDCE6214
The development progress is almost complete, but there is a problem that cannot be solved, please help to solve it, thank you.
Our power-on sequence follows the process provided in the datasheet.
And set HW_SW_CTRL and REFSEL to High, then use I2C to program.
When testing, use the customer's file, and configure register.
But whenever the REFSEL_SW of R2 is programmed to 0x2, the I2C line will be pulled low suddenly. It is normal to skip not program or program to other values.
The following is our hardware circuit plan, please help to confirm, thank you.
But the content I read from the EEPROM is the same as the preset value inside the IC, so the part of communication and reading is definitely normal.
  • 0
    TI__Mastermind 22310 points

    Yuxuan,

    The schematic does not appear to be an issue. 

    If the REFSEL pin is pulled low externally, and the default for R2[1:0] is 00h, why are they programming the REFSEL_SW to SECREF? It would not be necessary, as the external pin is already selecting SECREF.

    Without the programming of R2, is the EEPROM programming successful?

    Are they using TICS Pro to program the device, or something else?

    Once you program REFSEL_SW, is it SDA, SCL, or both that are pulled low? Do these lines get released, or is a power cycle required to bring the lines high again?

    Is the REGCOMMIT bit ever being written? Without this, the contents of the registers will not be written to EEPROM.

    Thanks,

    Kadeem

  • 0 in reply to Kadeem Samuel
    Prodigy 155 points

    Hi Kadeem,

     

    This circuit is the circuit I use to program IC, it only has programming function.
    And programming R2[1:0] is the programming file provided by my customer according to the set value.

    Regardless of whether the R2 is edited or not, it cannot be programed successfully.

    We use GPIO to simulate I2C to program IC.

    Both SDA and SCL will be pulled down. At present, they will not be released by themselves after testing.

    Both need to be reconnected to the power supply before they can communicate again.

    Yes, I have writes to REGCOMMIT.

    Thanks.

    Steve

  • 0 in reply to YUXUAN CHIANG
    TI__Mastermind 22310 points

    Yuxuan,

    Are the registers being written in the correct order (R85 to R0)?

    Are you certain that the CDCE6214 is the one pulling both lines low (when the I2C host is disconnected, is the I2C still pulled low)?

    Can you provide a .txt file of your register settings, so that I may use TICS Pro to try to load them into the device?
    Thanks,

    Kadeem

  • 0 in reply to Kadeem Samuel
    Prodigy 155 points

    Hi Kadeem,

    Yes, I wrote from Register R85 to R0, there is no problem with this order.
    After disconnecting CDCE6214, I2C is not pulled down.
    OK, I'll attach the file.

    Thanks.

    Steve

    Fullscreen CDCE6214_Register.txt Download 
    R85	0x00550000
R84	0x00540000
R83	0x00530000
R82	0x00520000
R81	0x00510004
R80	0x00500000
R79	0x004F0008
R78	0x004E0000
R77	0x004D0000
R76	0x004C0008
R75	0x004B0008
R74	0x004AA181
R73	0x00492000
R72	0x00480006
R71	0x00470000
R70	0x00460008
R69	0x0045A181
R68	0x00442000
R67	0x00430006
R66	0x00420000
R65	0x00410008
R64	0x0040A181
R63	0x003F2000
R62	0x003E0006
R61	0x003D0000
R60	0x003C0008
R59	0x003B0008
R58	0x003A502C
R57	0x00394000
R56	0x00380006
R55	0x0037001E
R54	0x00363400
R53	0x00350069
R52	0x00345000
R51	0x003340C0
R50	0x003207C0
R49	0x00310013
R48	0x003023C7
R47	0x002F0380
R46	0x002E0000
R45	0x002D4F80
R44	0x002C0318
R43	0x002B0051
R42	0x002A0002
R41	0x00290000
R40	0x00280000
R39	0x00270000
R38	0x00260000
R37	0x00250000
R36	0x00240000
R35	0x00230000
R34	0x00220000
R33	0x00210000
R32	0x00200000
R31	0x001F0000
R30	0x001E0060
R29	0x001D0000
R28	0x001C0000
R27	0x001B0004
R26	0x001A0000
R25	0x00190401
R24	0x00180024
R23	0x00170000
R22	0x00160000
R21	0x00150000
R20	0x00140000
R19	0x00130000
R18	0x00120000
R17	0x001126C4
R16	0x0010921F
R15	0x000FA037
R14	0x000E0000
R13	0x000D0000
R12	0x000C0000
R11	0x000B0000
R10	0x000A0000
R9	0x00090000
R8	0x00080000
R7	0x00070C0D
R6	0x00060000
R5	0x00050008
R4	0x00040000
R3	0x00030000
R2	0x00020002
R1	0x00012310
R0	0x00001010

  • 0 in reply to YUXUAN CHIANG
    TI__Mastermind 22310 points

    Steve,

    I will let you know by tomorrow (PST) if I encounter any issues with importing this file into EEPROM on an EVM.

    Thanks,

    Kadeem

  • 0 in reply to Kadeem Samuel
    TI__Mastermind 22310 points

    Steve,

    I believe that we are handling this through email, correct? If so, I will close this, and update with the final steps so that anyone that has this issue in the future can find the solution easily.

    Thanks,

    Kadeem