• State Resolved
  • Locked Locked
  • Replies 11 replies
  • Answers 4 answers
  • Subscribers 29 subscribers
  • Views 962 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.

DLPC6421: DataSheet Error duplicate pin E19 provided for P1_C_4 and P1_C_0 pins

Bill OLeary71
Prodigy 170 points

Part Number: DLPC6421

I submitted datasheet feedback, but I need to know the 

proper pin numbers for 

P1_C_4 

P1_C_0 

as soon as possible

I thought I submitted this same question yesterday, but I could not find it in the search for questions raised by me.

  • 0
    TI__Expert 4610 points
    Hello Bill,

    Welcome to e2e forum and Thanks for choosing DLP Technology.

    Thanks for pointing out the issue, We already found that issue few days back and we had put the datasheet in modification phase.

    correct pin config :
    P1_C_4 : AE19
    P1_C_0: AE18

    Thanks,
    Navneet
  • 0 in reply to Navneet Singh
    Prodigy 170 points
    thanks,
    Will you also add the missing comma in the list of ground pins?
  • 0 in reply to Bill OLeary71
    Prodigy 170 points
    Hi Navneet,

    There is also one more bit of inconsistency in the pinList
    on Page 8, the PM_ADDR_22 and PM_ADDR_21 pins are included in the list,
    they are the only 2 pins that are repeated in the table because they have a GPIO equivalent.
    This makes it difficult to automate reading the table from a a spreadsheet,
    I understand why they are shown this way, but would you consider placing them in the GPIO part of the table only
    and make them standout some other way in the PROGRAM_MEMORY section of the table without presenting them as a valid pin
    (otherwise I get a warning for duplicate pins A12 and E11) (if you merged all the cells into 1 for those entries, it would be easy to ignore!)
  • 0 in reply to Bill OLeary71
    Prodigy 170 points
    one more tweak...
    on page 11
    the 5th cell from the bottom of the table...
    there is a space between 'R-' and the 'VDQPAD_[7:0]' which makes my automated reader think the 'R-' is another pin
    can you split that line at the comma make it R-VDQPAD[7:0]
  • 0 in reply to Bill OLeary71
    TI__Mastermind 30875 points

    Hi Bill,

    The controller as such allows interfacing parallel flash upto 128Mb. These pins will be used as address lines only when interfaced with larger memory, otherwise they can be free GPIOs.

    We understand your point, since the default function is configured as memory interface pins, may be we can hide the GPIO_35, GPIO_36 from the list down so that you don't find duplicate pin issue.

    Regard,

    Sanjeev

  • 0 in reply to Bill OLeary71
    TI__Mastermind 30875 points
    On the Page #11.
    Got it, we will fix it in the next datashseet update.
  • 0 in reply to Bill OLeary71
    Prodigy 170 points

    So far I'm good with all the changes,

    I'm not sure you acknowledged this change:

    (adding the missing comma in list of ground pins)

  • 0 in reply to Bill OLeary71
    Prodigy 10 points
    hello invoice,

    The controller as such allows interfacing parallel flash upto 128Mb. these pins can be used as address traces best when interfaced with larger memory, otherwise they may be free GPIOs.

    We recognize your point, because the default function is configured as reminiscence interface pins, can be we are able to hide the GPIO_35, GPIO_36 from the list down so that you don't discover reproduction pin problem.

    Regard,
  • 0 in reply to IBOUKHOULEF FOUAD
    TI__Mastermind 30875 points

    Hi IBOUKHOULEF,

    Sure we can consider that, just to avoid pin confusion we can hide GPIO_35, GPIO_36 from the table and can leave comment comments section that FLASH Address lines saying PM_ADDR_22 and PM_ADDR_21 are re-purposed GPIOs for interfacing larger memory size flash parts.

    Regards,

    Sanjeev

  • 0 in reply to Sanjeev
    Prodigy 170 points

    Its not a big deal, but I would prefer that you leave the pins in  the GPIO section and refer back to them in the external memory section.

    You already have the GPIO section setup with the extra columns to enable a tool to merge the functional pinNames to the GPIO Name,

    so thats what I did...

    I actually just put a '#" in front of the 2 address pins in the external memory section so my tool could ignore those.

    Then I built the symbol like this:

    and I built the gpio symbol like this where I left space for the 2 pins we moved to the external memory interface

  • 0 in reply to Bill OLeary71
    TI__Mastermind 30875 points
    Bill,
    Okay thank you for sharing info. We have notified internally for document correction and will update as soon as we update the datasheet.
    Regards,
    Sanjeev