Other Parts Discussed in Thread: UCD9090, UCD90SEQ48EVM-560
Hi, team.
UCD9090 does not work.
But It works when connected to the tool and starts the GUI.
No operation on GUI, just connected.
What is the cause?
Best Regards,
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.
Hi, team.
UCD9090 does not work.
But It works when connected to the tool and starts the GUI.
No operation on GUI, just connected.
What is the cause?
Best Regards,
Hello
Based on what you described, it seems that device was stuck at ROM mode.
Please check bullet 3 of section 8.2.1 of https://www.ti.com/lit/ds/symlink/ucd9090a.pdf.
You can follow the attachment to exist the ROM mode.
8080.recover UCD9090A from ROM mode.pdf
Regards
Yihe
Thank you Yihe.
It was solved by writing the checksum.
However, it is unknown why the ROM mode has been set.
What are the conditions for entering ROM mode?
Best Regards,
Hello
I wrote to the UCD9090 using an evaluation board (UCD90SEQ48EVM-560).
After attaching the written chip to the board, a problem occurred.
The questions are listed below, can you check them?
1.Attach the writing method(1.pdf) we did.Is this writing method OK?
2.The chip that had the problem had a checksum of 0.Under what conditions will the checksum be 0?(2.PNG)
3.After regenerating the checksum, it become 3.PNG. Is checksum OK?
4.We have been writing on board UCD9090 until now.
There was no problem at this time.
Does this problem occur when the chip written on the evaluation board is mounted on another board?
Hi
Your programming methods are good. The reason why checksum is zero is that a special command(ROM_COMMAND) was issued from application to erase the checksum. This forces the devices into ROM mode. you can regenerate the checksum to bring the device out of ROM mode.
Regards
Yihe
Thank you for your reply.
I have a more questions.
1.Is there a special command (ROM_COMMAND) sent from the application in the writing procedure?
Can you check the program?
2.After regenerating the checksum, it become below picture. Is checksum OK?
Hi
The ROM_COMMAND is not part of the normal configuration, but as mentioned in the data sheet, the i2c signal integrity may change the commands.
If you follow the recover from ROM mode document, after regenerating the checksum, the device is back to program mode. you can click DEVICE_ID scan mode to confirm this.
Regards
Yihe