I migrated from several other M3 vendor-specific IDEs to mbed cause the cloud community seems so productive. However, this also has its drawbacks!
My problem seems simple: read a GPS receiver binary data stream (several 1000 bytes per sec), do a minimal amount of parsing of the binary data to engineering units, and then write the data to a SD card. Reading the data was easy, setting up the SD card was easy, and debug across the USB serial link was easy.
However, when I cranked up the data rate above 2000 bytes per sec, I began to see the occurrence of missed bytes. So I switched to the MODSERIAL library to get some built-in buffering. There I first noticed that there were several MODSERIAL libraries that seemed to be off-shoots to do different things. It wasnt clear which to use. And also the MODSERIAL library requires the FATFileSystem Library that also has many versions. In fact, some combinations will not allow my code to compile. A bit of trial and error is required. So its a bit of a struggle to maintain a consistent development pattern. Right now I am at a dead end cause I just cant get the MODSERIAL to work. I have posted questions on how to procede there so hopefully I can get out of my current dead end.
I also know that I will require some threads to get the serial read and SD write to work correctly. So I moved to the mbed-rtos library. That is: libraries .. many of them. Again, a lot of trial and error to get things to compile. As of this moment, everytime I add the rtos library, my serial read functionality stops working. Posted questions there as well to see if I can sort this out.
Bottom line is that the crowd development is great. But there needs to be some way to vet the stuff that gets posted. For me, working with any new libraries is a scary proposition!
I migrated from several other M3 vendor-specific IDEs to mbed cause the cloud community seems so productive. However, this also has its drawbacks!
My problem seems simple: read a GPS receiver binary data stream (several 1000 bytes per sec), do a minimal amount of parsing of the binary data to engineering units, and then write the data to a SD card. Reading the data was easy, setting up the SD card was easy, and debug across the USB serial link was easy.
However, when I cranked up the data rate above 2000 bytes per sec, I began to see the occurrence of missed bytes. So I switched to the MODSERIAL library to get some built-in buffering. There I first noticed that there were several MODSERIAL libraries that seemed to be off-shoots to do different things. It wasnt clear which to use. And also the MODSERIAL library requires the FATFileSystem Library that also has many versions. In fact, some combinations will not allow my code to compile. A bit of trial and error is required. So its a bit of a struggle to maintain a consistent development pattern. Right now I am at a dead end cause I just cant get the MODSERIAL to work. I have posted questions on how to procede there so hopefully I can get out of my current dead end.
I also know that I will require some threads to get the serial read and SD write to work correctly. So I moved to the mbed-rtos library. That is: libraries .. many of them. Again, a lot of trial and error to get things to compile. As of this moment, everytime I add the rtos library, my serial read functionality stops working. Posted questions there as well to see if I can sort this out.
Bottom line is that the crowd development is great. But there needs to be some way to vet the stuff that gets posted. For me, working with any new libraries is a scary proposition!