You are right on the statement ” I strongly believe something on main application is bugging down to this issue.” and since Coercion Dot appears in your sample, your main application also has that capability. Even the program works yesterday, there is no assurance it would work tomorrow if we don’t know the real cause of it.
I believe that the Dot is the only clue to solve this issue, which is not acceptable from the software security view point.
Also I have another issue with the SPI protocol of the AAS33001. The protocol is one of standard and it uses duplex operation mainly.
So that I need SPIMaster_SingleReadWrite definitely. If you wouldn’t develop this function, I have to move another option.
Regards,
Masao