Discussion and support forum for http://www.embedded-projects.net/
You are not logged in.
Hi,
because of working with several toolchains on several Computers, Iīd like to install Atmel Toolchain in a VM-ware windows installation under windows. This works pretty well, only driver-installation drives me crazy ...
One week ago, my new USBprog 3.0 hardware arrived, programmed with "AvrIsp mk2 Clone". While installing the drivers works pretty well in Windows, it failes in VM-ware (because of detecting false VID/PID).
VID/PID in Windows: 0x03EB / 0x2104
VID/PID in VM-Ware: 0x0000 / 0x0000
As mentioned on other place here in the forum ("usbprog under vmware + possible source of other problems") still the sw seems to be the problem ...
Therefore three questions:
1.) Is there a problem with the patch, suggested by hcm (introducing a new variable: device description requested), that this solution was not introduced since 08/2009?
2.) Bernhard, You wrote that thereīs introduced this (or another???) patch is introduced in octopus. But I can find there only a few changes from char to unsigned char (I donīt think, this is the patch). Could You (or another specialist) please, give me a tip, where to find this patch?
3.) When applying this patch, I could generate a new "AvrIsp mk2 Clone" firmwarem which is running under VM-Ware. Generating a new Boot-Loader does not make sense for me, because of programming it without a second programmer isnīt possible. Is this correct, or is there a trick available, for replacing bootloader (without 2nd programmer)?
With regards,
Michael
Last edited by michael (2010-01-23 20:44:10)
Offline
Hi,
is there not a specialist, who can answer the questions above?
Maybe another question when starting with sw-development.
1.) Is there a introduction or howto in which way to start with alle the subdirectories on svn repository? What is intended / necessary for which situation? The Readme which is in the Base Directory shows only a few of them ...
2.) For generating AVRISP-mkII-Clone e.g. I have to choose between the "jtagicemk2klon_xmega" an the "jtagicemk2klon" subdirectory. I canīt find differnces between them (the C and H files are for me binary identical). Did I make an error, when getting them (forgetting to set a environment variable or a config spec for the actual release - but I donīt know, if such stuff is available in svn) ...
3.) Additional a rough memory-layout would be helpful: In this range is the boot code, this adresses are available for mk2-klon, etc. Is there such a overview available, and where can he be found?
Any advice would be appreciated ...
With regards,
Michael
Last edited by michael (2010-01-30 17:58:58)
Offline
Luckily I found this topic before ordering. So I guess it will not work or did you find any solution for the problem with Virtualization?
Like you I'd like to use this also in a virtualized Windows and I don't have any other programmer at hand...
Offline
Hi symphys,
sorry, I got not any reply on my postings, but Iīm looking forward, getting it to run.
Iīll try to get the patch from hcm running (see above) ... but at the moment, I have
very less time ...
But as I understand, at least the programmer, which deals with bootloader has to stay
on Windows directly, because I can not exchange the bootloader without a second pro-
grammer. Working on VMware and programming in Win-XP, that would be o.k. for me.
With regards,
Michael
Offline
I'm only starting and don't even have the programmer yet. The PICKit works well and usually any stuff works on VMWare. So most likely it's a software problem.
Do I understand you correctly that programming another device with the firmware current on usbprog will work in VMWare while exchanging the firmware with another one will not?
Offline
Hi symphis,
Sorry for my late response - the current fimware on the usbprog doesnīt work in VMWare. Exchanging this firmware
on the usbprog is possible (from Windows) without the need of a second programmer (but this firmware must be patched
and generated previously); Afterwards debugging and programming under VMWare should be possible ...
Exchanging the bootloader requires a second programming device, which I donīt have ...
With regards,
Michael
Offline