Jump to content


  • Content Count

  • Joined

  • Last visited

About seanhodgins

  • Rank
    Noob Class

Contact Methods

  • Website URL

Profile Information

  • Location
    Hamilton, Ontario
  • Interests
    Electronics, gadgets, photography, video
  1. You're correct. I had been looking at the pins_energia.h file, but was looking at it wrong. The GPIO_XXs commented out on the right are incorrect. Following the number of the pin in the corresponding array works properly... Kind of stupid I didn't pick that up. I realize now that the GPIO is referring to the Launchpad.
  2. I have a different issue. It seems I'm only able to create a file as large as 56kbytes. Even with the 8mb flash version. If I try to go above 56kb the file does not create/open. I need a file that can be at least 200kb. Anyone experience this?
  3. @@Rei Vilo 1) It gets confusing because I am using CC3200MOD. So the Pins mapped are different than the Launchpad. But when I say GPIO, I mean the GPIO used when using energia. 2) I'm using the latest version of Energia, but I have CC3200 selected, not CC3200MT selected. These images should really help explain what I mean. The red text is what I actually have to use to enable the pins for my LEDs, not the ones listed. This is screen grab of the board I'm using for reference. Of course this could all be an issue with CC3200MOD. Maybe I didn't look into the issue deep en
  4. Was not able to solve the ADC problem. I was however able to solve the LEDs on my board. Somewhere in Energia there is some issues with the pin declarations. So I ran through all of the pins on my board setting them high, (GPIO0-30). GPIO18(which doesn't exist according to TI) makes MOD Pin 8 of the LEDs light up and GPIO 14(instead of 16) makes MOD Pin 6 light up. I'm happy they work, but I'm not happy that there are these kind of random issues that shouldn't exist. I've looked at the pin declarations and they seem to be right. With so many libraries messing with each other, I don't think
  5. I'm getting very frustrated with this CC3200MOD, and the CC3200 in general. First it started with the A0 analog channel always reading 4096 but now on to some GPIO problems. This should be fairly straight forward but apparently they make everything difficult, so I don't know what to say. I have made a custom PCB for using the CC3200MOD. Its supposed to read the 4 ADCs, 3 for accelerometer, which is working great, 1 for an analog microphone, which isn't working at all, but I've given up on it and going to just mux with one of the 3 working ones. Now I have 3 LEDs on the board for general LE
  6. I have a feeling this is an Energia issue. I'm looking for a solution. My theory is that energia may "Automatically" enable default serial pins in a certain way that causes this to happen. If you try to do PinTypeADC(A0, 0xFF), then the system will halt at that line. I'm trying to read all 4 ADCs at high speed and I need them all to work. I really hope its not the case that the RX line is automatically frying the ADC A0 just because its hooked up initially. That would be incredibly stupid.
  7. Almost a year later. I'm having similar issues. I'm trying to make use of all 4 ADC pins. I have the Launchpad-XL and two of my own custom boards using the CC3200MOD. They all give a reading of 4096 for ADC A0. I don't believe its fried. I have done a number of things to try it out, but I believe it has to do with how energia activates the serial ports. I'm using Serial1 to read the values. void setup() { PinTypeADC(A0, 0xFF); //This line is strange and freezes the CC3200 only if on A0 Serial1.begin(9600); Serial1.print("Starting Program on Pin "); Serial1.println(A0);
  • Create New...