I have successfully programmed my Basys2 using the 'djtgcfg' utility under Linux dozens of times, but I'm no longer able to do so. When I attempted to program the board yesterday, I got some unusual results:
> djtgcfg enum
Device: 3.....O......<.
Product Name: Digilent Basys2-100
User Name: 3.....O......<.
Serial Number: 210155528315
> djtgcfg init -d 'Basys2'
ERROR: unable to open device "Basys2"
> djtgcfg init -d '3.....O......<.'
ERROR: unable to open device "3.....O......<."
*I used the '.' character in the strings above to represent non-printable characters, because the replacement character used by my terminal won't display properly on this page.
Using the product name or serial number yields a similar result. It appears that I can't communicate with the device due to a corrupted device ID. However, my computer has no trouble recognizing the Basys2 board:
> lsusb
...
Bus 003 Device 011: ID 1443:0007 Digilent Development board JTAG
...
For what it's worth, here is the hexdump of the djtgcfg result above:
I succesfully programmed a friend's Basys2 multiple times using djtgcfg after having this problem with my board. When using his board, the output from djtgcfg was normal (all printable characters).
After experiencing this problem under Linux, I sucessfully programmed my Basys2 from a Windows machine. When using Adept2 under Windows, the device ID string still appears corrupted, but I am able to program it anyways.
I don't have regular access to a Windows machine, so I'd really like to get this working under Linux again. I'm hoping this is just an issue of some corrupted Flash or EEPROM in the AT90USB that could be fixed by reprogramming it... but I'm not sure what to try next. Any ideas?
Question
odougs
Hello,
I have successfully programmed my Basys2 using the 'djtgcfg' utility under Linux dozens of times, but I'm no longer able to do so. When I attempted to program the board yesterday, I got some unusual results:
*I used the '.' character in the strings above to represent non-printable characters, because the replacement character used by my terminal won't display properly on this page.
Using the product name or serial number yields a similar result. It appears that I can't communicate with the device due to a corrupted device ID. However, my computer has no trouble recognizing the Basys2 board:
For what it's worth, here is the hexdump of the djtgcfg result above:
So it appears the device ID as seen by djtgcfg is
A couple of other details that might be helpful:
I don't have regular access to a Windows machine, so I'd really like to get this working under Linux again. I'm hoping this is just an issue of some corrupted Flash or EEPROM in the AT90USB that could be fixed by reprogramming it... but I'm not sure what to try next. Any ideas?
Thanks for reading!
Link to comment
Share on other sites
6 answers to this question
Recommended Posts
Archived
This topic is now archived and is closed to further replies.