Products > Test Equipment

Hantek HDG2002B AWG: 5Mhz or 100MHz? Let's see!

<< < (39/134) > >>

rdg:
It looks like all the relevant system files are dated Nov 7th 2013. I have attached the relevant files. Added .txt extension because the fourm doesn't allow tar.gz
Interestingly it looks like the kernel was compiled a bit more recently. Here is the /proc/version:

Linux version 3.2.35 (root@zgt) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-176) ) #42 PREEMPT Wed Mar 26 12:49:52 CST 2014

rdg:
I noticed the HDG conveniently echos the keyboard scan codes to the terminal when keys are pressed.
I get scancode 0x33 for clockwise rotation of the dial, 0x32 for counterclockwise. Perhaps someone could confirm the scancodes they get?

Looking through the startup messages, I see the the high pitched buzzing starts just after

close beep now
dso-buzzer s3c2416-beep initialized done...

So maybe those things are done in the wrong order. It stops after a keypress when there is a 'close beep now' message. Frequency is 5 kHz and it is just loud enough to be really annoying for me but I guess it is possible some people may not be able to hear that.

rdg:
Ok, here are some hack fixes to some of the software problems.

In /etc/init.d/rcS put
/dso/app/test_beep 1
just before sleep 5 near the end of the file. That will eliminate the buzzing on bootup.

To make sure the backlight always turns on, put
/dso/app/test_bkl on 80
after the sleep 5

Now it is possible to use the 'Last' option in system status to keep the previous settings, well not all of them evidently. They are not syncing the hardware clock to the system clock after you change it so that is still lost after reboot. There is no cron and since the device is normally hard shutdown a workaround is needed. I made a file /home/user/sync_clock.sh containing:

while true; do
hwclock --systohc --utc
sleep 30
done

make it executable and then call it in your rcS
/home/user/sync_clock.sh &
after the sleep 5. Seems to work.

Looking through the system there is a lot of unnecessary junk and stuff left over from the development board they were evidently using. For me the main binary seems to burn about 55% CPU at all times when not really doing anything. I do hope they make some effort to clean all of this up at some point ...

fremen67:

--- Quote from: rdg on June 23, 2014, 07:53:07 am ---Ok, here are some hack fixes to some of the software problems.

In /etc/init.d/rcS put
/dso/app/test_beep 1
just after sleep 5 at the end of the file. That will eliminate the buzzing on bootup.

To make sure the backlight always turns on, put
/dso/app/test_bkl on 80
after the sleep 5

Now it is possible to use the 'Last' option in system status to keep the previous settings, well not all of them evidently. They are not syncing the hardware clock to the system clock after you change it so that is still lost after reboot. There is no cron and since the device is normally hard shutdown a workaround is needed. I made a file /home/user/sync_clock.sh containing:

while true; do
hwclock --systohc --utc
sleep 30
done

make it executable and then call it in your rcS
/home/user/sync_clock.sh &
after the sleep 5. Seems to work.

Looking through the system there is a lot of unnecessary junk and stuff left over from the development board they were evidently using. For me the main binary seems to burn about 55% CPU at all times when not really doing anything. I do hope they make some effort to clean all of this up at some point ...

--- End quote ---
Your software version was compiled on Nov 7th 2013. It is surprising that you have this version in a new device. The problems you have are solved on version 1.00.2. Your afg_bin also weight 1.3Mbyte, the one I have (1.00.1) only 200kbyte. The good news is maybe it is compiled with debug infos  ;) . I did not check at the moment.
I tried to launch your version on my Hdg but some libs are also missing...I think the best would be to upgrade to the last version (1.00.2).

As there is no download available on Hantek site, there are not a lot of possibilities:
- you ask Hantek and they provide you with an update
- we can identify the modified files between your version and the last one and we create a patch
- you flash your HDG with a nanddump from another machine (you have to save your calibration file /etc/htg.cal and your serial /etc/system.inf)

I have v 1.00.1 (140402) which is already newer than yours but I don't have v1.00.2.
If someone could make a nanddump of a v1.00.2, I could try to create a bootable SD for update.

rdg:
Thanks fremen67.

I have tried asking hantek, as of now the only response I have got is them telling me that I do have the latest version. But I think I am on to a different person now so maybe I will get something eventually.

It does seem like I somehow got a board with a development version of the firmware on it. As you suspected, the binary does indeed have the debugging symbols compiled in. This could be a lucky break should anyone want to hack custom features or develop an alternative firmware. Still, it is annoying as of now from the point of view of having a reasonably functioning AWG. I can make a full dump of all the firmware if that is useful.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod