Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by chicken

  1. On the profile page it is labeled as "content count". Maybe "posts" includes status updates and other content.
  2. Is there a specific event when you must read the ADC? If not, just make one main loop that reads keys and ADC. Reading the ADC should only take a fraction of a second.
  3. Did you already try the MSPFlash library that comes from Energia? Use search on this site to get plenty of threads about RTC, like for example this one: http://forum.43oh.com/topic/3375-energia-library-msp430-real-time-clock/
  4. I don't know how good those books by Make are, but if you're looking for some beginner books for Arduino and Raspberry Pi and don't mind that you only get a digital copy (PDF, ePUB or MOBI), this might be of interest: Humble Book Bundles: Arduino & Raspberry Pi https://www.humblebundle.com/books/make-arduino-and-raspberry-pi $1 bundle: Make: magazine, Volume 38: Everything you need to know about DIY consumer electronics Make: Basic Arduino Projects Making Things See: 3D vision with Kinect, Processing, Arduino, and MakerBot Make: Getting Started with the Internet of Things Make: G
  5. How do you expect the JTAG programmer to provide a UART bridge when it's not connected to UART pins of the MCU? One the MSP430F5529 LaunchPad, a second UART is broken out on pins 3 and 4 (P3_3/P3_4). So unless your board has those broken out, using the CCS debugger is your only option.
  6. @@nazmibojan thanks for reporting back. Great idea to get a cell phone repair shop to do the trickier soldering work :-)
  7. How long are the wires over which you want to do I2C? Are the grounds connected? Weaker (i.e. higher value) pull-ups will make noise issues worse.
  8. A MSP430F415 in a cheap fingertip oximeter from AliExpress Teardown here: http://www.kean.com.au/oshw/oximeter/ I wonder if that nicely labeled JTAG header is still functional. With 16K Flash and 512 bytes of RAM, this MCU is comparable to the MSP430G2553. Energia on an oximeter anyone? Addendum 2/28: I ordered an identical looking model off AliExpress. Unfortunately, it's no longer MSP430 inside :-( It's now powered by a STM32F030 ARM M0.
  9. I think the regulator is fine but can't supply enough current to the 3.3V rail. I'd check the power rail for a short circuit or low resistance to ground.
  10. Please define "not work for me". At a quick glance, it doesn't look like the libraries do something incompatible with Energia.
  11. Hi Rian, The packet handler interrupt routine will send SPI commands to the radio IC. This means that you cannot make calls to the radio from the main loop after ph_start(). If you want to test communication with the radio IC, comment out ph_start(). radio_setup() does configure all the pins. One could argue that I should also have set RADIO_SDN to low in there. Instead the first few lines of radio_configure() reset the radio by setting the SDN high for a few milliseconds and then low. If you want to put a resistor on the SDN line, I'd use a pull-up to keep the radio in reset until
  12. The redefinition of pgm_read_byte and pgm_read_word in the library (lines 18, 19) may also cause issues.
  13. Did you cross the serial lines as documented in the pinmap? Note that version 1.4 is different from 1.5. http://energia.nu/pin-maps/guide_msp430g2launchpad/
  14. Hi Rian, Are you using CCS to develop your dAISy project? I highly recommend CCS and the original project shared on Github, at least until you get that working. Energia is very limited in its debugging capabilities and may interfere in other unexpected ways. If your code hangs inside radio_configuration(), then it's very likely that there is an issue with the wiring or pin configuration. In particular RADIO_CTS (GPIO1) is critical. The radio uses this line to signal when it's ready to receive more commands from the MCU. Also RADIO_SDN (radio shutdown) needs to be set to low to turn on
  15. Does the regulator or any other component get hot? You might have a short circuit on the 3.3V rail.
  16. PS: Setting up clock systems can be quite complex, especially with the newer MCUs. Take a look into MSP430Ware which should come installed with CCS. It contains convenient functions to setup your clocks without having to worry too much about registers. Looks like this tutorial on getting started with CCS and MSP430 Launchpads uses MSP430Ware. http://processors.wiki.ti.com/index.php/Getting_Started_with_the_MSP430_LaunchPad_Workshop
  17. As mentioned above, I'd focus first on communicating with the sensor before going into interrupts and timers. You can verify the clock settings by looking up the registers in the Family User Guide of your MCU. http://www.ti.com/product/MSP430FR5739/technicaldocuments#doctype6 Looking at the intro of chapter 3.4, it looks like you may need to write a password into CSCTL0 before you can write to the other registers of the clock system. You should also learn to use the debugger in CCS. It allows to execute your program step by step and looking at register values etc. http://processors.
  18. Another MSP430, this time it's a MSP430FR5739 running the Ring "smart" doorbell The full teardown is documented here: https://www.exploitee.rs/index.php/Ring_Doorbell I was a bit surprised to only have a "lowly" MCU in a device that streams video over WiFi. But it looks like a specialized IC by Omnivision (OV788) and the WiFi module (GainSpan GS2011M) do the grunt work. The MSP430 probably just waits for someone to press the button and then turns on LED driver, camera and WiFi. See this dev kit by the vendor of the WiFi module. http://www.gainspan.com/products/gs_adk_aek_videoov72
  19. @@albertRM What is your specific problem? We can't help unless you let us know which pieces of your program work and what the symptoms of your issue are. This is the thread on this forum that our ever helpful @@Rei Vilo probably is referring to: http://forum.43oh.com/topic/1825-interfacing-with-dht11-humidty-temp-sensor/ At a quick glance, I'd first try to get the sensor reading to work without involving a timer interrupt for timeouts.
  20. For those with a dAISy USB or BoosterPack, I just published a new firmware version 4.11 on GitHub. https://github.com/astuder/dAISy/tree/master/Firmware It introduces the greatest incremental improvement since firmware 4.02. Turns out, slower channel hopping works A LOT better. Same range, but in my tests the change results in about 25-30% more messages received. I also fixed bug in serial communication that only occurs when you try to connect dAISy to an Android device. That bug was introduced a month ago, and impacts only a few customers that ordered units between December 20 2016 a
  21. Looking at the data sheet: - Hi/lo speed is determined by the voltage on the SET pin. See page 2 - The timing waveform on page 4 is describing 1 bit. Repeat it 72 times to transmit 72 bits of data (8/8/8 bit RGB for 3 LEDs), times the number of chained ICs. From what I understand, the SPI trick uses multiple bits of SPI data to match a single LED bit's timing. E.g. you'd use 100 to transmit a 0 and 110 to transmit a 1. You just have to make sure that SPI runs at roughly 600ns / bit, i.e. 1.666 MHz, with 1.6 probably being close enough. The trickier question is how to get the color data i
  22. Just the other day, there was an article on hackaday that may give you some workarounds http://hackaday.com/2017/01/20/cheating-at-5v-ws2812-control-to-use-a-3-3v-data-line/ Alternatively, a level shifter like SN74HCT125 could be used.
  23. Sounds like an issue with the wiring between the programmer and the MCU. Which pins of the MSPFET did you connect to what pins of the MCU?
  • Create New...