为什么ST25R3911第二个APDU命令后没有响应？

嗨马吕斯，
是的，你不应该尝试重新激活卡。
不确定发生了什么，但有一些想法可以获得更多信息：
 我假设您将激活期间收到的参数（rfalIsoDepDevice-＆gt; DID，FWT，dFWT和FsX）输入rfalIsoDepApduTxRxParam？你的错误变量的值是什么 - 当它既不是ERR_None也不是ERR_Busy？Hal_Delay（20）太大，如果收到的APDU大于90 + x字节那么这将溢出ST25R3911BRegards的FIFO，尤利西斯



以下为原文




Hi Marius,
yes, you should not try to reactivate the card.
Not sure what is happening but a few ideas for more information:

• I assume you feed in the parameters received during activation (rfalIsoDepDevice->DID,FWT,dFWT and FsX) into the rfalIsoDepApduTxRxParam ?
  
• What is the value of your err variable - when it is neither ERR_None nor ERR_Busy?
  
• The Hal_Delay(20) is too large, if the received APDU is larger then some 90+x bytes then this will overflow the FIFO of ST25R3911B
  

Regards, Ulysses

嗨尤利西斯
谢谢您的回复。
是的，激活后我使用从tfalIsoDepDevice返回的参数
错误=
rfalIsoDepPollAHandleActivation（RFAL_COMPLIANCE_MODE_NFC_11，RFAL_ISODEP_FSXI_512，RFAL_ISODEP_NO_DID，RFAL_BR_424，
＆安培; isoDepDevice
）;
myParam.DID = RFAL_ISODEP_NO_DID;
//isoDepDevice.info.DID; //
 
 myParam.FWT = isoDepDevice.info.FWT;
 
 myParam.dFWT = isoDepDevice.info.dFWT;
 
 myParam.FSx = isoDepDevice.info.FSx;
 
 myParam.ourFSx = RFAL_ISODEP_FSX_KEEP;
myParam.txBuf =＆amp; apduCommand;
 
 myParam.txBufLen = apduTxLen;
 myParam.rxBufLen =＆amp; apduRxLen;
 myParam.rxBuf =＆amp; apduResponse;在向卡发送第二个APDU时：
当我发送err = rfalIsoDepStartApduTransceive（myParam）时，我得到No error;
我使用'for'例程运行（35次。我后来将其更改为350次）以获得Transceive状态。
所以经过350次调用rfalWorker（）;和rfalIsoDepGetApduTransceiveStatus（）;
在350个循环后我仍然得到ERR_BUSY。 （我对第二个APDU命令的响应应该与我发送的第一个apdu命令的大小相同或更大）
我已经用HAL_Delay（1）的延迟改变了我的循环并且重试了2000（TIMEOUT = 2000）
for（int i = 0; i＆lt; TIMEOUT; i ++）
 
 {
 
 
 
 err = rfalIsoDepGetApduTransceiveStatus（）;
//检查APDU Transceive的状态
 
 HAL_Delay（1）;
 
//运行RFAL Worker
 
 rfalWorker（）;
 
 if（err == ERR_NONE）
 
 {
 
 logUsart（'APDU Transceive Success  r  n'）;
 
 rfalWorker（）;
 
 HAL_Delay（1）;
 
 打破;
 }
 
 HAL_Delay（1）;
 
 if（err == ERR_BUSY）
 
 {
 
 
// logUsart（'。'）;
 
 }
 
 }
