SD 0x68“无效开发”错误

你好，合成器，
代码片段看起来很好。
我会尝试复制它并回到你身边。
当做，
斯里达尔



     以下为原文
  Hello Synths,
 
The code snippet looks fine.
I will try to reproduce it and get back to you.
 
Regards,
Sridhar

我怀疑uhs-1卡，我用的是不能够被连接在固定的3.3V。我会尝试与3.3V microSD标准今天。
编辑：不，同样的问题。



     以下为原文
  I suspect that the UHS-1 card which I am using is not able to be interfaced at fixed 3.3V. I will try with a 3.3V microSD standard today.
 
Edit: No, same problem.

合成器，
我已经修改了有你提到的在FX3S FPGA开发板测试参数的FX3海量存储的例子（点击这个http://www.cypress.com/products/ez-u***-fx3s选择组件”选项卡）。
我可以看到它正在正常工作。
请在你的站台上查一下。简要介绍一下你的硬件和软件，用于测试。
让我知道你是检查以下你的API的返回值吗？是否通过JTAG调试或UART调试打印？
A.CuU3PSIbStItIn FPARAMS
CYU3PSIBSTART
CYU3PSI器件
这里是debugprints显示参数查询通过cyu3psibquerydevice API。
----------------------------------------------------------------------------------
在端口0找到了一个设备
类型＝2，NUBLKS＝1006592，EraseSe=＝32768，CKRATER＝24000000
BLKLEN＝512可移除＝1，可写＝1，锁定＝0
DDRMODE＝0，OpValk＝0，总线宽度＝1，NUMNATE＝2
CARCCMDCH类＝1525
开发0、0单元：位置= 0 = 503296 ---------------------------------- numblocks
在端口0找到了一个设备
类型＝2，NUBLKS＝1006592，EraseSe=＝32768，CKRATER
DEV 0：发现用户分区
DEV 0，单元1：位置＝0个数字块＝503232
DEV 0：发现用户分区
DEV 0，第0单元：BLKSIZE＝512 NUBBASIC＝503296
DEV 0，第1单元：BLKSIZE＝512 NUBBASIC＝503232
在端口1找到了一个设备
类型= 2，numblks = 124735488，erasesize = 16777216，clkrate = 24000000
BLKLEN＝512可移除＝1，可写＝1，锁定＝0
DDRMODE＝0，OpValk＝0，总线宽度＝1，NUMNATE＝2
CARCCMDCH类＝1461
DEV 1，单元0：位置＝0个数字块＝62367744
DEV 1：发现用户分区
DEV 1，单元1：位置＝0个数字块＝62367680
DEV 1：发现用户分区
DEV 1，第0单元：BLKSIZE＝512 NUBBASIC＝62367744
DEV 1，第1单元：BLKSIZE＝512 NUBBASIC＝62367680
调用USB连接
接收USB事件0
完成USB设置配置
-----------------------------------------------------------------------------------------------------------------------------------------
FX3SMASTSTARG.RAR
511.3 K



     以下为原文
  Synths,
 
I have modified the FX3 Mass Storage example provided with the parameters you mentioned above and tested on the FX3S FPGA Development board (Click this http://www.cypress.com/products/ez-u***-fx3s  and select Kits Tab).
 
I can see that it is working as expected.
 
Please check this on your platform. Brief us about your hardware and software that are using for testing.
 
Let me know how you are checking the return values of the following APIs in your case? is it through JTAG Debugging or UART Debug Prints?
          a. CyU3PSibSetIntfParams
          b. CyU3PSibStart
          c. CyU3PSibQueryDevice
 
Here is the debugprints shows the parameters queried through CyU3PSibQueryDevice API.
----------------------------------------------------------------------------------
Found a device on port 0
        Type=2, numBlks=1006592, eraseSize=32768, clkRate=24000000
        blkLen=512 removable=1, writeable=1, locked=0
        ddrMode=0, opVoltage=0, busWidth=1, numUnits=2
        cardCmdClass=1525
Dev 0, Unit 0: location=0 numBlocks=503296----------------------------------
Found a device on port 0
        Type=2, numBlks=1006592, eraseSize=32768, clkRate
Dev 0: Found user partition
Dev 0, Unit 1: location=0 numBlocks=503232
Dev 0: Found user partition
Dev 0, Unit 0: blkSize=512 numBlocks=503296
Dev 0, Unit 1: blkSize=512 numBlocks=503232
Found a device on port 1
        Type=2, numBlks=124735488, eraseSize=16777216, clkRate=24000000
        blkLen=512 removable=1, writeable=1, locked=0
        ddrMode=0, opVoltage=0, busWidth=1, numUnits=2
        cardCmdClass=1461
Dev 1, Unit 0: location=0 numBlocks=62367744
Dev 1: Found user partition
Dev 1, Unit 1: location=0 numBlocks=62367680
Dev 1: Found user partition
Dev 1, Unit 0: blkSize=512 numBlocks=62367744
Dev 1, Unit 1: blkSize=512 numBlocks=62367680
Calling USB Connect
USB event 0 received
USB Set Config completed
-----------------------------------------------------------------------------------------------------------------------------------------

•   FX3SMassStorage.rar 511.3 K  
  
  

感谢您在FX3S SDK上验证此代码。
在将初始化和查询代码从AppnIIT初始化函数移动到我的循环线程之后，我才能够成功地查询设备。我有三个理论来解释为什么这能奏效：
初始化和查询依赖于init码幂竞争的其他方面的时间要求
而且，既然你问了，我乐于分享，我有一个在FPGA触摸屏的驱动，我用调试（下）。



     以下为原文
  Thank you for verifying this code on the FX3S SDK.
 
I was able to successfully query the device only after moving the initialization and query code from ApplnInit initialization function to my looping thread. I have three theories as to why this could have worked:
 

• Time requirement between initialization and query
  
• Reliance upon some other aspect of init code
  
• Power competition
  

 
And, since you asked, I am happy to share that I have an onboard FPGA-driven touchscreen, which I am using for debug (below).