Search

Technical Discussion Group Forum

This forum is provided for user discussion. While Beacon EmbeddedWorks support staff and engineers participate, Beacon EmbeddedWorks does not guarantee the accuracy of all information within in the Technical Discussion Group (TDG).

The "Articles" forums provide brief Articles written by Beacon EmbeddedWorks engineers that address the most frequently asked technical questions.

To receive email notifications when updates are posted for a Beacon EmbeddedWorks product download, please subscribe to the TDG Forum of interest.

TDG Forum

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 15 May 2013 08:33 AM by  products_apps@logicpd.com
Flash blocks corruption while reading data
 1 Replies
Sort:
You are not authorized to post a reply.
Author Messages
jduran@gem-med.com
New Member
New Member
Posts:79


--
18 Apr 2013 03:33 AM
    Dear all,

    I run linux in the DM3730 torpedo module with file system stored in a yaffs partition. I test the performance of the CPU to read data from a USB CDC ACM device. The application JUST reads the data from the device but it DOESN'T stores the data in the file system. The USB device sends data at a rate of 888000 bytes per second. When the application is running the following traces appears in the console:

    Quote:

    [ 100.138488] cdc_acm 2-1.2:1.0: This device cannot do calls on its own. It is not a modem.
    [ 100.147460] cdc_acm 2-1.2:1.0: ttyACM0: USB ACM device
    491
    [ 103.850280] omap_device: omap_i2c.1: new worst case deactivate latency 0: 183105
    [ 106.157867] yaffs: **>> Block 1173 needs retiring
    [ 106.167938] yaffs: **>> Block 1174 needs retiring
    [ 106.176147] yaffs: **>> Block 1175 needs retiring
    [ 106.185333] yaffs: **>> Block 1176 needs retiring
    [ 106.191925] yaffs: **>> Block 1177 needs retiring
    [ 106.202697] yaffs: **>> Block 1178 needs retiring
    [ 106.210327] yaffs: **>> Block 1179 needs retiring
    [ 106.216674] yaffs: **>> Block 1180 needs retiring
    [ 106.225738] yaffs: **>> Block 1181 needs retiring
    [ 106.232116] yaffs: **>> Block 1182 needs retiring
    [ 106.239349] yaffs: **>> Block 1183 needs retiring
    [ 106.249542] yaffs: **>> Block 1184 needs retiring
    [ 106.256927] yaffs: **>> Block 1185 needs retiring
    [ 106.263336] yaffs: **>> Block 1186 needs retiring
    [ 106.272949] yaffs: **>> Block 1187 needs retiring
    [ 106.280487] yaffs: **>> yaffs write required 16 attempts
    [ 130.248229] yaffs: **>> Block 1173 retired
    [ 130.252655] yaffs: Block 1173 is in state 9 after gc, should be erased
    [ 132.256072] yaffs: **>> Block 1174 retired
    [ 132.260498] yaffs: Block 1174 is in state 9 after gc, should be erased
    [ 134.263854] yaffs: **>> Block 1175 retired
    [ 134.268280] yaffs: Block 1175 is in state 9 after gc, should be erased
    [ 136.271453] yaffs: **>> Block 1176 retired
    [ 136.275878] yaffs: Block 1176 is in state 9 after gc, should be erased
    [ 138.279449] yaffs: **>> Block 1177 retired
    [ 138.283874] yaffs: Block 1177 is in state 9 after gc, should be erased
    [ 140.287322] yaffs: **>> Block 1178 retired
    [ 140.291748] yaffs: Block 1178 is in state 9 after gc, should be erased
    [ 142.295196] yaffs: **>> Block 1179 retired
    [ 142.299621] yaffs: Block 1179 is in state 9 after gc, should be erased
    [ 144.302978] yaffs: **>> Block 1180 retired
    [ 144.307403] yaffs: Block 1180 is in state 9 after gc, should be erased
    [ 146.310638] yaffs: **>> Block 1181 retired
    [ 146.315063] yaffs: Block 1181 is in state 9 after gc, should be erased
    [ 148.318511] yaffs: **>> Block 1182 retired
    [ 148.322937] yaffs: Block 1182 is in state 9 after gc, should be erased
    [ 150.326416] yaffs: **>> Block 1183 retired
    [ 150.330841] yaffs: Block 1183 is in state 9 after gc, should be erased
    [ 152.334167] yaffs: **>> Block 1184 retired
    [ 152.338592] yaffs: Block 1184 is in state 9 after gc, should be erased
    [ 154.342193] yaffs: **>> Block 1185 retired
    [ 154.346618] yaffs: Block 1185 is in state 9 after gc, should be erased


    Which is the reason of the behavior?

    Joaquim Duran
    products_apps@logicpd.com
    New Member
    New Member
    Posts:


    --
    15 May 2013 08:33 AM
    Which USB port are you using? Try using the USB OTG port instead. Are you testing this on our baseboard? Have you modified the timings for the NAND or USB host chip?
    You are not authorized to post a reply.