//用于循环结束
 
 logUsart（'AID接收缓冲区有％d字节 r  n'，apduRxLen）;
 if（apduRxLen＆gt; 0）
 {
 logUsart（'Rx数据：％s  r  n'，hex2Str（apduResponse.apdu，apduRxLen））;
 为了确保，我在发送第二个APDU命令之前在Param结构中再次编写了所有参数。
 myParam.txBuf =＆amp; apduCommand; //＆amp; apduCommand;
 
 myParam.txBufLen = apduTxLen;
 
 myParam.rxBufLen =＆amp; apduRxLen;
 
 myParam.rxBuf =＆amp; apduResponse;
 
 myParam.DID = RFAL_ISODEP_NO_DID; // isoDepDevice.info.DID; //
 
 myParam.FWT = isoDepDevice.info.FWT;
 
 myParam.dFWT = isoDepDevice.info.dFWT;
 
 myParam.FSx = isoDepDevice.info.FSx;
 
 myParam.ourFSx = RFAL_ISODEP_FSX_KEEP;
但是仍然没有对第二个apdu命令做出响应（同样，我在时间问题的情况下从ERR_BUSY中删除了USART写入命令）但是仍然在ERR_BUSY上。



以下为原文




HI Ulysses
Thank you for your reply.
Yes, After Activation I use the parameters returned from tfalIsoDepDevice
err =
rfalIsoDepPollAHandleActivation(RFAL_COMPLIANCE_MODE_NFC_11,RFAL_ISODEP_FSXI_512,RFAL_ISODEP_NO_DID,RFAL_BR_424,
&isoDepDevice
);
myParam.DID = RFAL_ISODEP_NO_DID;     
//isoDepDevice.info.DID; //

myParam.FWT = isoDepDevice.info.FWT;

myParam.dFWT = isoDepDevice.info.dFWT;

myParam.FSx = isoDepDevice.info.FSx;

myParam.ourFSx = RFAL_ISODEP_FSX_KEEP ;
myParam.txBuf = &apduCommand;

myParam.txBufLen = apduTxLen;
myParam.rxBufLen = &apduRxLen;
myParam.rxBuf = &apduResponse;On Sending a Second APDU to the Card :
I get No error when I transmit err = rfalIsoDepStartApduTransceive(myParam);
I Use a 'for' routine that runs ( 35 times.  I later changed it to 350 times) to get the Transceive status.
So after 350 times calling the rfalWorker(); and rfalIsoDepGetApduTransceiveStatus();
I still get ERR_BUSY after the 350 cycles. ( My response for the second APDU Command should be more or the same size as the first apdu command that I have sent)
I have changed my loop with a delay of HAL_Delay(1) and retries of 2000 ( TIMEOUT = 2000)

for (int i=0;i
{

         

          err = rfalIsoDepGetApduTransceiveStatus();
//Check The Status of the APDU Transceive

          HAL_Delay(1);
         
// Run the RFAL Worker

          rfalWorker();

          if (err == ERR_NONE)

          {

                   logUsart('APDU Transceive Successrn');

                   rfalWorker();

                   HAL_Delay(1);

                   break;

           }

          HAL_Delay(1);

          if (err == ERR_BUSY)

          {

                 
//  logUsart('.');

          }

}  
// for loop end


logUsart('AID Receive Buffer have %d Bytesrn',apduRxLen);
if (apduRxLen > 0)
{
       logUsart('Rx Data: %srn',hex2Str(apduResponse.apdu,apduRxLen));
}Just to be sure, I have written the all parameters again in the Param struct before sending the second APDU comand.

myParam.txBuf = &apduCommand;// &apduCommand;

myParam.txBufLen = apduTxLen;

myParam.rxBufLen = &apduRxLen;

myParam.rxBuf = &apduResponse;

myParam.DID = RFAL_ISODEP_NO_DID;//isoDepDevice.info.DID; //

myParam.FWT = isoDepDevice.info.FWT;

myParam.dFWT = isoDepDevice.info.dFWT;

myParam.FSx = isoDepDevice.info.FSx;

myParam.ourFSx = RFAL_ISODEP_FSX_KEEP ;
but still no response on the second apdu command, ( also,I removed the USART Write command from ERR_BUSY in case of timing issues)  but stays on ERR_BUSY.

嗨马吕斯，
看起来像司机的状态机没有前进。也许在中断移植中存在问题。你能拿一个万用表测量ST25R3911B的INT引脚吗？如果它很高，那么ISR不会被执行。
问候，尤利西斯



以下为原文




Hi Marius,
looks like the state machine of the driver is not advancing. Maybe an issue in the interrupt porting. Can you grab a multimeter and measure the INT pin of ST25R3911B? If it is high then the ISR is not exexuted.
Regards, Ulysses

嗨尤利西斯。谢谢。
我将在SPI Pins和INT Pin上连接我的逻辑分析仪，看看发生了什么。
因为向卡发送和接收第一个APDU是好的，这很奇怪，但是当我尝试向卡发送另一个命令时，我没有得到任何回复（ERR_BUSY）。



以下为原文




Hi Ulysses. Thank you.
I will connect my logic analyser on the SPI Pins and INT Pin to see what is happening.
Cause it is strange that sending and receiving the first APDU to the card is good, but as soon as I try to send another command to the card I get no response back (ERR_BUSY).