Jump to content
43oh

tripwire

Members
  • Content Count

    193
  • Joined

  • Last visited

  • Days Won

    14

Everything posted by tripwire

  1. The MSP432 launchpad can't program MSP430 chips, it's only set up to program ARM Cortex MCUs. Power/EnergyTrace and backchannel UART work just fine, though. By the way, the MSP432 launchpad has a 3.3V supply voltage rather than 3.6V as used on the MSP-EXP430FR5969. That doesn't cause problems as the MSP430F/G chips run happily at either voltage, but it's sometimes important for other components if you're using a custom board.
  2. I haven't written any code for it yet, but I did some digging into the documentation and it's an interesting bit of kit Some useful documents are here: http://www.knowles.com/eng/content/download/5990/105795/version/1/file/SPH0641LU4H-1.pdf (datasheet) http://media.digikey.com/Resources/Knowles/knowles-sisonic-design-guide.pdf (see section 2.2.4: PDM Digital SiSonic) http://curiouser.cheshireeng.com/2014/10/21/introduction-to-mems-microphones/ (general overview) https://e2e.ti.com/blogs_/b/precisionhub/archive/2015/01/21/delta-sigma-adc-basics-understanding-the-delta-sigma-modulator (
  3. You haven't set the GIE bit anywhere, so all (maskable) interrupts are disabled. That includes your comparator interrupt. Add a "__bis_SR_register(GIE);" before the infinite loop, that should make the ISR work.
  4. Yes, but the necessary modification is difficult at present. The emulator firmware doesn't support cJTAG (only SWD and JTAG), while the CC26xx doesn't support SWD (only JTAG and cJTAG). That means that full four-wire JTAG is the only option that will work right now. The problem is that the launchpad only exposes pins for SWD and cJTAG rather than the full JTAG pinout used with the on-board target. To add a JTAG cable you need to tap into one of the traces on the PCB by scraping off the soldermask and tacking a wire to the trace. The other connections are exposed at J103 and one is on a
  5. You're right, the power won't have started to run down until the plastic strip was removed. Unfortunately I wasn't exaggerating when I called the power consumption atrocious. People have reported draining the battery enough to affect the IMU within a couple of days. I think you might need a newer firmware than that. Are you updating over-the-air from a phone or with a Debug DevPack? I use the DevPack, and the SensorTag sample in the BLE Stack 2.1 has been updated with the power consumption fixes. It's also available as a prebuilt hex file for programming with SmartRF Flash Programm
  6. One thing I've heard is that the IMU doesn't work properly when the supply voltage has dropped below 3V. I know you only just got the SensorTag and would expect the coin cell to fresh, but the original firmware had atrocious power consumption...
  7. Here's a list of things to check for if you're getting excessive power consumption on the CC2650 SensorTag - particularly when using TI-RTOS: [3.0mA constant] If you're not using the MPU, has it been powered off? By default the Board_MPU_POWER pin is set to output high during startup (TI-RTOS 2.1). [2.9mA when idle] Do you have a power policy set up in the TI-RTOS .cfg file, and is it correctly configured to run when tasks are idle? [0.5mA when SPI inactive] Are the SPI bus pins set to pulldown when the SPI driver is inactive? If they're left floating the serial flash inputs can draw exces
  8. It's time for an update. Remember when I said this: When I was writing the firmware I took care to minimise power consumption where possible. The RTOS tasks sleep between measurements and there's no busy-waiting. Writes to the flash are batched up and sent a page at a time, with the flash put in shutdown until the next page is ready. The LEDs and buzzer are not used during logging. I was pretty confident that the power consumption would be acceptable. Well, I finally got around to taking some current measurements two weeks ago and the results were woeful. The average current was s
  9. You have to use the full editor (click the "More Reply Options" button). Below the edit textbox is an "Attach Files" area. After choosing an image file to attach it will be listed in the attachments area with an "Add to Post" link, which pastes some markup that inlines the image in your post. You can preview the post to check that the image upload/insert worked correctly.
  10. I don't think the SSI on Tiva supports that. You'd need to reverse the bit order yourself before passing the data over to the SSI.
  11. I've confirmed that the problem was specific to my SensorTag. As well as ignoring I2C the chip appeared to have some physical damage to the corners (just visible under magnification). I also had an unexplained current draw of about 4mA that was making the coin cell go flat in a day or two. That seemed likely to be caused by the TMP007, and since it since it didn't work anyway I decided to desolder it. Sure enough the 4mA mystery load vanished. I guess it was either shorting out internally or the missing corners had ended up bridging the contacts under the chip.
  12. Thanks! I noticed you'd already been busy deleting similar ones while searching for the original source of the text. The "Beyonce" one had about four hits on 43oh at the top of google's list, but they'd already been cleared off the blog
  13. I just noticed some interesting comments in the sidebar on the 43oh blog. On the Launchpad Screw Terminal Power Connector article someone has posted: "Well if you look at it from a flag planting point of view the Soviets got a few rotbos up there, and the Americans a few rotbos and some people, so they may have a claim. I guess if we get some settlers up there then they can stake out there own claims. I suspect though that some international body such as the International Astronomical Union, might need to be involved in divvying up things.But certainly the people selling the rights to land
  14. Yeah, CCS doesn't handle such things well. The other classic trap is with characters other than the standard a-z|A-Z|0-9 and common punctuation. I seem to remember it chokes on accented characters, which isn't great if you happen to have any in your name...
  15. I just checked it on BLE stack 2.0, and I've also previously tried the TI-RTOS i2ctmp006_cc26xx* sample. Both gave the same result: no acknowledgement from the sensor. * Although that sample was written for the TMP006 the code should work equally well on TMP007
  16. I'm running the BLE stack 2.1 SensorTag and SensorTagStack sample projects, but the TMP007 temperature sensor doesn't work. It fails to acknowledge the I2C address. I'm running the sensortag from a 3.3V supply, so it's not the battery voltage dropping out. Is anyone else getting the same problem, or is it only my SensorTag that's misbehaving? EDIT: Rewrote the post and title because it's only the TMP007 that's not working. The HDC1000 fails the sensorHdc1000Test on startup, but after that it seems fine.
  17. Does the file pwmled_pem4f.h exist at the path listed above? If it does exist then maybe try setting up a new CCS workspace at a path with no spaces in the name. I've had trouble with that in TI's software before...
  18. Can you post the rest of your program? (include everything from the start of main() until that loop above) Also, what hardware is this running on? Which MSP430 chip and what PCB/launchpad are you using?
  19. I'm expecting the 50mm roll to be better value for money (ie less than 5x the cost of a 10mm roll). That said, you do make a good point about how long it will take to use up. I've still got about 24.3 metres of a 50mm x 25m double-sided tape roll that I'll struggle to get through in an average lifetime
  20. Does anyone here find kapton tape useful for holding things in place on PCBs or protecting against shorts? If so, what size tape do you prefer: narrow ~10mm wide or big 50mm rolls that you can snip smaller pieces off?
  21. Here's a heads-up for anyone that wants to use the external SPI flash memory on the SensorTag: it's not accessible while a debugger session is active. Unfortunately the pin on the SensorTag's CC2650 which outputs the SPI clock to the flash memory is also used as the JTAG TDI pin: While you're debugging using the Debug DevPack the CC2650 is unable to clock data out to the flash chip. That means the flash will just sit there doing nothing and the CC2650 will end up reading zeroes from the SPI bus. To use the flash you need to be certain that no JTAG communication is occurring during exe
  22. Aha, I think I have just the thing... Here's some information about a similar problem I had when getting the external flash to work in my program: http://forum.43oh.com/topic/8822-warning-jtag-interferes-with-sensortag-external-flash-access/ EDIT: I just took a look at the extFlashOpen and it calls extFlashVerifyPart to get the manufacturer/device ID. That will get zeroes when the JTAG is active, so extFlashOpen will return false in that case I also spotted this interesting comment, which might help me cut the power consumption of the flash between write operations #ifdef IO_P
  23. Are you using TI-RTOS to write the firmware for the SensorTag? There's currently a bug in the board.c file in tirtos_simplelink_2_13_01_09\packages\ti\boards\SensorTag\CC26XXST_0120. The UART pins are mistakenly configured for a different CC26xx evaluation board (SRF06EB). The corrected version of the offending section is posted below, with the original version shown in the comments: const UARTCC26XX_HWAttrs uartCC26XXHWAttrs[CC2650_UARTCOUNT] = { { /* CC2650_UART0 */ .baseAddr = UART0_BASE, .intNum = INT_UART0, .powerMngrId = PERIPH_UART0, .txPin =
  24. Hi Nick, I'm not ready to release the source just yet, but I am planning to write more about this project as it develops. The majority of that will cover the logging system: how the code is structured, the data flow, log data format and the thought process behind it. Hopefully that will be of interest! Regarding your own project, what particular aspect of writing to the flash are you having trouble with? Is it the practical details of communicating with the flash and performing commands, or is it more on the program design side of things? I'd like to hear a bit more as it will help me
  25. Ah, that's a good point. The MSP432 has a DriverLib ROM, as does the Tiva series. I think the CC3200 and CC26xx do as well. I can't remember seeing any MSP430s with it, however.
×
×
  • Create New...