FX3 SDK和FX3 Bootloader之间存在巨大差异

嗨，Lumpi，
这是一个很好的观察。这是我们这边的错误。
启动API设置SPI接口的时钟由用户指定频率的一半。这就是为什么CYFX3BooStudio Word的工作速度较慢。我们将在下一个版本中修复这个问题。请指定当前所需频率的两倍。没有约束检查的cyfx3bootspisetconfig代码，它可能会要求更高的频率。
谢谢，
Sai Krishna。



     以下为原文
  Hi Lumpi,
    That is a very good observation. It is a mistake from our side.
    The Boot API is setting to the SPI interface clock to half of the frequency specified by the user. This is why CyFx3BootSpiReceiveWords works slower. We will get this fixed in the next release. Please specify double the required frequency for now. There is no bound check in the CyFx3BootSpiSetConfig code, and it will be possible to request a higher frequency.
    Thanks,
    Sai Krishna.

HiSai Krishna
非常感谢你的回答，这对我来说是很好的设置频率倍数，太棒了！
但那样做的速度不会那么快。更大的问题是，在两个传输字节之间，在Bootloader LIB的情况下有大约15U的延迟，并且在SDK LIB的情况下，只有一个比特大于1U（看一下我在前一篇文章中添加的PDF文档）。我认为SDK版本的“长”时间（1US）是TyReX OS的结果，但在Bootloader LIB的情况下，我认为没有TraceX正在运行。所以应该快一点！我相信在Bootloader LIB的情况下，使用GPIO API的软件SPI将比引导加载程序LIB的外围SPI快。
你也有一个很好的解决办法吗？那太棒了。
当做，
隆皮



     以下为原文
   Hi Sai Krishna,

    thank you very much for the answer that will be fine for me to set double of frequency, great! 
    But that would not perform that faster then. The bigger issue is, that between two transfer bytes there  is a delay of about 15us in case of bootloader lib and in case of the sdk lib there is just a bit more than 1us (take a look to the pdf document I appended in my previous post). I think the "long" time (1us) of the sdk version is a result of threadx OS but in case of bootloader lib I thought there is no threadx running. So that should be way faster! I believe in case of the bootloader lib a software SPI using the GPIO api will be faster than the peripheral SPI of the bootloader lib.
    Do you also have such a nice workaround for that? It would be awesome.
    regards,
    lumpi

你好，
这有什么更新吗？
谢谢，
隆皮



     以下为原文
  Hi,
    any updates on this?
    thanks,
    lumpi

嗨，Lumpi，
常规API上的单词之间的延迟与thigx无关。由于需要检查各种错误条件等，这只是普通的软件延迟。在引导库中，我们有一个轮询循环，它在状态寄存器的每个检查之间插入一些延迟。这就是为什么在操作之间有很长的潜伏期。我们将解决这个问题和频率问题。我们可以给你一个测试API的下降。
最后，我们将无法获得一个更快的基于GPIO的SPI。CPU可以切换一对GPIOS的最大频率将在10 MHz以下。与FX3GPIOS相比，这是不可能的。
谢谢，
Sai Krishna。



     以下为原文
  Hi Lumpi, 
    The delay between words on the regular API has nothing to do with ThreadX. It is just plain software delays due to the need to check for various error conditions etc. In the boot library, we have a poll loop which inserts some delay between each check of the status register. This is why there is a long latency between operations. We will fix this along with the frequency issue. We can give you a test drop of the API. 
    Finally, we will not be able to get a faster GPIO based SPI. The maximum frequency that the CPU can toggle a pair of GPIOs at will be under 10 MHz. It is not possible to go faster than this with the FX3 GPIOs. 
    Thanks,
    Sai Krishna.

