Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chameleon RevG not getting into Bootloader in Windows 10 #270

Open
nov3mb3r opened this issue Aug 12, 2020 · 20 comments
Open

Chameleon RevG not getting into Bootloader in Windows 10 #270

nov3mb3r opened this issue Aug 12, 2020 · 20 comments

Comments

@nov3mb3r
Copy link

nov3mb3r commented Aug 12, 2020

I have a problem entering the bootloader. I press the RButton, upon connecting my USB, installed the atmel driver, but upon running the ChameleonFirmwareupgrade, I get an application error: dfu-programmer: no device present.
Some side notes:
This is a genuine KAOS product from you,
No lights are flashing during connection
atmel driver installed successfully
Run ChameleonFirmwareUpgrade.bat as admin

@nov3mb3r nov3mb3r changed the title Chameleon not getting into Bootloader in Windows 10 Chameleon RevG not getting into Bootloader in Windows 10 Aug 13, 2020
@madalinamarin
Copy link

I had the same problem, I solved it using macOS.

@david-oswald
Copy link
Collaborator

Dear @nov3mb3r, can you check in the dev mngr that the atmel drivers are installed and that the chameleon is really in the bootloader (i.e. shows up as Atmel DFU or so)?

@nov3mb3r
Copy link
Author

This is my Device Manager:
image
I would expect that the bootloader is the AT32UC3A. Is that correct? In my understanding, drivers are installed but somehow i can't get to boot

@timokasper
Copy link
Collaborator

are you using an original ChameleonMini RevG? Then this should be an ATXMEGA128A4U. For other devices please ask the manufacturer.

@nov3mb3r
Copy link
Author

@timokasper As I said in the first issue, I use an original ChameleonMini RevG. I bought it from your workshop in 36c3

@timokasper
Copy link
Collaborator

just to be sure: the chameleon is switched OFF, then you hold the Rbutton, then you switch ON again ; as a result no LED lights up (indicating the bootloader is active) and then you plug in the USB, correct?

@nov3mb3r
Copy link
Author

Correct!

@timokasper
Copy link
Collaborator

grafik

I did the same it looks like this. Windows 10 64 bit.

so for some unknown reason you have a different driver. I had installed a while ago the WinAVR package is that maybe the cause?

@nov3mb3r
Copy link
Author

No I have not installed WinAVR or other packages. I retested in a laptop where I have practically nothing, and I have the same problem

@ceres-c
Copy link
Contributor

ceres-c commented Aug 14, 2020

This might be a bit too barbaric, but I'd give a try with Zadig. Try changing the default driver for the Chameleon to libusb, but PLEASE pay attention to not fu*k up any other device

@nov3mb3r
Copy link
Author

@ceres-c I would appreciate some instructions since I am a total newbie in hardware

@ceres-c
Copy link
Contributor

ceres-c commented Aug 14, 2020

It should be pretty straightforward, you have to select the device you're 100% sure to be the chameleon from the dropdown menu and then pick "libusb" in the selector to the right of the green arrow. Then use the big button "install libusb" (or something like that). The chameleon should then be automatically soft-unplugged from your PC and the device list from device manager will be updated. There you should be able to see something like the output @timokasper has "libusb-win32".
Just be sure to select the right device to force driver update on (the name should be the same as in Device Manager)

@nov3mb3r
Copy link
Author

@ceres-c Interestingly enough, there are no devices to choose apart from my keyboard and mouse! I am starting to suspect that my chameleon might be faulty

@ceres-c
Copy link
Contributor

ceres-c commented Aug 14, 2020

Check the "List all devices" checkbox in options menu

@nov3mb3r
Copy link
Author

I already did that before posting :)

@ceres-c
Copy link
Contributor

ceres-c commented Aug 14, 2020

That's quite strange indeed.
It seems a driver issue to me, since an Atmel device is correctly recognized by windows. Could you try with a linux live iso? I can't help you further since USB issues with this kind of devices were one of the reasons I switched from Win to Linux ass a daily driver :)

@nov3mb3r
Copy link
Author

Will give it a try and make new issues for linux this time if I have problem

@lvandenb
Copy link

lvandenb commented Feb 3, 2022

strange , on my win10 x64 machine , using bootloader on Chameleon , I see no COMport, and there is Atxmega128A4U
image

and when reconnecting i don't see a virtual com port,
image

@david-oswald
Copy link
Collaborator

@lvandenb that looks like expected behavior: the bootloader is a USB device but does not emulate a COM port. The normal firmware shows then up as COM8 in your case.

@lvandenb
Copy link

lvandenb commented Feb 3, 2022

yes , it was only to show a normal/working situation, vs the one on top.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants