This is a quote from the comments on the Kickstarter site:
"The I/O is 5V tolerant, with the exception of a couple of pins;
we'll publish pin mapping so you can see which is which. We have
one I2C, one UART, and one SPI interface available. The
resolution of analog I/O is 12-bit. If you want to do bare
metal programming, you're free to; Wiring/Arduino is just a
set of libraries that you can choose to use or not."
The important and complete hardware stuff is in the github zip. They are using a STM32F103CBT6. The SPI interface to the CC3000 is apparently non-trivial,
I was afraid that the STM32 was too small. It looks like the only way to use it with the Micro framework
is to setup a an Arduino command processor on the Spark Core and talk to it through the UART.
Perhaps we can entice Secret labs to build a 2nd generation Mini around the design on Github. I guess the
other alternative is to use the CC3000 directly, but it seems frightfully difficult to port the TI SPI driver over to the MF.
well, if the goal is 'use the spark core' then you probably are out-of-luck for netmf directly, as you point out. but if the goal is 'make a new hardware', then it should be easier, because you can put in a better processor. the package of the 415 is 64 pin, and spark core's is 48, so you might have some placement challenges, but I think the mini is already using a 64 pin device, so it should be doable.
if you talk to it through a uart, that kinda loses the benefit of spi, right? I haven't looked at the datasheet, but now I'm curious about the difficulty you mention. From the outside, it looked like it presented a high-level interface to networking; i.e. it has its own tcp/ip stack, and works similar to how many of the shields work. In a way this might make integraiton easier. Well let me rephrase that; it would make integration easier except for the fact that lwip/enc38j60 is already integrated, and what can be easier that work already done? So it requires positive, non-zero, effort, but probably would reduce the code footprint a bunch.
Hmm. now I'm curious. I wonder if someone has a cc3000 on a breakout board.... I don't know how digikey is selling them for 12.50 when others (e.g. mouser) are selling them for about double that. Maybe they have a special deal with ti...
Too bad there's no F4 in 48 pin package. I don't really see the point in talking to the Spark Core over UART, there are simpler and/or cheaper ways of doing that: http://imall.iteadst...m130522001.html
at the outset it might be too much for a managed 'driver'. well maybe. maybe not! I say this only because its' interrupt driven and I was concerned about latency, but then if it's handling the network stack, then it is also handling acks and retries so the host may be able to be more leisurely about servicing requests.
...Too bad there's no F4 in 48 pin package....
well the current mini uses a 64-pin package does it not? anyway I know the various ghi boards in dip form factors do, so it should be doable from a layout perspective.
OK well hmm I may have to carve out some time this summer. I am currently distracted trying to port an RTOS to the NP2, and ultimately port netmf on top of the RTOS, but that could take a while (if it even works out), and I may need a distraction from my distraction. Plus, this wifi capability is germane to some paid work I'm doing, so maybe I can fold it in that way....
Thanks for the links!
ps hanzibal, I have been meaning to do your oscilloscope art, but I haven't been able to get to it yet, haha
ps baxter, I have always been envious of your avatar -- it reminds me of Lord Melchett from Blackadder, and consequently when I read your posts it is always in that character's voice, haha
OK, well it will probably a a couple weeks before I can fiddle with it. Too bad centerblack doesn't have spares of his breakout board, I'd rather than than the gauche TI dev board, but I did order one. Digikey thanks you, at least; haha.
hmm, could be usable for development at least. won't win any 'sexy dev board of the month' contests, but hey its a dev board.
It's much smaller than it looks but it's abviously designed as an add-on for some TI general eval platform. You only need to connect SPI bus, power, gnd and the enable pin so it's quite simple.
...at the outset it might be too much for a managed 'driver'. well maybe. maybe not! I say this only because its' interrupt driven and I was concerned about latency, but then if it's handling the network stack, then it is also handling acks and retries so the host may be able to be more leisurely about servicing requests.
Exactly, the module handles most or all of the protocol level stuff internally so I'd expect a managed driver to perform ok or at least better than any UART based module.
...anyway I know the various ghi boards in dip form factors do, so it should be doable from a layout perspective.
Yes, I have a couple of those boards and as I recall, the design makes pretty good use of the PCB space as it is bit I suppose one could always add a couple of layers.
...ps hanzibal, I have been meaning to do your oscilloscope art, but I haven't been able to get to it yet, haha
I can imagine you'd display graphics or even video ;-)
I decided to make a breakout from the centerblack design http://www.centerblack.com/. I simply submmited the the Eagle .brd file to OSH PARK and after processing it for a while they presented a response for approval that I cast to the attached PDF file. All-in-all, a pleasant experience compared with other board houses with Gerbers et al. The boards turned out to be 1.17 x1.17 inch, min. order 3 for a total price of $6.85. It looks like one can make a breakout for the order of $20:
OSH Park board (1.17 x1.17 inch) $2.28 (min 3 @$6.85)
Thought I would give an update on my experiences with the CC3000; not pleasant at all. I received my Wi-Fi CC3000 BoosterPack and MSP430 LaunchPad Bundle so I installed all of the software. Can't connect at all. It appears to me that TI has messed up their software packages. The following message was sent to TI support which outlines the problem. I alluded to the fantasy that evaluation was for >1000 units production to hopefully get their attention, but if they do reply i will probably have to deal with a Rep. on the phone at some point ... blah
Sorry to hear that, have you tried the Texas E2E community?
They are very helpful and you usually get help directly from TI employees working within the very field in question. At one point they even called me on the phone and that without me having pretended to be a big shot with 1k+ units planned for production
well I soldered on some pin headers ('custom made' since they are on an unusual 2mm pitch). we'll see if I can get something to go over the spi; maybe there's a 'version' command or something similar....
Exactly, why on earth did they choose to add custom headers with 2mm pitch as an alternative to the special headers already being odd? I'll give it a try too, using SPI bit banging of my very own USB board as to challenge you all in this quest for fame and glory. Saddle up there, oh bretheren fore once again we shall ride blindly (and stupidly) into the unknown.
From the main sketch, ArduinoCC3000.ino, it seems that there is a simple version command.
The code size they mention is about the same size as I was getting with the Basic WiFI Application on the MSP430 (~10k and ~100 bytes). I am going to give up on the MSP430 and follow in your footsteps.