Thanks, I totally appreciate where you are coming from. Here's how it is from a potential customer's perspective: We're looking at the Beaglebone, rather than the Raspberry Pi, because we have an embedded application with 20-100 units. If it were just a single item, we would probably be tempted to use a Pi, because there are already a few GSM/GPS boards out there and a bigger community. It's worth doing a little more work to put it into the Beaglebone because we're going to make a few of them, so we value the embedded flash, additional IO and commercial availability of the processor.
I think you're going to find a few customers in this same situation: the "in-between" numbers where it's worth a little extra work to use a Beaglebone, but we don't have enough volume to spend time making up our own PCB. Customers in this situation are going to want to buy a single board for evaluation, and if that works out well they'll buy 20-100 more boards for prototypes, then maybe look at making their own PCB. Before they buy the first board, they're going to want to see a development path - 1 item: "is good example code available for our first unit?" 20-100 items: "can I get a good price break for 50 units?" own PCB: "are schematics available for our implementation?" At the moment you look to be doing a good job of the first step, but the development path from there is unclear. Perhaps you guys have a strategy for prototypes and production? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
