- #ZADIG DRIVER INSTALLATION ABORTED HOW TO#
- #ZADIG DRIVER INSTALLATION ABORTED INSTALL#
- #ZADIG DRIVER INSTALLATION ABORTED DRIVERS#
- #ZADIG DRIVER INSTALLATION ABORTED DOWNLOAD#
The drivers part was pissy, but once figured out, no big deal. To me, the toughest part was matching up the JTAG pinouts and opening the case without breaking the sticker, in that order. Whew! It's late and I feel goofy, so you'll have to deal with my terrible humor in there. Enter your keys into the scope however the hell you want, and send a bottle of tequila my way, if you like.Now, prepare your champagne glass and run this:.If you get a keys not found message like I did, make sure your scope is in RUN mode and has an active trace then re-dump the SRAM. Move that file to where you have rigup.exe.Your dump file will be in the same folder as the executables (the subdirectory of the Bfin-toolchain install).dump binary memory ds2k_00_sdram.bin 0x00000000 0x07FFFFFF.Watch the gdbproxy window for periodic messages. The command follows and will take a LONG time. Now, as the two girls one cup people said, we will begin the dump.
Fix that, then CTRL-C both command prompts and relaunch the proxy then GDB until you get success. If it didn't work, you suck, or your drivers suck.
If it worked, you should see a list of 8 regions (from 0-7). For the next 2 lines, type these comamnds at the (gdb) prompt:. In command prompt 2, run bfin-elf-gdb.exe with no parameters. Keep window 1 open, Trebek, you scurvy bastard! (Saturday Night Live reference, there). This is basically an intermediary program that will allow the special bfin version of the Gnu Debugger (GDB) to "speak JTAG" - it's like talking dirty to the chip, but better! If you followed so far, you should get a message stating that the gdbproxy is waiting on port 2000. In command prompt 1, run the following: bfin-gdbproxy.exe -debug bfin -frequency=5000000. Open 2 command prompts as administrator in this folder. #ZADIG DRIVER INSTALLATION ABORTED INSTALL#
Install the Blackfin toolchain on a folder on your desktop and go to that directory, and then into the subfolder elf\bin. I then installed the WinUSB driver for the first Olimex device in the list using the handy Zadig driver installer from here:. This is left as an exercise for the reader. Install the drivers for the JTAG adapter as attached - there are instructions on Sparkfun and Olimex's sites. This is WAY beyond the scope of this post. #ZADIG DRIVER INSTALLATION ABORTED HOW TO#
PREREQUISITE 4: Figure out how to hook up the circuit to the JTAG header using pull-up resistors, etc. Being loaded with disposable income, I used the Olimex from Sparkfun - $71 of goodness. Get your JTAG adapter and drivers installed. #ZADIG DRIVER INSTALLATION ABORTED DOWNLOAD#
PREREQUISITE 2: Download the 32-bit Blackfin toolchain 2014R1 from here:. If using UAC, you MUST run the command prompt as administrator. Please keep general Windows questions to other threads. If you don't know it, Google is your friend. I am NOT going to detail general Windows tasks. OK, as requested by Gandalf_Sr, here is my detailed step-by-step guide to my *working* hack on the MSO2072A. Now I can run 'JTAG Shell' from start and interact with the command prompts. I used libusb-win32-bin-1.2.6.0.zip Next I unpacked the libusb-win32-bin-1.2.6.0 folder to C:/Temp and then opened the bin folder and installed install-filter-win.exe (I think) Next I ran the inf-wizard.exe file while my USB Blaster was plugged in, it found and created an inf file and then offered to install it, I accepted. I'm trying to follow in Slappy's footsteps, I downloaded urJTAG, managed to install on my Windows 7-64 system (you have to run the install as Admin), but then got an error every time I tried to run it with my el-cheapo 'Altera' USB Blaster from eBay saying it couldn't find the libusb0.dll driver - I believe I've just solved that issue I downloaded libusb-win32 from here. I'll leave that dump running but suspect it will be the same as the previous ones. 
I have the Ubuntu Netbook dump running but I got the error at the stage of testing the memory using '(gdb) info dump' which replied that it could not parse XML because that feature was not included at compile time.
0 kommentar(er)
