Please don't cut-and-paste the ANSI codes. It makes the logs very difficult to read.
I don't know what you mean, i posted the log i get in the windows cmd, i thought you need the complete log... Will delete these line now.
This:
←[1m
is an ANSI code. On Linux (every terminal program I've ever seen) and Mac when you copy-and-paste from a terminal window it does not include that stuff. If Windows doesn't work that way and you can't find a terminal program that acts normally, you can use -Dcolor_console=false to simply turn off the color.
USERCODE before bitstream upload: 0x657f5ebe
WOW, caught it red-handed:
your board is BROKEN. That is supposed to be 0xcafebabe. You are definitely, definitely, definitely getting corruption on your jtag lines.
java.io.IOException: TML acknowledgement of read operation failed; expected=0x435 got=0x0
Same story here. If a few reads and writes succeed (like "magic number check ok"), and then you get one of these, it is 100% certain that you have signal integrity problems on the JTAG bus.
I am really sorry, but
you have data corruption issues on your JTAG bus -- this is a hardware malfunction. You really need to contact your board vendor and work this out with them. The TML definitely isn't going to work properly if the data it sends to the chip is getting corrupted
not a lot I can do about that.
Sorry man, I know this isn't what you want to hear, but this is incontrovertible proof that the bits being sent into the JTAG bus are not the same bits coming out the other end. And, unfortunately, there is nothing that can be done in software or in the bitstream to fix that.
