Occasional Contributor
Regular ContributorWe would like to inform you that since we haven't received a response from you regarding our previous notification, we will now move this discussion to community support. If you have any new questions or concerns, we recommend starting a new thread to receive assistance from Intel experts. Alternatively, if you don't have any further inquiries, our community users will be here to help you in this thread. Your understanding is greatly appreciated.
Occasional ContributorI'm sorry for the delay in my response. Here's the translation of your message:
"Sorry for the delay in getting back to you. Firstly, it's normal for the nCONFIG and nSTATUS pins to have pull-up resistors. When I encountered this error, I tested the voltage of these two signals and found that one was at 0V, while the other was around 0.7V. The same board can be programmed successfully on my colleague's computer almost every time, but on my computer, it's quite challenging. I'm not sure if there are differences in program settings causing this issue or if it's something else.
Regarding the second link you provided, I encountered an error, and it seems that 'myfile' is not valid.
Lastly, in the link you provided for changing the TCK clock frequency of the USB-Blaster, that seems to be for Blaster-II, while I'm using the Blaster. When I use it, there is no parameter called 'JtagClock'."
If you have any further questions or need assistance with specific technical issues, please feel free to ask.
