Jump to content


  • Content Count

  • Joined

  • Last visited

About amstan

  • Rank
    Advanced Member

Contact Methods

  • Website URL

Profile Information

  • Gender
    Not Telling
  • Location
    Santa Clara, California
  • Github
  1. It's not that great. I tried it for my rgb clock project. You have to do a lot of work for it. You basically trade your project documentation(which you have to customize for their site) for the boards. They're not that good of boards, green only, take quite a while to get(elecrow was faster). http://www.electronics-lab.com/projects/mcu/025/index.html I eventually went with elecrow since they had black available and I didn't feel sketchy basically selling my design.
  2. When i dabbled into I2C it seemed that the hardware for it is really inflexible(it even contains bugs). So i just made/adapted my own bit banging library. I don't care that it's bit banging because it's probably fast enough. The bonus is that you can use it on any pins that you like. https://github.com/amstan/binaryclock/blob/master/firmware/i2c.h
  3. When I counted there were 81. I guess you have 80 now. heh. How do you limit current on them? Aren't you worried that you get uneven brightness if you just use the pin current limit? At least the anodes should have a resistor for current limit(ideally a transistor as well, if you want higher currents). Also.. a battery like the CR2032 can only give like 5mA, anything more and the voltage should drop. If the voltage drops too low you might have glitches in the mcu and have problems with the program execution. You could solve that with a big cap. I included the leftover parts fo
  4. @@simpleavr Why don't you jump on IRC to discuss donating arrangements? #43oh on irc.freenode.net
  5. Would this be of interest? I have a bag of them (80, all pictured). In various stages of pin bending(i don't think any are broken though). I didn't really have any plan for them, totally forgot I had them for a while there. I'm open to donating them for this group buy. At least part of them(I don't think there's a need for 80, heh). The catch is that they're 3 digits, this board calls for 4 digit displays.
  6. Yeah, same. I have too many things i don't have a purpose for.
  7. I had mine working on 18MHz using the ti sample code and my own xtal.
  8. Unfortunately it doesn't look very well when it's stationary. Perhaps I'll get some videos in a few days.
  9. I got mine a few days ago. I wrote a python3 driver for it: https://github.com/amstan/pynoritake I also tried to emulate the squiggle from this lcd megademo 2, Just run ./squiggle_noritake.py to see it on ttyUSB0, you'll need numpy as well.
  10. You need to install http://processors.wiki.ti.com/index.php/MSPDS_Open_Source_Package aka tilib. It replaces the uif method in mspdebug. Energia comes with a binary of it. If you don't want to go the energia route, and you have archlinux you can install https://aur.archlinux.org/packages/mspds/. If you're on another distro you could look inside here and run the compiling commands manually.
  11. ld.exe: CC3000FirwareUpdate.cpp.elf section `.rodata' will not fit in region `rom' ld.exe: section .vectors loaded at [0000ff80,0000ffff] overlaps section .rodata loaded at [0000e6b0,00011a29] ld.exe: region `rom' overflowed by 6840 bytes Seems to me that something won't fit. The CC3000 firmware might be too big to be used with the fr board(which only has 16k of code space). I might be wrong though.
  • Create New...