Member #13237

Member Since: January 6, 2007

Country: United States

  • I wish I had read the datasheet closer before buying. Ill still play with it, but the problem is 6uA/MHz but MHz is either 24 or 48 not Khz. so 144 or 288ua. Where the competition can get down to 6-10uA total with slower clocks at 1.8V the closest for this part on the datasheet is 80uA but that is with more stuff off than the competition. So a design with a CR2032 should last single digits of time times the length of time this part runs. Now if you get into the very deep sleep modes, without I/O (so how do you wake up gotta read more), then sure you can get a long run on a CR2032. The description says ~1.6mA. So at ~10ua that would be 160 times longer?

  • Two days ago it was $59 at amazon, now $69

  • And as far as the verilog/vhdl side there are free tools out there that run on linux and windows that any one can dive in and start using. Understanding that you dont need to see an actual led light (or actual smoke come out of the part) to learn something, you can do huge, complicated designs, just like the professionals do it. That last step of taking your design to silicon has a learning curve sure, but you can divide those learning experiences up on these natural boundaries. I have been working in the silicon industry for years and along with the pay-for tools we use the free tools quite a bit (verilator and icarus and gtkwave), as we do our software development on chip/board simulators so that when silicon arrives we are mostly ready to go.

  • I dont see the logic is all that hard, counting from 0 to 1, AND, OR, NOT covers about 99% of it. The tools are proprietary and generally not at the quality of the equivalent software toolchains. That is a major barrier to entry for software folks to transfer over. xilinx or someone did a study back when languages were taking over schematic capture, and software folks were preferred over electrical engineers for doing logic design because all you had to teach them was the concept of things happening in parallel, they already knew programming languages and compilers and other similar tools. Today of course that is different. If someone were brave enough to make a programmable device where the guts of it, were open such that the open source community could make the compiler and place and route, etc, you would eventually see tools that dont suck, run everywhere, and overall better experience.

    The real reasong for adding a coment though is that if you go over and look at what has, which wants to be competition for cpld and small fpgas, that may or may not be a good stepping stone for software folks that want to do more than just bit bang some gpios. not the same languages, sure, C and asm instead of verilog and vhdl, not the same experience necessarily as pure logic, but the experience of understanding the signals you want to send or receive, using a simulator that provides waveforms that you use gtkwave or something with, that is all the same experience as with cplds and fpgas.

  • How do I load firmware from ubuntu/linux?

  • I would definitely buy breakoutboards to go with the mbed if sparkfun made them and/or sold them.

No public wish lists :(