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.
Part Number: TMS320VC5505
I recently wrote a simple software for the TMS320VC5505 eZdsp Stick (revB) by using the usual example code. Everything was working fine until I loaded the program to EEPROM using the eZdsp Programming Tool (programmer_USBKey.out). Afterwards the communication over I2S totally stopped working. The measurement of the I2S pins pointed out that there are absolutely no I2S signals at any time, neither in a debug session nor by running the program programmed to EEPROM.
The main problem is that I cannot restore a working state so that I have no idea where to start identifying the causes of the problem.
In another thread I found the hint
"We know this issue. The example did not clear some conditions set by pre-installed code (boot from flash)."
Therefore one thought would be that those conditions set by pre-installed code were necessary for my software to start up/initialize I2S.
The important part of the code (or a minimal example) is basically the example code. Other parts of the program (UART, LED) are not affected and work exactly as expected..
Is there anyone who had a similar problem ?
Many thanks in Advance!
- TMS320VC5505 eZdsp USB Stick (Rev B)
- Code Composer Studio Version: 126.96.36.19900
- .out to .bin conversion using hex55.exe (latest version)
- programming using eZdsp Programming Tool (programmer_USBKey.out).
Please make sure you read the forum guidelines first.
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to Lalindra Jayatilleke:
Thank you for asking!
The problem is still present, but as I had no possibility to get the system back in a working state, I purchased the same Stick again (it's RevC now). As I fear that loading the program to EEPROM will lead to the same result, I did not try it yet with the new Stick. Therefore, I would be happy about any hint regarding the problem in this thread.
In the event that I find the source of the problem and/or a solution, I will post it here.
In reply to Richard Stelzer:
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.