The new set of CrossWorks Technology Libraries

Comments

9 comments

  • Avatar
    Tim Rogers

    I noticed USB host and device have entries in the license window. Any time frame on host?

    0
    Comment actions Permalink
  • Avatar
    Paul Curtis

    Not yet.  Certainly not in the near term, perhaps 6 months, depends upon our workload.

    0
    Comment actions Permalink
  • Avatar
    Michael Farnet

    Paul - As you write the manuals you probably wonder if anybody will read this.  Well, I have and they are wonderful.  The run through the examples is great.  I am well on my way on my own board now.  "Thanks" is not enough, but I don't know how to say it any better.

    0
    Comment actions Permalink
  • Avatar
    Paul Curtis

    Thanks for the kind words.  However, more documentation is needed, clearly, but at least you have working examples to start from!  I plan to add some more example code that you can crib from.  The CoreBASIC example is pretty good as an example that shows what you can do with all the software we've thrown into the world...

    0
    Comment actions Permalink
  • Avatar
    Matt

    Hi Paul,

    Like many others, we've ported a common FatFS to an LPC17xx.  We typically are sending small blocks (2048 bytes) to it at a 10 Hz rate.  We have seen cases where about every 10 to 20 seconds we may get a delay of up to 50 milliseconds waiting for the card to confirm a write (typical is a few milliseconds).  This isn't an SPI or other delay, it is waiting for the card response.

    We have considered that we might not be accessing the card in the best manner and that your mass storage library might be an option to solve this.  Do you have any kind of performance data for this library that might push us in that direction?

    Thanks Paul!

    0
    Comment actions Permalink
  • Avatar
    Paul Curtis

    This is typical of an SPI-based card: it will be doing internal garbage collection as part of the erase unit.  You're not sending a whole sector so the card needs to read, erase, write (this is simplified) the new data.  So, nothing for it I'm afraid, it's just the way they work.

    0
    Comment actions Permalink
  • Avatar
    Matt

    Yeah, thought so, but appreciate the confirmation.  We'll probably still look at your tech for future builds, especially the TCP/IP network library.  Thanks Paul...

    0
    Comment actions Permalink
  • Avatar
    John Lagerquist

    Any chance we'll see Vybrid support for the file system and TCP/IP in the near future?

    0
    Comment actions Permalink
  • Avatar
    Dr Danish Ali

    Any chance of integrating the Technology Library documentation into Crossworks?

    Yes I know you get a link to the pdf, but I want to be able to use the Crossworks help search facilities - much the same way we can for standard C, C++, GNU ...

    As you wrote the pdf, it should be relatively easy to generate the appropriate files.

    0
    Comment actions Permalink

Please sign in to leave a comment.