- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have a customer working with the CYBLE-416045-EVAL stick and has upgraded the programmer to KitProg3 in order to work within his Keil uVision environment. There is an error he is seeing, is it something we know about and can address? Here is his statement:
We almost succeeded to use Keil with the kitprog, hooray! The problem remains is this error: RDDI-DAP Error. Any ideas?
Thank you!
Please let us know.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I was trying to recreate this error. I was able to observe the error when I was playing around with the Max Clock setting in the Debug settings window. Also, it used to happen rarely during debugging. I was able to get past this issue by unplugging and replugging my kit. You can play around with the clock settings. It should be less than 1/3 of the BUS CLK frequency of the PSoC.
Please let me know if you are able to reproduce this issue consistently. If yes, please let me know the steps.
Regards,
Dheeraj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
In the MDK Keil Help there was a description about RDDI-DAP Error as below.
moto
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In the Target Options, select Cypress MiniProg4/KitProg in the Debug window. Then open the Settings window. Can you share the screenshot of this window?
Are you seeing the ID Code and Device Name listed?
Regards,
Dheeraj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I was trying to recreate this error. I was able to observe the error when I was playing around with the Max Clock setting in the Debug settings window. Also, it used to happen rarely during debugging. I was able to get past this issue by unplugging and replugging my kit. You can play around with the clock settings. It should be less than 1/3 of the BUS CLK frequency of the PSoC.
Please let me know if you are able to reproduce this issue consistently. If yes, please let me know the steps.
Regards,
Dheeraj