Some ongoing notes trying to understand what the iCopy-X is made of, what's the current state and what could be done once the software gets fully open-sourced.
=> 
I want to warmly thank @gator96100 for sharing his own finding that are being merged over time in this repo as well!
Links mentioned in the documentation and in social networks
- iCopy-X on Facebook
- iCopy-X on Twitter
- iCopy-X on WeChat ?? Cannot find it.
- iCopy-X on Kickstarter
- https://icopy-x.com/
- https://www.icopy-x.com/warranty (not yet online as of 06/2021)
- https://www.icopy-x.com/support (not yet online as of 06/2021)
- https://www.icopy-x.com/updates a form where you need to provide your serial number as apparently firmwares are diversified per device.
- team@icopy-x.com => product level
- Nikola T. Lab Youtube channel
- Nikola T. Lab on TikTok
- Nikola T. Lab on Twitter
- https://www.nikola-lab.com/ (not yet online as of 06/2021)
- team@nikola-lab.com => distributorship
2021-07 UPDATE
Source of Proxmark3 and FGPA have been recently released together with the electric schematics.
Experiments on these sources are conducted in separate repositories.
We're still missing the STM32 and the Python application details to be able to develop on the iCopy-X interface.
Most teardown observations predate the source release.
So far, major observations are the following.
iCopy-X is based on Proxmark3 and a NanoPi NEO embedded Linux to run the client side. It contains an additional Python wrapper to provide a user interface with LCD and buttons.
- Proxmark3 has an external flash like RDV4 but no smartcard reader
- Proxmark3 FPGA is a larger model XC3S100E than the usual XC2S30
- Proxmark3 runs a modified version of RRG/Iceman repo circa September 2020 (forked from 29c8b3aa4ee8cb3d66a1542d95740d996abe201f)
- ARM firmware got modified at least to deal with the new FPGA image and to remove version information
- FPGA image got modified to merge lf, hf and felica images
fpga_compressgot modified to allow larger image (#define FPGA_CONFIG_SIZE 72864L)- client for NanoPi got modified at least to return error codes, to deactivate history and logs and to remove version information
- client for Windows got modified at least to return error codes and to remove version information
- UPDATE: full diff here
- How firmwares are tied to serial numbers? cf version.so
- Are cards really tied to icopy-x? If yes, how?
- Is the antenna LED drivable?
- LED screen drivable by both STM32 and NanoPi?
- Non-PC Mode: is there any usage of /dev/ttyACM0 when untied to ?
- Open the source code of STM32 and most of the Python application such that it could be properly maintained up to date with the RRG/Iceman and its GUI maintained properly as well
- Bind the UART-to-USB bridge to the Linux Debug console when in non-PC-Mode, it's much more convenient than using the inner UART1