嗨，Sai Krishna，
非常感谢您的大力支持。试卷会很棒，我们怎么交换呢？
最后，我们将无法获得一个更快的基于GPIO的SPI。最大频率
GT可以在10 MHz以下切换一对GPIOS。这是不可能的
和FX3GPIOS相比，这个速度要快一些。
那该告诉我什么？我认为SPI是FX3中的外围硬件接口。你想告诉我，那个外围设备的控制需要GPIO API，因为它是有限的吗？
谢谢，
隆皮



     以下为原文
  Hi Sai Krishna,
    thank you very much for your great support. A test drop would be great, how can we exchange it?
     
    >> Finally, we will not be able to get a faster GPIO based SPI. The maximum frequency
    >> that the CPU can toggle a pair of GPIOs at will be under 10 MHz. It is not possible
    >> to go faster than this with the FX3 GPIOs.
    What should that tell me? I thought the SPI is a peripheral hardware interface in the FX3. Do you like to tell me, that the control of that peripheral needs the GPIO api and because of that it is limited?
    thanks,
    lumpi

嗨，Lumpi，
我会给你发电子邮件，一旦修复准备好了。然后，您可以创建一个支持案例来获得它。
不，我不是在讨论FX3中存在的SPI硬件模块。我用GPIOS来讨论SPI实现。我是说，如果你去GPIO位砰击实现，那么我们不能有更好的性能数字，因为CPU可以切换一对GPIOS将在10兆赫以下。
谢谢，
Sai Krishna。



     以下为原文
  Hi Lumpi,
    I will send you an email once that fix is ready. May be then you can create a support case to get that.
    No. I was not talking about the SPI hardware module present in the FX3. I was talking about SPI implementation using GPIOs. I was saying that if you go for GPIO bit banging implementation then we cannot have better performance numbers because the CPU can toggle a pair of GPIOs at will be under 10 MHz.
    Thanks,
    Sai Krishna.

嗨，Sai Krishna，
实际上我打开了一个支持测试用例交换的例子。
当做
隆皮



     以下为原文
  Hi Sai Krishna,
    I have actually opened a support case to exchange the test drop.
    regards
    lumpi

你好，
只是为了更新大家…
上面列出的所有问题都解决了，这些更改将是下一版本FX3SDK的一部分。
谢谢，
Sai Krishna。



     以下为原文
  Hi,
    Just to update you all...
    All the issues that were listed above are solved and these changes will be part of next release of FX3 SDK.
    Thanks,
    Sai Krishna.

嗨，Sai Krishna，
下一个FX3SDK版本何时发布？
谢谢，
隆皮



     以下为原文
  Hi Sai Krishna,
    when will be the next release of FX3 SDK?
    thanks,
    lumpi

嗨，Lumpi，
我们计划发布在3个星期的时间从现在开始。最有可能的第一周，下个月，如果一切按计划。
谢谢，
Sai Krishna。



     以下为原文
  Hi Lumpi,
     
    We are planning to release it in a time of 3 weeks from now. Most probably first week of next month, if everything goes as per the plan. 
     
    Thanks,
    Sai Krishna.

嗨，Sai Krishna，
很高兴知道，非常感谢。
当做，
隆皮



     以下为原文
  Hi Sai Krishna,
    good to know, thank you very much.
    regards,
    lumpi

