It is correct :-) audio-widget-PCM5102 is a branch of audio-widget-nik. However, there are changes in the features such that you need to use the PCM5102 version of the WidgetControl GUI tool for widgets with the PCM5102 firmware. And it is recommended that you do a "factory reset" after flashing the new firmware. Using the PCM5102 GUI tool with the "old" firmware or "old" GUI with the new firmware will leand to unpredictable results (ie disaster) :-)

OK. Do you think it is possible to change WidgetControl so that it simply dumps a range of defaults? That should be fairly easy, I guess, if read-status-from-Widget were a separate button and didn't happen automatically.

I'd prefer that over maintaining a separate set-the-defaults firmware. Clicking through WidgetControl takes quite a while when you're making a large pile of boards.

alex@downstairs:~/sdr-widget$ ./widget-control
usage: sudo ./widget-control [options] [values]
options: -a = list the devices connected and their serialIds.
-d = print the default feature values.
-g = get the feature values from the widget nvram.
-l = list the possible feature values.
-m = get the feature values from the widget ram.
-r = reboot the widget.
-s = set the feature values in the widget nvram.
-u serialId = open the device with the specified serialId.
Only -s and -u take values.
The -s option takes values in the form printed by -d or -g or -m.
The acceptable values for each feature are listed by -l.
The major and minor version numbers are optional to -s, but
if provided they must match the ones printed by -d, -g, -l, and -m,
which should all match each other
The -u option takes one value which is the serialId of the device you
want to program.
alex@downstairs:~/sdr-widget$ ./widget-control -d
11 38 widget uac1_dg8saq normal normal ak5394a pcm5102 hd44780 500ms fir
alex@downstairs:~/sdr-widget$

You should be able to give systemcalls in the c files. You could probably also keep it outside the code in the makefile as there should be some post processing abilities. So instead of a fairytale tonight - read them the make man page...

Brgds

BTW: The widget-control only works when I'm logged in as root in linux... How do I run it as admin in windows? I have tried to start a shell as admin and so forth and then shoot of the command without luck... It is just doing nothing. But alas, I have the crappiest XP installation at hand... Totally screwed. How do the rest of the XP users handle this?

About the experimental drivers - do you people get BSOD's when connecting the widget in XP? Vista works OK but I'm not alowed to experiment on that machine :-(