Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Binary characters in output of IDENTIFY #24
I have a "garbled" output before and after CONFIG= and IDENTIFY
I do not understand your question regarding local logging. I use minicom on linux and enable "local echo" by "Ctrl-A-E". Usually I also activate "line wrap" with Ctrl-A-W. All the commands of minicom can be found in the menu "Ctrl-A-Z"
the rest is just copy&paste ;-)
the "garbled" output of the chameleon looks like uncleared output buffers or a read/write out of memory bounds (fencing issue), because it changes every time I execute it or debug output.
Oh, LOGMODE=OFF to the rescue! It was set to LOGMODE=LIVE during my experiments (not that I remember actually setting it). That setting produced the garbled extra bytes during set UID=12345678 and CONFIG=MF_14443A_READER or IDENTIFY!
Wit LOGMODE=OFF the extra bytes are gone.
For the chamtool.py to work properly it assumes LOGMODE=OFF or MEM. It should therefore
Otherwise it will choke over all "extra" bytes sent by the chameleon, as in my case!
I can make a pull request, what should I implement a), b) or c)?