This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ISD51 connect error

I have isd51.dll ver 2.34.

I would like to use an ISD with TI TUSB3210 processor (like standard 8052 derivate).
And I've got an Error message from
ISD51 Monitor Error:
'There was no reply from the target system!'

I correctly set baudrate to 9600, tested both in simulator and hyperterminal as well described in ISD51.htm file. The function with 'A'character and output character work perfectlly. So I go back to simulator and try send HEX 0xA5 by sin=0xA5 command in simulator - it display 0xF7 followed by 6 hex values. => It seems that all work OK.

But when I try it in Hyperterminal it does'not work. So I think that when Debugger send initial command - no response from 8052 by UART.

Where should be an error ?

Radim

Parents Reply Children
  • Thomas, how are you getting on with the TUSB3200 chip?
    Mine is starting to behave now, but I had a real struggle to start with due to lack of documentation from TI.

  • Very thanks Thomas!

    this I forgot, so I disable T2 and use standard T1 as baud rate generator.

    Can I use these values ?

    TMOD &= 0x0f;
    TMOD |= 0x20;
    SCON = 0x50; /* enable serial uart & receiver */
    PCON = 0x80;
    TH1 = RS232_BAUDRATE;

    TR1 = 1; // enable Timer 1


    2) I am using TUSB3210 chip for USB HID transfer protocol. I would like if it possible to discuss about it. Something I understood but something not. If anyone is interested in TUSB chips - it should be good to discus about it.

  • well, I have already done several designs with the TUSB3200A.
    For easy debugging I am using the 3200 in external mode.
    Although the docs could be better I found almost everything in the datasheet.
    One thing which I could not get work properly was the I2C port.

    You can reach me thzepf@yahoo.com

    thomas

  • >One thing which I could not get work properly was the I2C port.

    I did finally get it working, because an I2C connection to another processor (a PIC16F877) was a crucial part of my design.
    I referred to the TUSB3210 boot code, and did some signal logging with a digital CRO to finally crack it.
    (The TUSB3210 and TUSB4210 have very similar I2C hardware to the TUSB3200, but the error flag clears differently.)

  • Hej

    i am doing some TUSB6250 but can't really get started, so if you would share some of the codes i like that....


    Kasper