Jump to content


  • Content Count

  • Joined

  • Last visited

  1. I kind of agree. I just posted the first revision of a design that (hopefully) address most of the issues. Take a look and tell me what you think...
  2. This is my first attempt at a booster pack design. The design is inspired by the TI/Element 14 Fuel Tank Booster Pack. I wanted to improve on a few of the aspects of the Fuel Tank as well as add a few features to it. Fuel Tank Cons: Non-standard pinout. The I2C pins are not brought out to 9 and 10 as they should be on the BP standard Not solar friendly. The charging IC on the Fuel Tank supports solar charging, but it's not easy to add it. Battery is in parallel with load. The battery is always powering the LP, even when charging current is available Not low-power friendly. The regul
  3. Out of curiousity, what was the bug with pin 6? I was unable to find it in the github issues. Andy
  4. I noticed that in HardwareSerial.h, setPins is declared, but not implemented in HardwareSerial.cpp. So I had a go at it and this is the result. Contributing code to Energia is out of my league, but maybe someone much more skilled than I could use this. It's not fully implemented. According to the reference manual, pins 58 and 59 can be muxed to UART1, but care must be taken that the analog paths are disabled. My thought was that setPins() would return -1 if it was a bad config, would return 0 if the resulting configuration would be dangerous (short analog to digital, overlap with UART0) a
  5. Above doesn't work, hangs shortly after the .setModule(2). I guess I'll let the pros handle it...
  6. Could it be as simple as changing this (HardwareSerial.cpp): static const unsigned long g_ulUARTBase[2] = { UARTA0_BASE, UARTA1_BASE }; //***************************************************************************** // // The list of possible interrupts for the console UART. // //***************************************************************************** static const unsigned long g_ulUARTInt[2] = { INT_UARTA0, INT_UARTA1 }; //***************************************************************************** // // The list of UART pin modes. // //********************************************
  7. The only thing I found is that the schematic seems to label them as TX/RX for some reason - maybe just copied over? The manual says that package pins 3, 4 (GPIO_12, GPIO_13) can be multiplexed to UART0_TX, UART0_RX. However, this would blow up using this UART for debug. Package pins 58, 59 would be the only other possible targets (PIN_MODE_6?). They would require making sure the analog is shut off first, I think. What would be the high-level procedure to modify Energia to use these? Thanks, Andy
  8. Hello all, Love the site and have found a ton of useful information here! I have a question regarding hardware serial on a CC3200 launchpad (rev 4.1). I have found the pinmaps at http://energia.nu/pin-maps/guide_cc3200launchpad/ and they reference TX/RX, TX(0)/RX(0), and TX(1)/RX(1). I was looking for clarification on how these relate to Serial, Serial1, etc. I have a project that uses I2C and UART and would like to keep the FTDI UART as well for debug. P.S. a similar question was asked here, but this particular part was not answered Thanks, Andy
  • Create New...