Oh in Diff3 there was also a bug fix for DI=8 and DI=9 handling in PPS process based on observed "unsupported baud rate" message, as well as handling the case where first PPS byte appears to be 00 similar to how ATR ignores initial 00 byte. As part of debugging PPS, printing the PPS REQ/RSP is added.
Min On Thu, Nov 17, 2022 at 9:59 PM Min Xu <min...@min-info.net> wrote: > > Hi Harald > > Thank you for the appreciation. The diff files are extracted from our > vendor svn repository against original 0.5 git release > > Diff1 contains all of the changes that I have previously made against > 0.5 and I believe a majority has been merged. But since I wasn't sure > of the state on the full repository I am including them again. > > Diff2 contains a change to wdt.c to reboot the board on WatchDog > timeout, and also added brownout interrupt handle to also reboot. > They maybe set to reboot in original firmware, but my repository prior > to this change had them indicating the Watchdog timeout by rapidly > blinking the LEDs. Both modes will reboot with different blinking > pattern (possibly hard to tell) > > Diff3 is the majority of Man-in-the-Middle changes. As I mentioned > long ago, there is a difference between the original 1.3/1.4 board vs > our board in that the power relay for vcc-phone into vcc-sim is > enabled by setting a '1' for the 'nPWRFWD' instead of clearing to 0. > I left the pin-name as is so I can vaguely remember this fact. To > actually work, Diff5 is needed. > > Diff4 is just my compulsiveness to clean up the newline format used > throughout. Because a log saved by putty looked like random newlines > are added > > Diff5 fixes the TCK byte in ATR if present and TA3 was modified. > > The two BMPs are part of Diff5 as a documentation of the > Man-in-the-Middle result > > Best Regards > > On Thu, Nov 17, 2022 at 5:00 AM Harald Welte <lafo...@osmocom.org> wrote: > > > > Dear Min, > > > > On Mon, Nov 14, 2022 at 12:04:03PM -1000, Min Xu wrote: > > > I just recently made some changes to my 1.4 firmware to support > > > Man-in-the-Middle modification of ATR because some device apparently > > > changes the Vcc to 1.8v after reading the ATR that indicates the card > > > supports Class C. > > > > Can you please share/publish the related modifications to modify the ATR > > on-the-fly? > > > > Thanks in advance! > > -- > > - Harald Welte <lafo...@osmocom.org> http://laforge.gnumonks.org/ > > ============================================================================ > > "Privacy in residential applications is a desirable marketing option." > > (ETSI EN 300 175-7 Ch. A6)
