The ChameleonMini is a versatile contactless smartcard emulator compliant to NFC. The ChameleonMini was first developed by KAOS. This is NOT the official repo for KAOS's ChameleonMini. For further information see the Getting Started Page
The device appeared on /dev/ttyACM0, then i upgraded the firmware like:
$ sudo avrdude -c flip2 -p ATXMega128A4U -B 60 -P usb -U application:w:Chameleon-Mini.hex:i -U eeprom:w:Chameleon-Mini.eep:i
avrdude: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.00s
avrdude: Device signature = 0x1e9746 (probably x128a4u)
avrdude: NOTE: "application" memory has been specified, an erase cycle will be performed
To disable this feature, specify the -D option.
avrdude: erasing chip
avrdude: reading input file "Chameleon-Mini.hex"
avrdude: writing application (123898 bytes):
Writing | ################################################## | 100% 2.47s
avrdude: 123898 bytes of application written
avrdude: verifying application memory against Chameleon-Mini.hex:
avrdude: load data application data from input file Chameleon-Mini.hex:
avrdude: input file Chameleon-Mini.hex contains 123898 bytes
avrdude: reading on-chip application data:
Reading | ################################################## | 100% 0.72s
avrdude: verifying ...
avrdude: 123898 bytes of application verified
avrdude: reading input file "Chameleon-Mini.eep"
avrdude: writing eeprom (124 bytes):
Writing | ################################################## | 100% 0.03s
avrdude: 124 bytes of eeprom written
avrdude: verifying eeprom memory against Chameleon-Mini.eep:
avrdude: load data eeprom data from input file Chameleon-Mini.eep:
avrdude: input file Chameleon-Mini.eep contains 124 bytes
avrdude: reading on-chip eeprom data:
Reading | ################################################## | 100% 0.01s
avrdude: verifying ...
avrdude: 124 bytes of eeprom verified
avrdude done. Thank you.
which seems ok. but when i try to verify if everything is ok. It doesn't show up anymore into dmesg output. Well, not entierely true. I get:
[98615.909077] usb 5-1.1: New USB device found, idVendor=16d0, idProduct=04b2, bcdDevice= 0.01
[98615.909082] usb 5-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=220
[98615.909084] usb 5-1.1: Product: Chameleon-Mini
[98615.909085] usb 5-1.1: Manufacturer: Kasper & Oswald GmbH
[98615.909087] usb 5-1.1: SerialNumber: 9355438xxxxxxxxxxxxxxxxxx
[98615.962471] cdc_acm 5-1.1:1.0: ttyACM0: USB ACM device
which seems ok, but not. I had the udev rules. But it doesn't help. I don't really figure out what is the meaning of the last line of the dmesg output.
Any idea what is going on?
BTW, ModemManager is not running of my machine:
$ sudo systemctl status ModemManager
● ModemManager.service
Loaded: masked (Reason: Unit ModemManager.service is masked.)
Active: inactive (dead) since Thu 2021-04-15 15:54:44 CEST; 17h ago
Main PID: 40629 (code=exited, status=0/SUCCESS)
CPU: 30ms
Hello,
The device appeared on /dev/ttyACM0, then i upgraded the firmware like:
which seems ok. but when i try to verify if everything is ok. It doesn't show up anymore into dmesg output. Well, not entierely true. I get:
which seems ok, but not. I had the udev rules. But it doesn't help. I don't really figure out what is the meaning of the last line of the dmesg output.
Any idea what is going on?
BTW, ModemManager is not running of my machine:
Any tip to fixe both my Chameleon and proxmark ?