Prototype module prototyped on a prototype Protomodule
#1
Posted 03 May 2012 - 12:56 PM
- Gutworks likes this
Total BOCS Traveled Distance: 9708 miles | States Visited: 5
Track the Box
#2
Posted 03 May 2012 - 01:22 PM
#3
Posted 03 May 2012 - 01:41 PM
Total BOCS Traveled Distance: 9708 miles | States Visited: 5
Track the Box
#4
Posted 03 May 2012 - 01:46 PM
#5
Posted 03 May 2012 - 01:46 PM
My .NETMF projects: .NETMF Toolbox / Gadgeteer Light / Some PCB designs
#6
Posted 03 May 2012 - 02:09 PM
#7
Posted 03 May 2012 - 02:49 PM
Total BOCS Traveled Distance: 9708 miles | States Visited: 5
Track the Box
#8
Posted 03 May 2012 - 02:52 PM
Just out of curiosity, what 'module source' do you have?The issue I did run into, and community member Matt Isenhower saw the same issue, was code compiled from the module source seems to send an extra byte during enumeration.
#9
Posted 03 May 2012 - 02:55 PM
When can this be ordered and for which amount?
So far I've got all Go! modules, you know the tagline of Pokémon? Gotta catch 'em all
We're still working out logistics on getting them made up and assembled and exploring all our options there. We obviously want to make them as affordable as we can so that the 'Go! Bus' isn't a barrier to entry on using the Netduino Go. We're currently waiting on quotes from some various suppliers and assembly houses. Hopefully we can state a price and timeline to being available in the next couple weeks.
Total BOCS Traveled Distance: 9708 miles | States Visited: 5
Track the Box
#10
Posted 03 May 2012 - 03:06 PM
Just out of curiosity, what 'module source' do you have?
I'll have to check when I get home but it's a zip with your CW2 handle on it and it's an IAR Workbench workspace from I want to say the tail end of March as timestamps on the files. I'll be more specific a bit later, obviously it would be great if that's all it was (out of date source).
Total BOCS Traveled Distance: 9708 miles | States Visited: 5
Track the Box
#11
Posted 03 May 2012 - 03:23 PM
Ok. Please note the reason module firmware source has not been released yet is because I am waiting for the go!bus protocol specification to be finalized, to avoid exactly this kind of issues.I'll have to check when I get home but it's a zip with your CW2 handle on it and it's an IAR Workbench workspace from I want to say the tail end of March as timestamps on the files. I'll be more specific a bit later, obviously it would be great if that's all it was (out of date source).
#12
Posted 03 May 2012 - 05:31 PM
Ok. Please note the reason module firmware source has not been released yet is because I am waiting for the go!bus protocol specification to be finalized, to avoid exactly this kind of issues.
Yeah, we're certainly aware of that but we bugged Chris into giving us the firmware for experimenting, as neither Dan nor I have any experience working this close to the hardware (.NetMF is the closest for me).
When you talk EE use small words, I'm just a Software Developer
My Blog/Site and Everything Else
If my post helped you please consider pressing the "Like This" button in the bottom right-hand corner.
Oh my. So many things, so little money!!
#13
Posted 03 May 2012 - 11:24 PM
Total BOCS Traveled Distance: 9708 miles | States Visited: 5
Track the Box
#14
Posted 13 May 2012 - 02:49 PM
Total BOCS Traveled Distance: 9708 miles | States Visited: 5
Track the Box
#15
Posted 14 May 2012 - 05:17 AM
Protomodules are available for
When you talk EE use small words, I'm just a Software Developer
My Blog/Site and Everything Else
If my post helped you please consider pressing the "Like This" button in the bottom right-hand corner.
Oh my. So many things, so little money!!
#16
Posted 14 May 2012 - 06:38 AM
#17
Posted 14 May 2012 - 06:46 AM
#18
Posted 14 May 2012 - 07:54 AM
#19
Posted 14 May 2012 - 02:44 PM
Total BOCS Traveled Distance: 9708 miles | States Visited: 5
Track the Box
#20
Posted 14 May 2012 - 04:21 PM
I'm always looking for ways to save myself time during module development and the ProtoModule seems to have potential for that.
However, I'm trying to understand the value proposition of the ProtoModule over the full-featured $8 STM8Discovery board made by ST, which comes with STLinkv1 and is accessible over USB for programming and debugging the chip.
The STM8Discovery board only requires soldering a Go! connector / pin headers to get going, requiring about the same soldering skill level as the ProtoModule.
I may be missing something, but in the case of the ProtoModule, it seems that the user would also have to purchase STLinkv2 separately for programming / debugging or at least would need to provide a USB -> Serial cable (i.e. FTDI-type of solution) to upload firmware to it?
It would be great if you would provide specific details on the requirements for working with the ProtoModule, end-to-end.
As far as the "Standard Module Firmware" goes: what specific features will it provide and when will it be released?
Thanks,
Cheers,
-Fabien.
5 user(s) are reading this topic
0 members, 5 guests, 0 anonymous users