Jump to content
43oh

nathancrum

Members
  • Content Count

    25
  • Joined

  • Last visited

  • Days Won

    5

Everything posted by nathancrum

  1. Yea I looked at the Fujitsu parts, but they are not rated as well for power consumption. The Fujitsu spec is 10.6mA @ 25MHz. The Cypress spec is 1.4mA @ 40MHz / 0.13mA @ 1MHz For the product design I'm working on at my day-job we wanted the best performance, period. The Fujitsu part isn't rated at lower speeds so I wasn't sure how quickly - or if - the power dropped at lower speeds. We're running it @ 8MHz and it seems to consume a few hundred uA so the Cypress part is quite good in that range. That said - for a Storm Ninja add-on - the Fujitsu chip might be worth the power/cos
  2. Good question. We do not have a specific launch date in mind, but I think we are aiming at having parts ready to ship this fall. We will most likely launch a Kickstarter campaign sometime in the next 30-60 days. Deliveries would probably start 90-120 days after the campaign ends. At least that's my best guess for now. Regarding the LCD - there are a few example images posted above. The contrast on the 128x128 screen is really excellent - it is a joy to look at: Regarding external Cypress FRAM - 2Mbit is about $20, 1Mbit is about $12. http://www.digikey.com/product-detail/en/
  3. @@DeepBlueSky - I've had success getting an MSP430F5529 to write to an SD card, but it's running on two AA's. SD cards can take anywhere from 30 to 100mA to drive so yea - not very practical on a limited power budget. I doubt you could even get it to operate with the internal resistance of a coin cell. I'm actually using external FRAM for that reason on a project at work. Cypress makes a range of chips from 256kb? up to 2Mbit. It's expensive compared to SD cards or even flash, but far superior to both for power efficiency and it's also a LOT faster than flash so you can write your data
  4. Hi guys. It's been awhile since we've posted on this project, but progress has been steadily moving on. We're working with the Rev 3 prototypes at this point and I think we're pretty close to a final product. Patrick is going to be out at the Bay Area Maker Faire next week showing them off. We're also trying to upload stuff as it's stable to github - a few demo projects and an Android app for bluetooth: https://github.com/ApparentlyConnected Shurikens (daughterboards) have expanded now to include a sensor board (RGB, accel & temp), a relay board, an AC rectifier board for use w
  5. @@bluehash Thanks - we're already having fun playing with it and really impressed with the Sharp LS013B7DH03. The mirrory finish on the 96px one from the BoosterPack is sort of a novelty, but the contrast on the 128px H03 is much nicer on the eyes overall. Next I'm working on a Bluetooth LE shuriken and Android app and @@Patrick is working on a WiFi expansion and internet upload. Weeeee!
  6. FYI - made some more progress on the Energia graphics library and have added a bitmap interpreter for the TI Image Reformer tool in the MSP430 graphics library package. Adding any custom image to a project just got a lot easier. (edit) And I am loving this screen - the contrast is awesome.
  7. You'll need reset, test and ground and if your custom 5969 circuit is power hungry, it will need its own power supply during programming too (the onboard Launchpad regulator isn't terribly powerful and will choke if you ask it to power too much.)
  8. FYI - We've also forked the Energia github and have pushed these changes already. Hopefully we can resolve the driver issues in the future, but for now it's functioning separately. https://github.com/ApparentlyConnected/Energia We've also started adding libraries for our Shurikens (daughter boards) like the Sharp 128x128px LS013B7DH03 Memory LCD. On deck are the bluetooth (Microchip RN4020) and WiFi (Microchip RN171) modules. Unfortunately the existing libraries like SPI aren't abstracted enough to be cross compatible (we're using different UARTs, pins, etc) so some more work will
  9. @@pabigot - We definitely would like to get some demos in the hands of people that can put them to use, but we don't have many prototypes yet. I think there's probably something we can work out though. BSP430 also looks really cool - we'd love to have the Storm Ninja supported there too. Regarding Energia - I was still hoping to figure it out myself so I knew where everything was located. If someone could either list the files or point me towards the documentation that would be awesome. I don't mind doing the work - I'm just a little lost. As I mentioned - I think I have the pins file
  10. Hi guys, We've been playing with the prototypes for a few weeks now and wanted to start adding support for our board in Energia and...after some searching, it's not at all clear if that's possible right now. I will keep looking, but figured I should post here for now since someone probably knows the answer, "Is is possible to add new processor boards to Energia via text configuration files?" ...or is it more complicated? I got as far as writing a pins file before realizing this was not sufficient to totally describe the board. The Storm Ninja is "hardware-compatible" with the FR5969
  11. FYI - flashing only the BSL and connecting to CCS has essentially the same effect. It "recovers" then updates and it works fine.
  12. @@greeeg - you are the man. So - I was counting on CCS to update the firmware and it was erroring out without attempting to fix anything. I was able to flash the BSL firmware using flasher, but every time I tried to flash the FW_3_3_0_6 firmware it failed verification. So - I tried flashing only the BSL_1_1 firmware. Then I plugged the ezFET into USB and tried erasing the target using MSPFlasher. That's when it did this: c:\ti\MSP430Flasher_1.3.2>MSP430Flasher.exe -e ERASE_ALL * -----/|-------------------------------------------------------------------- * * / |__
  13. Attached is the schematic. It probably looks pretty *cough* familiar. Storm Ninja Base PCB Schematic.pdf
  14. Yea - we missed that the first time we flashed, but later found it - used it - same error - no change unfortunately.
  15. @@spirilis Yep - we're 100% winblows. Tried reflashing all the ezfet lite firmwares. The 3V6_TEST firmware lites up the error LED, but all the rest of the test firmwares don't, so power seems ok and it is definitely being flashed with the ezfet on the FR5969 Launchpad... Our setup is basically identical to @@greeeg - would love to hear any ideas from him. We used the MSP430Flasher_1.3.2 to write the BSL and then flash the EZFET_LITE_Rev1_1_FW_3_3_0_6 firmware...still no love.
  16. @@nimblemotors Is that an FRAM MCU? I wasn't aware you could trim the DCO in FRAM chips...?
  17. @@abecedarian Used the latest (I think) version of the flasher. 1.3.2 @@spirilis Yea - very annoying. We must be doing something wrong. The eZFET lite ref. schematic shows 4 voltages for the reg from 2.8 to 3.6V so I assume all of those would be ok for the voltage checks using the ADC. We're using 3.3V. Voltage on Pin 1 and 2 from the voltage dividers both look fine. We've been struggling with this a couple days - ready to throw in the towel. Can't figure out what's wrong.
  18. FYI - first dev prototypes are built. The processor module is fine, but we're still debugging the ezfet lite circuitry - getting this error when connected to CCS: "Error initializing emulator: Could not set device Vcc" Don't know what's wrong. The programmer is basically a pin-for-pin copy of the ezfet lite reference using a 3.3V regulator. We flashed it using the MSP430Flasher command line tool, the EZFET_LITE_Rev1_1_FW_3_3_0_6 firmware and an FR5969 Launchpad via SBW. It seems to work, but generates a verification error and then we get the above error on connecting to CCS. Is the
  19. Just as an FYI - I was concerned about using the built in DCO in the FR5969 for UART because the spec sheet says although it's factory trimmed, it's still +/-3.5%. Generally it needs to be within 2% for a UART to work correctly so I measured the two FR5969's I have on our 2.4GHz frequency counter and this is what I got. 2 is obviously not a big sample size, but the frequency trimmed DCO on the FR series looks pretty good @ room temp and 8MHz or under. I found another doc from TI that's a comparison between F5xxx and FR5xxx and it mentions the DCO is generally within 2% "within a restrict
  20. @@pabigot I have to apologize - I thought for sure someone at Microchip had said 50ms and I had that number floating in my head for weeks. It probably came from the attached (convincing) power graph, but but I just checked the presentations and they also included an actual time trace. *cough* I was only off by an order of magnitude *cough*. Later they also claim typical on time of ~250ms so they're all over the map. I haven't personally verified any of this yet, but I have both an RN171 and RN131 and plan to play with them soon. Time Trace: Total wake-to-sleep time = 463 ms Associate
  21. @Rei We're not necessarily DOA without 5V, but the thought had occurred to us. The processor board will be 3.3V, but we were considering using something like this on the UNO breakout to provide both 5V compatibility and higher current capacity (MSP430 is only 6mA per pin max vs. the UNO's 40mA): http://www.ti.com/lit/ds/symlink/txb0108.pdf @@pabigot Our tentative plan was to use the Microchip RN4020 for Bluetooth LE. 16mA is skirting with the limit of what you could get out of a coin cell, but as long as it's used in bursts it should be ok. For continuous use or WiFi you'd need AAA's,
  22. @@igor I get you're annoyed there are multiple connector layout standards, but you think we should match our programmer to a less common one than Arduino? Your reasoning is exactly why we put it in UNO format instead of boosterpack - to support the most existing developers and hardware. We'd love to support both, but you can blame that impossibility on TI - why on earth did they set up the pin spacing on the launchpads to be exactly 0.10" shorter than Arduino (gah! so close!). If it was at least 0.20" we could just add a second set of headers inboard. I'd have to look at the pin assignm
  23. Layout for the programmer attached. As mentioned this is in the form factor of the UNO, but it's actually an eZ-FET lite programmer using the MSP430F5528. It includes the F5528, micro-USB, 4 LEDs (2 for the ezFET, 2 for UART), a regulator and a breakout for standard JFET. ...and before you ask, yes the product name is Storm Ninja. For those unaware, it's a joke from one of our favorite shows - Archer.
  24. @@spirilis - Right now the processor module has standard 0.1" headers so you can pop it on a breadboard. We could use smaller, but the limiting factor for size is the CR2032 anyway. IO includes 14 digital I/O's, 6 analog, UART, I2C, SPI and SBW (26 pins in all, one NC). @@Rei Vilo - Yes similar idea. Although I don't know why, but I haven't seen any micro-form-factor Arduinos like that based on the AVR equivalent to the MSP430FRxxxx - the XMega processors: http://www.atmel.com/products/microcontrollers/avr/avr_xmega.aspx There are also a few low-power libraries for Arduino, but the
  25. Hi Guys, My name is Nathan. I've lurked around here on 43oh a bit, but this is my first official post. I've been working with the MSP430FR5969 for several months now and I've quickly grown to really like it. It seems to me TI's FRAM processors should really be getting more exposure for battery powered development in both professional and maker communities. To that end - I was hoping to get some feedback on a product idea. We've packaged the FR5969 into a tiny coin-cell powered module. The module can operate as a stand-alone processor or it can plug into an UNO-form-factor breakout
×
×
  • Create New...