Other Parts Discussed in Thread: MSP430F2370, TRF7970A, DLP-7970ABP, MSP430G2553
Hello All,
I am using the Hardware combination MSP-EXP430G2ET + DLP7970ABP (V4.7) for Mifare classic authentication process.
I used the sample code SLOC297C. With this the Anti-collision process is executed successfully and I can read the UID of the Mifare classic 4K tag.
To this sample code I ported the SDM code from SLOA214 for adding the Authentication functionality. But the Authentication process is not successful. The code is blocked indefinitely in the "Mifare_DM1_Recieve()" while waiting for the (SDM_BITCLK rising edge) response from the tag. While debugging I suspected that the data is not transmitted properly and hence there is no response from the Tag.
Therefore, I enabled the interrupt for the "SDM_BITCLK" to check the Mifare_SDM_Transmit() function. After enabling the interrupt, I could see continuous interrupts in the line and it is not reliable. I also verified that this is not due to porting but it happens with the SLOC297C code itself. But still (when the interrupt is disabled) the anti-collision process is successful but the authentication process blocked. I hope the reason for this is, only in authentication process (SDM mode) the P1.3(SDM_BITCLK) is used but not during anti-collision process. I observe that this interrupt starts as soon as the TRF79xxA_turnRfOn() function is executed without writing other register settings.
Please help me to solve my issue. Hope I made the necessary changes. Let me know if I am missing something.
I didn't modify the clock configuration in SLOC297C. Not sure whether this issue is related to clock settings. Also, by default, R5 and R7 is unmounted in MSP-EXP430G2ET. Hope there is no need to use the external crystal.
Changes made to MSP-EXP430G2ET are,
- Enabled HW UART in J101,
- Opened J7,
- Opened J6,
- Removed R6.(Removed R6 only after facing this issue, thinking pull up on switch button is causing the above problem. But same behavior with and without R6).
Please let me know if any other HW change is required.
Thanks and Regards,
Skumar