emFILE用于内部FLASH

HyMig是一个好主意，使用EMFLASH系统和USB EMFLE系统可以管理巨大的数据，当连接到PC主机时，你可以传输这些数据。我一直使用EMFLID+USB，这很好。顺便说一下，我不明白你想要什么，通常，通过SPI接口使用SD微盘的文件系统，我不知道它可以用内部闪存，也许不是我从来没有听说过，并且认识到大容量存储需要USB的大容量存储协议。我不知道如何使用SD或内部闪存。谢谢您。



     以下为原文
          Hi tiny   
It's a good idea to using emFile system and USB   
EmFile system can manage huge data and   
when connect to the PC Host, you can transfer these data.   
   
i have been using emFile+USB, that working quite good.   
Btw, I don't understand what you want to,   
Usually, emFile system using SD micro disk via SPI interface   
I don't know that can use with internal flash memory, maybe NOT   
I didn't heard that ever   
And to recognize as mass storage is needs Mass Storage protocol of USB.   
I don't know how to do with SD or Internal flash.   
Thank you.   

将EMFLAMP组件用于与外部EXALL SD卡一起使用。这意味着它不能很好地利用内部存储。你应该看看EEPROM组件（或者仿真EEPROM组件，但是确保你在这个版本的最新版本）。
为了存储，我建议你定义一个你需要存储的定义。定义一个“C结构”，因此每个条目都有一个固定长度的记录（如果可能的话，它的大小是16的倍数）。然后，您可以创建新条目，并将它们存储到EEPROM中。



     以下为原文
  The emFile component is intented to be used with _external_ SD cards. This means it won't play well with internal storage. You should look maybe at the EEPROM component (or the emulated EEPROM component, but make sure you are at the latest version with this one).
    For storage, I suggest you come up with a definition what you need to store. Define a 'C struct', so you get a fixed length record for each entry (if possible make it so its size is a multiple of 16). Then you can create new entries, and store them into the EEPROM.

使用内部闪存的其他考虑因素
1）您的总写入速率为每行15毫秒，行＝256字节。
您可以写一行，但这会告诉您有效的写入时间，这是
总测量推送率。
2）闪速写周期限制为10K周期，85℃EEPROM，
如果你能忍受2KB限制，IS



     以下为原文
  Some other considerations using internal FLASH -
     
    1) Your overall write rate is min of 15 mS per row, a row = 256 bytes.
    You can write < a row, but this tells you effective write time, which sets
    overall measurement thruput rate.
     
    2) FLASH write cycle limitation is 10K cycles, 85 degrees C. EEPROM,
    if you can live with 2KB limitiation, is -
     
     

我刚刚发现这一点：
HTTP://www. CyPress？COM/？RID＝3091
这似乎解释了USB CDC类的驱动程序的情况（微软本身支持它，但是我必须提供.INF文件来告诉Windows在哪里查看，这个INF文件是由创建者在构建过程中生成的）
它也有一些有用的信息，通过一个UBUTACT连接发送大量（和64字节）的数据。
我建议更新的计划是在故障发生时在EEPROM中以一种设置格式存储数据，并且当我通过USB接口接收到某个命令时，然后通过UsBART发送数据。然后，我可以使用终端存储这一切到CSV文件（我想），并将其读入Excel。
用FAT16／32格式化来解决问题听起来更为可行。你怎么认为？
还感谢有关闪存寿命的信息，我将记住，当我写这些缓冲器。
汤姆



     以下为原文
  I have just found this:
    http://www.cypress.com/?rID=3091
    Which seems to explain the driver situation of the USB CDC class (Microsoft natively supports it, but I must supply an .INF file to tell Windows where to look, and this INF file is generated by Creator during the build)
    It also has some useful information about sending large amounts (>64bytes) of data over a USBUART connection.
    I supose the updated plan would be to store the data in a set format in the EEPROM when a fault occurs, and when I receive a certain command over the USB interface then send the data over USBUART. I can then use the terminal to store this all to a csv file (I think) and read it into Excel.
    That sounds much more feasible that messing around with FAT16/32 formatting. What do you think?
    Also thanks for the info about the flash life expectancy, I shall remember that when I am writing these buffers.
    Tom

如果整个事情都是关于调试的，为什么不使用EMFLAMP组件作为它的意图呢？只是把你的东西作为一个文本文件（或CSV）登录到卡。当出错时，只需在PC上读取该卡，就可以得到一个完美的调试日志。唯一的缺点：写小卡片的数据到卡片会很慢…



     以下为原文
  If this whole thing is about debugging, why not using the emFile component as its intended? Just log your stuff out as a text file (or CSV) to the card. When something goes wrong, just take the card and read it in the PC, and you have a perfect debug log. Only drawback: writing small packats of data to the card will be slow...

这将是理想的，因为它是关于调试，但我们不能有一个SD卡在董事会由于各种环境问题，不幸的是。
再次感谢大家的帮助，我现在来看看UBUTART，并努力让它工作。
汤姆



     以下为原文
  That would be ideal as it is about debugging, but we are cannot have an SD card on the board due to various environmental issues, unfortunately.
    Thanks again for all of your help everyone, I'm having a look at the USBUART now and attempting to get it to work.
    Tom