motopic

Member Since: June 2, 2006

Country: United States

  • News - The Final Open House Remi… | about 3 years ago

    Ha, the bouncy castle gave me an idea.
    You guys should run your very own WIPEOUT zone !!!

  • News - The Return to Shenzhen - … | about 3 years ago

    Use a good syringe like from Zeph.
    http://www.zeph.com/chem_direct.htm

  • News - Arduino: The Documentary | about 3 years ago

    A number of reasons.
    1 FPGA are more expensive. I buy Freeduino clones for $9.95. The cheapest FPGA is $50. FPGA boards are not targeted to deployment, but protoyping.
    2 FPGAs have their own language. You have to build, in SW the operating guts of what you are trying to do. And debug it? Don’t discount the difficulty of this. And this is before you even get close to working on your ‘real’ project.
    3 ALL FPGA SW is proprietary. All the cool little things you need like SERIAL, I2C, SPI are proprietary. To deploy anything you make you have to PAY $$$ to vendors like Xilinx.
    4 Then you need all the tools for the system you designed and built, so you can write userland software to run the project. Did you choose wisely here, or develop a FPGA that you now have to write all the libraries for?
    ARM7? Old ARM7 have lots of libs and are cheap. You get lots of power, but still, software for basic stuff like SD cards/FAT16 can be a challenge to get working(there are many to choose from). SW is all over the map. I found myself integrating all kinds of code from all kinds of styles and designs.
    STM32? Nice chips, powerful designs. But again, SW is all over the map, especially if you try to stay open source, and not buy say Rowley Crossworks at $1500 per user. At this point when I was developing arms, I knew how to tweak startup.S codes because you needed to know how to do that to get various compilers, libraries and chips to work together. Not fun.
    Arduino? Cheap, sure they are smaller, less powerful. Tons of software, most of it provided in the base system. Common design of libs, and hw make getting up and running a fast deal. I wrote a RTC lib on my second day with the HW (my rtc was not supported) using another RTC as an example.
    So why not PIC?
    Because PICS suffer from proprietary compilers and software too. I have to pay $150 for the cheapest compiler for a pic project, (that arduino could also do easily), so that will be the last pic project I do.
    My observations.

  • Tutorial - Arduino Buying Guide | about 4 years ago

    “Arduino Pro: A SparkFun original. The pro mini is a great little board. "
    Maybe should be:
    "Arduino Pro: A SparkFun original. The pro is a great little board."
    Also of course this paper only discusses arduinos that SF sells. There are lots and lots of arduinos out there, many add other features or are much cheaper.
    Finally, is SF going to fix the SD shield with a proper signal shifter? I see lots of queries about that on the SF AVR forums, and on the Arduino Forums.

  • Tutorial - Notes on the STK500 Serial Bootloader | about 5 years ago

    um, a link?
    Programmers Notepad2: http://www.pnotepad.org/
    Get the portable version and install it on your usb stick.

  • Product DEV-08183 | about 7 years ago

    I too found this a very interesting device. We are working a Open HW/SW Project and have several complaints about having to purchase PIC compilers just to work on code. This device I had up and running in literally 5 minutes. No extra HW programmers to buy, works perfect with laptops. a really good value.

No public wish lists :(