Community > MAX1000 community projects
MAX1000 Driver and Setup Files
8x8:
--- Quote from: JH on October 14, 2019, 01:41:32 PM ---Arrow provide also an diagnose tool which helps to identify the problem:
https://shop.trenz-electronic.de/Download/?path=Trenz_Electronic/Software/Drivers/Arrow_USB_Programmer
--- End quote ---
I tried that, got the same error as mrisco. The search for programmer hardware is the only test that failed (Error. No programmer hardware found.).
JH:
Hi,
i'm a little bit confused now.
So Arrow diagnose tool didn't find the programmer after you has changed EEPROM like on your link or before?
If it didn't find it now, can you send me the whole log and did you run it as Admin(is needed to reset JTAG Server Service)?
And "Several bytes after the USB id" after USB ID can also happens when the person from your link has changed some other port parameters.
Did the FTDI tools told you the EEPROM was empty? Or did it found some configuration and in this case did you remember what you read as product description (something with Arrow in the name?) ?
br
John
8x8:
--- Quote from: JH on October 15, 2019, 08:58:23 AM ---Hi,
i'm a little bit confused now.
So Arrow diagnose tool didn't find the programmer after you has changed EEPROM like on your link or before?
If it didn't find it now, can you send me the whole log and did you run it as Admin(is needed to reset JTAG Server Service)?
--- End quote ---
My device is now detectable and I have been able to program it via Quartus on Linux. My earlier comments were in response to your questions regarding the device in its original state.
--- Quote from: JH on October 15, 2019, 08:58:23 AM ---And "Several bytes after the USB id" after USB ID can also happens when the person from your link has changed some other port parameters.
Did the FTDI tools told you the EEPROM was empty? Or did it found some configuration and in this case did you remember what you read as product description (something with Arrow in the name?) ?
--- End quote ---
Yes, I realized that. The FT_PROG tool did not indicate the EEPROM was blank.
JH:
Hi,
thanks for clarify.
Without the old content i can't check if this wrong content was caused by our production or not. Maybe you can send me one time the serial number (number on the white sticker with QR Code), so I can check another module from the same production batch, in case we have it still on stock.
br
John
8x8:
--- Quote from: JH on October 15, 2019, 01:44:27 PM ---Maybe you can send me one time the serial number (number on the white sticker with QR Code), so I can check another module from the same production batch, in case we have it still on stock.
--- End quote ---
My S/N is A01756.
Navigation
[0] Message Index
[*] Previous page
Go to full version