Cannot flash Au

Help Request
21

I promise I have found the actual issue now. Usually I have 2 Lab windows open, one for a bigger project, and one to test modules individually. When 2 or more windows are open, the RAM loading works fine, but when trying flash loading, or erasing, I get this error: TDO didn’t match. Got FE expected 31 with mask 11 at byte 0

When one window is open, flash works perfectly. I do not know why. Like I said before, I am new to electronics. So far, this error appears in .19 and .20 for me, and I have not tried any other versions yet.

22

Interesting, good find!

It likely has to do with each window doing periodic sweeps of connected devices. I’ll look into it.

1 Like
23

I knew I could be useful.

Edit: Also when I let Labs run for a while, at one point it does not let me do anything but close it

24

I just tried it natively on Arch and in a Ubuntu VM and couldn’t reproduce it.

Are you running in a VM or anything else notable about your setup?

25

I do not think that there is too much different than the usual, Jammy Jellyfish is incomplete though, I do not have Appimage, and besides Labs, KiCad and LTSpice running through Wine, there are no appimages for Vivado, ISE, etc. Also it is unusually laggy here. Some things I can not pinpoint here but I do not think there is any big differences, besides that I had to create a launcher to give Labs the VIvado location. There is a lot missing that I used to have that disappeared when I went from 24.04.1 back to Jammy, so that is severely annoying. Maybe it is a unique issue.

Maybe you can check the specific error?

26

Update: I have moved back to 24.04.1 (Edit, I am on LTS, maybe that is a factor?), and the problem still exists. All I know is that it is there, I do not know why.

I have 2 old Aus, maybe it is a problem related to the old Au’s hardware? If I buy some of the new boards, I could test for that problem.

27

The JTAG interface is identical on the new boards.

When you say it’s still there, do you mean only when you have two open or always?

Are you running Ubuntu in a virtual machine or is it running directly on your computer?

28

Its running directly on my computer, and it is there when i have 2 or more tabs open. Also, when I leave Labs for a while, at one point, it does not allow me to de anything but close it.

29

Hi, I just got a similar error. Its the first time I tried to flash the AU I have been using for over 2 months.

II had just updated the SW with 2.0.41-beta.

I was using 2.0.38-beta before.

I loaded 2.0.38-beta and the error persists.

Same error with flash or ram programming

Checking IDCODE…

TDO didn’t match. Got FF expected 03 with mask 0F at byte 0

I ran a FTDI text program made available by “gc74” .

image
image610×506 37.1 KB

30

I just tested the Pt and the Cu boards and they program.

31

Hello,

IDCODE missmatch means the FTDI chip have issue communication with the FPGA over the JTAG bus.

If you never programmed the board, you can check 2 things :

  • The power led turn green or stays red?
  • The 8 LEDs do the blinking pattern when the board is powered?
32

Hi, I returned the board this morning.

It was flashing the LED’s from the last program loaded.

I did not check for communication output. The loaded program should be transmitting from the onboard USB and the FT+ board if attached would be sending out a constant stream of data, if a computer was communicating with the FT601.

The board did respond to the FTDIListDevices.exe as posted above.

33

If you never flashed it but it was flashing leds means that it had the factory program on, so it was working when it left the factory, but maybe got damaged during transport or later :frowning:

My program talks with the FTDI interface chip on the bottom of the board, which in turn communicate with the FPGA.

So the issue is possibly a broken solder on a JTAG pin.