Skip to main content
B
b239955_st
Visitor II
June 10, 2004
Question

Indart and EEPROM Conflict

  • June 10, 2004
  • 4 replies
  • 1095 views
Posted on June 10, 2004 at 08:40

Indart and EEPROM Conflict

    This topic has been closed for replies.

    4 replies

    B
    b239955_stAuthor
    Visitor II
    June 9, 2004
    Posted on June 09, 2004 at 13:59

    Since Indart emulator uses the same pins as external EEPROM, I can not read, neither write inside my EEPROM memory by using Indart. did anybody have such a problem and is there any solution for that?

    Thank you
    L
    ldefend1
    Visitor II
    June 10, 2004
    Posted on June 10, 2004 at 06:34

    Which inDART are you using?

    Which MCU are you using?

    B
    b239955_stAuthor
    Visitor II
    June 10, 2004
    Posted on June 10, 2004 at 07:16

    I'm using indart-ST72C/SK and the micro is ST72C216G1M.

    thanks friul
    L
    ldefend1
    Visitor II
    June 10, 2004
    Posted on June 10, 2004 at 08:40

    As the inDART-ST7C user manual states on page 22 (limitations section) ST72C target device ISPDATA and ISPCLK lines are reserved for debug communication, therefore wasted and not usable by target application when inDART-ST72C is connected. Leave them connected to the target application (EEPROM in your case) some electrical conflict may arise, due to ISPDATA line that is shared with MISO function (Master Input Slave Output), in fact the EEPROM device could leave the line at 0 or 1 in push pull mode, instead tri-state. ISP communication from inDART and target microcontroller will be corrupted.

    Terms & ConditionsAccessibility statement