• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 4 answers
  • Subscribers 28 subscribers
  • Views 807 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

[FAQ] Supported USB to I2C Adapters

Further question about the USB to I2C adapter working with DLP EVM GUI.

Jerome Beguin
Prodigy 10 points
Other Parts Discussed in Thread: DLPA2005, DLPC3435, DLPC3430

Hi everyone. 
We have design a custom board using DLPC3435 and DLPA2005 to drive a DLP .2 WVGA. 
We haven't implement a USB to I2C or SPI on the board. 
So in order to debug, flash the firmware in the Flash memory we wanted to use the DLP EVM GUI software. But I will need a USB to SPI/I2C converter. 
From what I've read on this forum it appears that the GUI software is only compatible with few converter and one of them is not available anymore. (

So here is my questions:
- Can I use the CYUSBS236 from cypress ?

- Could the GUI use some serial command through an Arduino to connect to I2C ? 

- Is there any documentation in order to create the code for an Arduino to do the job and make it compatible and usable with the GUI software ?

- Is there another way or procedure to flash the firmware on the flash memory ?

Thanks in advance for you help. 

  • 0
    TI__Genius 12785 points

    Hello User,

    Welcome to the E2E forum and thank you for your interest in DLP® technology.

    Please allow me to address your questions.

    Jerome Beguin said:
    - Can I use the CYUSBS236 from cypress ?

    Yes, but please note that this is a development tool for the CY7C65215 bridge controller. In fact, the CY7C65215 is the bridge controller that we use on our EVMs. You may want to refer to reference design TIDA-00325 when considering how to incorporate this device into your design.

    Jerome Beguin said:
    - Is there any documentation in order to create the code for an Arduino to do the job and make it compatible and usable with the GUI software ?

    We do not have Arduino specific code or documentation available. However, we do provide a C language API to assist with software development on our DLPCs. Though this will not work directly with an Arduino micro-controller, the code can be used as a basis to write your own code, or can be converted to the Arduino programming language.

    Jerome Beguin said:
    - Is there another way or procedure to flash the firmware on the flash memory ?

    Depending on what tools you have at your disposal, it may be possible to flash the devices before soldering onto your custom board. If this is not possible, you may want to consider using an SOIC clip as detailed in this post.

    The DLPC can be flashed through the DLPC GUI, but this requires that the DLPC complete its boot process. Unfortunately a valid firmware image will be needed to be flashed for the DLPC to complete this process.

    Regards,

    Austin

  • 0 in reply to Austin Snyder
    Prodigy 10 points

    Hi Austin,

    Thank you for you reply,
    We have bought the equipment and followed this procedure. 
    The flash memory was successfully flashed. 

    But still the DLPC3435 didn't start properly. We have a PROJ_ON signal going to DLPA2005 and DLPC3435, then we can measure the DLPC communicate with the flash memory as we measure the SCZ0 and it goes down, but for not very long and then nothing happens. And HOST_IRQ stays high.

    I'm wondering if there is any issue with the file. What we've got from firmware selector tools is this file: FWSel_DLPC3430_DLPA2005_pm3_i2c0x36_v7p4p3.img

    And we used it as it is to flash the memory. Have we missed an operation ?

    Maybe an important question: 
    Is it necessary the DLPA2005 is connected to DLPC3435 through SPI ?

    Because in the design we have routed DLPA2005 with SPI0 on SCZ1. Could it be the issue ? Is there a way to change the firmware to tell DLPC3534 to use SPI0 SCZ1 instead of SPI1 SCZ0 to communicate with DLPA2005 ?

    Best regards

    Jerome

  • 0 in reply to Jerome Beguin
    TI__Genius 12785 points

    Hi Jerome,

    Jerome Beguin said:
    I'm wondering if there is any issue with the file. What we've got from firmware selector tools is this file: FWSel_DLPC3430_DLPA2005_pm3_i2c0x36_v7p4p3.img

    There is no issue with this firmware. To confirm I flashed the image on my hardware. The system booted without issue.

    Jerome Beguin said:
    And we used it as it is to flash the memory. Have we missed an operation ?

    So long as the hardware is correct, all that should be needed is to flash the firmware and drive PROJ_ON high.

    Jerome Beguin said:
    Maybe an important question: 
    Is it necessary the DLPA2005 is connected to DLPC3435 through SPI ?

    Yes, this is necessary. The DLPC needs to configure and communicate with the DLPA during bootup and the platform's operation.

    Jerome Beguin said:
    Because in the design we have routed DLPA2005 with SPI0 on SCZ1. Could it be the issue ? Is there a way to change the firmware to tell DLPC3534 to use SPI0 SCZ1 instead of SPI1 SCZ0 to communicate with DLPA2005 ?

    If SPI1_CSZ0 is not routed to the DLPA2005, this is very likely the issue behind your system not booting. The initialization process involves communication between the DLPC and DLPA. If this does not happen properly, the boot process will not complete. Unfortunately there is not easy method of switching this in the software.

    I recommend making alterations to your board by routing the DLPA SPI chip select to SPI1_CSZ0 to verify if the board boots with this change.

    Regards,
    Austin

  • 0 in reply to Austin Snyder
    Prodigy 10 points

    Hi Austin,

    It took me some times to make the SPI correction on the board. 

    I still have a question. How are we suppose to setup the pull-up / pull-down resistor on the GPIOs. 

    Because some of them are also used for DSI configuration at boot. So should I keep the config for DSI lines or set up all pull-up for SPI lines ? Can I configure the DSI lines later via software ? 

    Regards

    Jerome

  • 0 in reply to Jerome Beguin
    TI__Genius 12785 points

    Hi Jerome,

    Jerome Beguin said:

    I still have a question. How are we suppose to setup the pull-up / pull-down resistor on the GPIOs. 

    Because some of them are also used for DSI configuration at boot. So should I keep the config for DSI lines or set up all pull-up for SPI lines ?

    GPIO_3 (SPI1_CSZ0) and GPIO_4 (SPI1_CSZ1) need to be pulled up. GPIO_1 (SPI1_CLK) and GPIO_2 (SPI1_DOUT) are the GPIOs needed to configure the DLPC for DSI. These can be either pulled up or pulled down by a fairly weak pull resistor (say of at least 7.9 Kohms). The important aspect here is that they be in a defined state of pulled up or down but with a weak enough pull resistance so that the SPI bus can still force the signal.

    Jerome Beguin said:
    Can I configure the DSI lines later via software ? 

    Unfortunately no, this is not possible.

    Kind regards,

    Austin

  • 0 in reply to Austin Snyder
    Prodigy 10 points

    Hi Austin, 

    Ok I understand. 

    I'm using 1k pull-up /down resistor, Maybe it is too weak. I think I have some 10k in stock, I will test with 10k. 

    Best regards

    Jérôme Béguin

  • 0 in reply to Jerome Beguin
    TI__Genius 12785 points

    Hi Jerome,

    I agree in the thought that this may be too strong of a pull. Please let us know if this issue is resolved.

    Regards,

    Austin