| Products > Test Equipment |
| Hantek HDG2002B AWG: 5Mhz or 100MHz? Let's see! |
| << < (129/134) > >> |
| FrankenPC:
--- Quote from: fremen67 on November 02, 2016, 12:41:03 am --- --- Quote from: FrankenPC on November 01, 2016, 08:33:38 pm ---I take it the DNW.EXE USB download program is part of the ARM toolchain support files? Or some kind of dev tools download? --- End quote --- Yes. Have a look back in the thread, here: https://www.eevblog.com/forum/testgear/hantek-hdg2002b-awg-5mhz-or-100mhz-let's-see!/msg451021/#msg451021 and here:https://www.eevblog.com/forum/testgear/hantek-hdg2002b-awg-5mhz-or-100mhz-let's-see!/msg451081/#msg451081 You don't need configs.zip as it is for OpenOCD. Just dnw and the drivers corresponding to your system. --- End quote --- HOKAY! So...Windows 7 x64 can now see the device when I plug/unplug the usb cable. "FriendlyARM MINI2416"...yadda yadda... It has a yellow exclamation mark but that may or may not mean anything. I select option 5 in UBOOT to download the rootfs.ubi file and run DNW. DNW says it can't open the USB port. In the config section of DNW do I need to put in a magic number for the USB connection? In device manager address property is "00000006". I've tried that in 0x00000006 hex notation. I've tried it without. I ran DNW as admin. Nadda. Any other pointers before I "Titanic" this thing? Thanks again for your assist. I still don't even know why the effin nand went bad in the first place. Gives me all kinds of warm fuzzies. |
| fremen67:
--- Quote from: FrankenPC on November 03, 2016, 05:06:35 am ---HOKAY! So...Windows 7 x64 can now see the device when I plug/unplug the usb cable. "FriendlyARM MINI2416"...yadda yadda... It has a yellow exclamation mark but that may or may not mean anything. I select option 5 in UBOOT to download the rootfs.ubi file and run DNW. DNW says it can't open the USB port. --- End quote --- With Windows 7 x64, I guess you have a "code 52" meaning that it does not want an unsigned driver. If it is the case (and it should be :)), use dseo13b to activate the test mode on Windows and then reboot. It should than work. Just run it again when you are finished, desactivate test mode and reboot. --- Quote from: FrankenPC on November 03, 2016, 05:06:35 am ---In the config section of DNW do I need to put in a magic number for the USB connection? In device manager address property is "00000006". I've tried that in 0x00000006 hex notation. I've tried it without. I ran DNW as admin. Nadda. Any other pointers before I "Titanic" this thing? Thanks again for your assist. I still don't even know why the effin nand went bad in the first place. Gives me all kinds of warm fuzzies. --- End quote --- Nothing to change on dnw. Just select "USB Port", "Transmit", "Transmit" again, select your file and this will launch the tranfer. Update: I changed the driver name to "EmbedSky TQ2416 Board" in the attached files as it is the name which appears initially when there is not driver installed ... |
| FrankenPC:
--- Quote from: fremen67 on November 03, 2016, 10:05:31 pm --- --- Quote from: FrankenPC on November 03, 2016, 05:06:35 am ---HOKAY! So...Windows 7 x64 can now see the device when I plug/unplug the usb cable. "FriendlyARM MINI2416"...yadda yadda... It has a yellow exclamation mark but that may or may not mean anything. I select option 5 in UBOOT to download the rootfs.ubi file and run DNW. DNW says it can't open the USB port. --- End quote --- So, after a 7 day vacation....I came back to this. You were right about the digital signature. But also, the intel USB 3.0 driver was killing the entire bus. So, it was a double whammy. Anyhow, it's running! Thanks again for your help! And yeah, I only uploaded the rootfs.ubi image. Nothing else. I need to calibrate I assume. No big deal. Cheers! --- End quote --- |
| TurboTom:
F/W 1.00.3.03.10, FPGA 81 is out! |
| wojt:
Luckily they fixed the issue with phase jumping when 2 channels have very close frequencies. Nice. |
| Navigation |
| Message Index |
| Next page |
| Previous page |