Hello,
before my Breakout arrives I have few questions:
- so shield uses SPI module; this is interrupt driven?
- shield also occupies USART for debugging; can I disable this?
- it uses timers?
- how much flash, eeprom uses minimalistic (f.e. build_test) project?
- how much memory uses CC3000 driver?
- in sources I saw CC3000_TINY_DRIVER, where it is documented?
- I am totally unfamiliar with Arduino IDE, sketches; can I use CC3000's library with normal gcc toolchain (ANSI C, makefiles,...)?
P.S. sorry for bad English.
CC3000 resources
Moderators: adafruit_support_bill, adafruit
Please be positive and constructive with your questions and comments.
- adafruit_support_rick
- Posts: 35092
- Joined: Tue Mar 15, 2011 11:42 am
Re: CC3000 resources
The CC3000 library is interrupt-driven
You don't have to use the USART
Hmmm ... I don't recall seeing any timer code in there.
Compiling buildtest reports the following:
I doubt that you can use the unmodified driver library with the normal gcc toolchain. It will have arduino dependencies. It might not be particularly difficult to modify - I don't know.
You don't have to use the USART
Hmmm ... I don't recall seeing any timer code in there.
Compiling buildtest reports the following:
If I remove everything but CC3000 driver initialization from the sketch, I get a pretty good estimate of the compiled size of the driver itself:Sketch uses 19,296 bytes (59%) of program storage space. Maximum is 32,256 bytes.
Global variables use 788 bytes (38%) of dynamic memory, leaving 1,260 bytes for local variables. Maximum is 2,048 bytes.
I don't know anything about the Tiny Driver. Sorry.Sketch uses 11,672 bytes (36%) of program storage space. Maximum is 32,256 bytes.
Global variables use 616 bytes (30%) of dynamic memory, leaving 1,432 bytes for local variables. Maximum is 2,048 bytes.
I doubt that you can use the unmodified driver library with the normal gcc toolchain. It will have arduino dependencies. It might not be particularly difficult to modify - I don't know.
- valdas
- Posts: 2
- Joined: Tue Dec 03, 2013 12:23 pm
Re: CC3000 resources
Hello,
thanks Rick.
About USART: I want use USART for my own purposes. But if several files of driver (f.e. in dir "utility") have calls to function "DEBUGPRINT_F" which sends info trough USART. So I think driver could interfere with my own code which uses USART (eg. unwanted messages, erroneous messages, collisions,...). Can I somehow configure driver so that it does not "touch" USART? Or driver sends debug and info text only when I execute particular driver's command?
thanks Rick.
About USART: I want use USART for my own purposes. But if several files of driver (f.e. in dir "utility") have calls to function "DEBUGPRINT_F" which sends info trough USART. So I think driver could interfere with my own code which uses USART (eg. unwanted messages, erroneous messages, collisions,...). Can I somehow configure driver so that it does not "touch" USART? Or driver sends debug and info text only when I execute particular driver's command?
- adafruit_support_rick
- Posts: 35092
- Joined: Tue Mar 15, 2011 11:42 am
Re: CC3000 resources
Debug is a conditional compile option. You just turn if off.
Please be positive and constructive with your questions and comments.