• State
  • Locked Locked
  • Replies 11 replies
  • Subscribers 31 subscribers
  • Views 2087 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.

Configuring FPGA on Lightcrafter on power up.

Shinichi Watanabe
Intellectual 460 points


I understand the FPGA starts configuration with "nCONFIG" pin going to high after power on.
And nCONFIG is connected to GIO46 of DM365. This line should be controlled by DM365 s/w
properly. But GIO46 keeps as GIO input mode. The line is observed about 2.2V because external
pull-up resister is connected.

I guess the FPGA starts configuration when nCONFIG goes to 2.2V from 0V at power on.
In this case state of GIO23 impacts the high level of DO output(FPGA Flash) in the beginning
of configuration. But the FPGA retries configuration with "Auto-restart configuration on error"
option. Then configuration will be succeeded when GIO23 is stabled.

Please check DM365 s/w and control GIO46 properly. Also please check operation of GIO45(nCE).

Thank you.
Best regards,
S.Watanabe

  • 0
    TI__Mastermind 30600 points
    Watanabe-san,

    Thanks for your post. Could you clarify your question? Are you having an issue with the LightCrafter 4500?

    Thanks,
    Paul
  • 0 in reply to Paul Goedeke
    Intellectual 460 points

    Paul, let me summarize my concerns.

    -I am talking about Lightcrafter 3000.

    -I understand the FPGA on the board should be configured on Power up.

     The FPGA starts cofiguration when nCONFIG goes to high.   The signal is connected

     to GIO46 of DM365.  But GIO46 is configured as input.  

     Please check S/W of DM365.

    P.S. Actually nCONFIG input goes to 2.2V and start configuration because the is pull up

    to 3.3V.  But sometimes DO output from FPGA serial ROM conflicts with GIO23 of DM365.

    DO is connect to GIO23 of DM365 to support programming serial ROM with GUI.

     

    Thank you.

    Best regards,

    S.Watanabe

  • 0 in reply to Shinichi Watanabe
    TI__Mastermind 30600 points
    Watanabe-san,

    You're concerned about the serial ROM conflicting with GIO23? Have you had any symptoms on your Lightcrafter? What issues are you seeing?

    Thanks,
    Paul
  • 0 in reply to Paul Goedeke
    Intellectual 460 points

    Paul, please see attached waveforms.

    We can see unexpected low H-level on DO output at the beginning of FPGA configuration.

    The DO output is connect to GIO23 of DM365.   Also I do not see unexpected level after

    removing R8(disconnecting GIO23 connection).

    Thank you.

    Best regards,

    S.Watanabe

     FPGA_ROM_timing1.pdf

  • 0 in reply to Paul Goedeke
    Intellectual 460 points

    Paul, please see attached waveforms.

    We can see unexpected low H-level on DO output at the beginning of configuration.

    I do not see the unexpected level after removing R8(disconnecting GIO23).

    Also I see 2.2V for H-level on nCONFIG.   The control is connected to GIO46 of SM365.

    But GIO46 is configured as input.  Please check Lightcrafter firmware.

    Thank you.

    Best regards,

    S.Watanabe

    2870.FPGA_ROM_timing1.pdf

  • 0 in reply to Shinichi Watanabe
    TI__Mastermind 30600 points
    Watanabe-san,

    Thank you for the detailed waveforms. I'll take a look at this and get back to you.

    Can you describe for me any symptoms you're seeing with Lightcrafter performance? Is it not booting up correctly? Or not being programmed correctly? What isn't working?

    Thanks,
    Paul
  • 0 in reply to Paul Goedeke
    Intellectual 460 points

    Paul, the symptom is reported by our customer who has built the hardware similar to

    DLP lightcrafter 3000.   They have faced FPGA configuration fail(timeout?) sometimes.

    In most cases configuring FPGA is succeeded because FPGA retries configuration.

    Thank you.

    Best regards,

    S.Watanabe

  • 0 in reply to Shinichi Watanabe
    TI__Mastermind 30600 points
    Watanabe-san,

    Thank you for the explanation. I'll post back when I have more information.

    Paul
  • 0 in reply to Paul Goedeke
    TI__Mastermind 30600 points

    Watanabe-san,

    I checked the lines you mentioned and showed me in the attachment on a standard Lightcrafter. I did not see any of the same symptoms you reported. The FLASH_DI line did not have the 1.2V anomaly you showed and the FLASH_CSZ line didn't have the activity that I circled in the below image.

    I'm wondering about your mid-level comment for FLASH_CONFIGZ. I saw the line jump from 1.6V to 3.3V. The line actually started at a mid value and it looks like that may be the case in your picture as well, although I can't tell.

    When you discuss removing R8, are you removing R8 from the Lightcrafter or from a custom board? Are the scope shots you sent me from a Lightcrafter?

    Thanks,

    Paul

  • 0 in reply to Paul Goedeke
    Intellectual 460 points

    Paul, thank you for your investigation on your Lightcrafter.

    I understnad you did not see the symptom.

    A customer has reported the symptom on their board.  Also I saw the symptom on my Lightcrafter.

    The scope shots are from my Lightcrafter.

    I guess the timing of FPGA_CONFIGZ is not correct.   This signal should be driven by DM365 at

    proper timing.   The level of 2.2V may be made by external Pull-up resistor and internal Pull-down

    resistor.    I have checked GPIO configuration register after booting the Lightcrafter.

    GPIO46(FPGA_CONFIGZ) is configured as input.

    Thank you.

    Beset regards,

    S.Watanabe

  • 0 in reply to Shinichi Watanabe
    TI__Mastermind 30600 points
    Watanabe-san,

    This issue is going to take some deeper investigation. We'll take note of the issue in our tracking system.

    If the device successfully retries or removing R8 solves the issue, are these solutions that the customer can use?

    Thanks,
    Paul