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

LMK03328: Codeloader port configuration

Ashwin Vasudevan
Prodigy 40 points
Part Number:

Hi,

I have a question about port configuration in the Codeloader tool, while using a 3 pin I2C header with on my board with the 10 pin header of the USB2ANY module. On the Port Setup tab, what do I set my pin configuration to? Currently I have 3 jumper wires connecting directly as shown below

 USB2ANY J4.1 -> SDA on board

USB2ANY J4.2 -> SCL on board

USB2ANY J4.5 -> GND on board,  and am able to detect the device on the I2C bus (at address 0x54).

 

The Codeloader has the mapping as in the attached picture, but I have tried changing it to clock bit -> pin2 & data bit -> pin1. In both cases, the data read from the LADR registers is different for LADR 2-5 (byte 2-5), shown below. I did try changing the pin # few more times but get the same result every time. There is no clock output from the LMK3328 also.

# EEPROM file originally exported: 18/04/2017
# Restored to GUI Map from:
#
#    HADR    LADR    DATA    BYTE
#    -------    -------    --------    ---------------
    00    00    01    0
    00    01    00    1
    00    02    00    2
    00    03    00    3
    00    04    A4    4
    00    05    20    5
    00    06    02    6

# EEPROM_Data_Read

#    HADR    LADR    DATA    BYTE
#    -------    -------    --------    ---------------
    00    00    01    0
    00    01    00    1
    00    02    AD   2
    00    03    1F    3
    00    04    2A    4
    00    05    15    5
    00    06    02    6

* What should the pin configuration be?

* Do I need to check anything else to ensure that the EEPROM is correctly programmed?

Thx,

  • 0
    Prodigy 40 points

    Ashwin Vasudevan said:

    Part Number: LMK03328

    Hi,

    I have a question about port configuration in the Codeloader tool, while using a 3 pin I2C header with on my board with the 10 pin header of the USB2ANY module. On the Port Setup tab, what do I set my pin configuration to? Currently I have 3 jumper wires connecting directly as shown below

     USB2ANY J4.1 -> SDA on board

    USB2ANY J4.2 -> SCL on board

    USB2ANY J4.5 -> GND on board,  and am able to detect the device on the I2C bus (at address 0x54).

     

    The Codeloader has the mapping as in the attached picture, but I have tried changing it to clock bit -> pin2 & data bit -> pin1. In both cases, the data read from the LADR registers is different for LADR 2-5 (byte 2-5), shown below. I did try changing the pin # few more times but get the same result every time. There is no clock output from the LMK3328 also.

    # EEPROM file originally exported: 18/04/2017
    # Restored to GUI Map from:
    #
    #    HADR    LADR    DATA    BYTE
    #    -------    -------    --------    ---------------
        00    00    01    0
        00    01    00    1
        00    02    00    2
        00    03    00    3
        00    04    A4    4
        00    05    20    5
        00    06    02    6

    # EEPROM_Data_Read

    #    HADR    LADR    DATA    BYTE
    #    -------    -------    --------    ---------------
        00    00    01    0
        00    01    00    1
        00    02    AD   2
        00    03    1F    3
        00    04    2A    4
        00    05    15    5
        00    06    02    6

    * What should the pin configuration be?

    * Do I need to check anything else to ensure that the EEPROM is correctly programmed?

    Thx,

  • 0 in reply to Ashwin Vasudevan
    TI__Mastermind 32575 points
    Hi Ashwin,

    The I2C SDA/SCL signals from USB2ANY will come out on Header pins J4.1/2 (SDA/SCL) regardless of the Pin Configuration settings. You can revert the Pin Configurations to the original (Figure 3 in the EVM SW User Guide).

    It is good that you can detect the device at address 0x54.

    Instead of sending the .epr file, can you send the GUI configuration .mac file (File > Save)? This file format saves more information, such as PRIREF / SECREF input frequencies which are used to compute the VCO and output frequencies based on the programmed divider settings.

    Thanks,
    Alan