嗨，今天终于可以让SPI工作了（经过一周的诅咒）…直到我发现一个愚蠢的错误在我身边）
使用CYSUB3014（DVK板CYSUB3KIT-1001）
最近重新安装到FX3 SDK 1.2.3
-顺便说一句，W7 X64的bug失踪包括路径仍然存在但复制整个柏树文件夹从程序文件程序文件帮助x86 USB枚举在固件uload作品好了：）还有日食后精灵IMG的作品现在建立转换：）我是新来的，如果我不正确的PLE SPIASE指正（通常使用更多的并行接口，但GPIF II不适合我的需求在所有SPI是唯一足够快，周围留下了CYUSB3014芯片的特点）
我试着寻找可能的所以我最后的配置为最佳速度：
cyu3pspiconfig_t spiconfig；spiconfig.isl***first = cyfalse；spiconfig.cpol = cytrue；spiconfig.ssnpol = cyfalse；spiconfig.cpha = cyfalse；/ /只使用零滞后时间spiconfig.leadtime = cy_u3p_spi_ssn_lag_lead_half_clk；spiconfig.lagtime = cy_u3p_spi_ssn_lag_lead_zero_clk；spiconfig。ssnctrl = cy_u3p_spi_ssn_ctrl_fw；spiconfig.clock = 1000000；//这只是暂时对示波器spiconfig.wordlen = 32更准确的测量；cyu3pspisetconfig（&；spiconfig，null）；
经过一些测量，我发现了这个（见SPI.JPG）
SCK运行在双频率现在（不知道这是旧的SDK的情况下）而不是2mhz 1MHz
SPI定时：
转染前的SPI时间
32位字转染16US代替32位
同步间隙2us（铅+ tssnh +滞后时间，我猜的）…这让我很困惑：
1。SSSNCTRL对这个没有影响，…即使SSN控制是不存在的，GAP也是存在的！！！！
2。如果间隙（铅+ tssnh +滞后时间）应该是0 + tssnh + 0.5us。好的，但是TSNNH需要多长时间，我怎样才能改变它呢？数据表明只有tssnh >；= 10ns，这一切。
我发现，我局与SPI工作稳定= 25 MHz的设置SCK其实现在运行在50MHz！！！！（表限制SPI 32MHz或33MHz的的），在30mhz设置（60mhz其实）也是如此，但不稳定…有时不开始。
SPIJJPG
481.8 K



     以下为原文
  Hi , was finaly able to get SPI to work today (after week of lot of cursing ... until i find a stupid bug on my side)
    using CYUSB3014 (DVK board CYUSB3KIT-001)
    recently reinstaled to FX3 SDK 1.2.3
    - btw that w7 x64 bug on missing include path still persist but copy entire cypress folder from Program Files x86 to Program Files help

    - USB enumeration after firmware uload  works fine now :)

    - also Eclipse post build conversion from elf to img works now :)

    I am new to SPI so if i am incorrect please correct me  (usualy using more paralel  interfaces but GPIF II does not suits my needs at all so SPI is the only fast enough peripherial left on CYUSB3014)
    I tryed find the best speed possible so my final config is as this:
    CyU3PSpiConfig_t spiConfig;
spiConfig.isL***First = CyFalse;
spiConfig.cpol = CyTrue;
spiConfig.ssnPol = CyFalse;
spiConfig.cpha = CyFalse;                          // only to use zero lag time
spiConfig.leadTime = CY_U3P_SPI_SSN_LAG_LEAD_HALF_CLK;
spiConfig.lagTime = CY_U3P_SPI_SSN_LAG_LEAD_ZERO_CLK;
spiConfig.ssnCtrl = CY_U3P_SPI_SSN_CTRL_FW;
spiConfig.clock = 1000000;                         // this is only temporary for more acurate measuring on osciloscope
spiConfig.wordLen = 32;
CyU3PSpiSetConfig(&spiConfig,NULL);
 
    after some measuring i found this (see SPI.jpg)
    SCK runs on double frequency now (do not know if this is the case for older SDK) 2MHz instead of 1MHz
    SPI timing :
    SPI init time before transfere 9us
    32bit word transfere 16us instead of 32us 
    synchronisation gap 2us (lead + tssnh + lag time i assume) ... this confuses me a lot:
    1.  ssnCtrl has no  effect on this,... gap is present even if SSN control is NONE !!!
    2. if the gap is  (lead + tssnh + lag time)   then it should be 0+tssnh+0.5us. ok but how long is tssnh and how i can change it? Datasheet says only that tssnh >= 10ns and that is it all.
    Also i find that SPI works stable on my board with seting SCK = 25 MHz  whitch actualy now runs on 50MHz !!! (datasheet limits SPI to 32MHz or 33MHz), on 30MHz setting (60MHz actualy) it works too but not stable ... sometimes do not start.
     
   
 

•   SPI.jpg 481.8 K