LeafLabs Garden

A place to share, learn, and grow...

1. 

   poslathian
   LeafLabs

   gke - regarding you post about good old makefiles - we could not agree more. The IDE and the maple "toolchain" are pretty decoupled, and you can use Maple just as effectively using make + your favorite editor. Check out http://leaflabs.com/docs/unix-toolchain.html

   Regarding the overhead associated with this or that call (like digitalWrite). We went as far as we thought reasonable in stripping out random overhead. For example, on some platforms calls to digitalWrite check the pinMode and other crap every time. But at the end of the day, the wirish library, which is the high level Arduino stuff, is designed for usability. The lightweight, powerful stuff is underneath in a library called libmaple, which you are more than welcome to use!

   Feel free to browse all the code here: http://github.com/leaflabs/libmaple/

   Posted 4 years ago #
2. 

   gke
   Member

   Thanks poslathian. Still tunneling into the libraries etc but I was trying to stay up in the IDE layer otherwise I may as well just drop all the way down to the STM libraries.

   @gbulmer. Yes it was the software I2C/Wire I was interested in. The revised Wire.{cpp,h} are running at 400KHz with gpio calls and at about 280KHz with digital read/writes. Not interested in the I2C hardware as my app has nothing else to do while reading sensors etc.

   Hopefully another iteration today. Other duties are distracting me :).

   Greg

   Posted 4 years ago #
3. 

   gke
   Member

   http://www.eganfamily.id.au/Family/Misc/Wire.zip

   The pulse timing probably needs some checking but later ...

   Posted 4 years ago #
4. 

   crenn
   Moderator

   Unfortunately, the I2C on STM32F1xx is a bit weird. If you glance at the Revision History at the back of the RM0008 manual for the STM32F1xx, pretty much every one of the 14 document revisions contain changes and clarification on the I2C peripheral. I think Crenn is very likely the most knowledgeable I2C contributor, ahead of the official library.

   Perry is possibly the best one to talk to about I2C as he did the low level I2C implementation I do believe which is what I'm using. I don't fully understand the limitations of the I2C peripheral as I haven't read through the the errata sheet fully.

   I also haven't been around as moving out is taking longer than I thought and now that I'm mostly moved out (there is a bit more coming this weekend which signals the end of the 'big move'), I'll be getting around to trying to rewrite the Wire implementation, although I'll probably be referring back to this thread when the Software Wire implementation is completed.

   Posted 4 years ago #
5. 

   gke
   Member

   Thanks. I will probably step back a bit from the Wire stuff to get board maps and STM32F4 stuff done. I will update (10 minutes) the Wire.zip file which now uses PIN_MAP rather than the explicit pin numbers. Still ugly but better than it was. The i2c routines probably should be in their own class but ....

   Greg

   Posted 4 years ago #
6. 

   crenn
   Moderator

   Hi gke,

   I've been working on the new Wire library lately and I'm wondering if I can pull some of your changes into the software side of the library, mainly to speed up the library (and fix some issues). Not sure if you're still around the forums, but I'll see if I can't grab your attention via youtube as well.

   Regards,
   crenn.

   Posted 3 years ago #

RSS feed for this topic

Reply

You must log in to post.