Jump to content


  • Content Count

  • Joined

  • Last visited

  1. Thanks for your support! I'm going to make some changes in the way I develop the code: First, I'm going to set up a version control system and then I'm going do a commit every time I program the microcontroller. Hopefully this will help me narrow down the minor changes I'm making that could be affecting things. Then I'm going to actually reset the Lauhcnpad after every programming, since I had issues with previous configuration remaining in registers. I'll also study the debug giude in detail. As for no rush, normally I tend to postpone my projects until the last possible moment. F
  2. Hi @@Lyon! I must have missed that part of the manual. I'll just have to read more carefully! I mostly focused on the examples from the workshop (which now seems like it was a bad idea) and I haven't seen TI use disable->enable workflow there at all. I do have experience with other microcontrollers. I used Atmel AVR and Microchip PIC18 in the past. AVR was relatively easy to work with and PIC18 required digging up some not-very-easy-to-find documentation, but both were much easier to comprehend. Also bugs on them weren't as smart as Tiva C bugs: There they'd usually stay in place an
  3. Hi! First about the hex... The algorithm didn't change at all, it's that I just couldn't think of a way to post the characters that I got on screen, so I switeched the terminal to hex and put the code I'm getting. When the test was done, I had the ADC disabled and the value set manually to 2030; I was sending characters '2' '0' '3' '0' '\r' 'n' from the serial port at the time. Do you have any sources for the UARTDisable()->Configure->UARTEnable() workflow? I think I read somewhere about UART being enabled even though it should be disabled by default, but I don't think I've he
  4. Here's the code: /* * main.c */ #define TARGET_IS_BLIZZARD_RB1 //#define UART_BUFFERED #include <stdint.h> #include <stdbool.h> #include "inc/hw_memmap.h" #include "inc/hw_types.h" #include "driverlib/sysctl.h" #include "driverlib/gpio.h" #include "driverlib/debug.h" #include "driverlib/rom.h" #include "inc/hw_gpio.h" #include "driverlib/adc.h" #include "driverlib/fpu.h" #include "driverlib/interrupt.h" #include "driverlib/timer.h" #include "inc/tm4c123gh6pm.h" #include "utils/uartstdio.h" #include "driverlib/uart.h" #include "driverlib/pin_map.h" uint32_t adcData[4]; static
  5. Interesting suggestion! First, a bit of calculation: At the end of my loop, I move a pin high and low. After doing some measurements on how quickly that happens, I've noticed that the loop frequency is around 125 kHz. When using serial port in the traditional way, we have 1 start bit, 8 data bits and one stop bit. So that's 10 bits per loop iteration. If I don't want to overfill the FIFOs, I'll need data rate of at least 1 250 000, so I'll need to do the debugging until the Launchpad works stable at that frequency. Obviously I can't calculate... The ADC is 12 bit, so I'll need at least
  6. Hi! I'm haivng an unusual problem with UART0 on Tiva C Launchpad. I'm also using Code Composer Studio 5.5. What I'm trying to do right now is to do A/D conversion on the microcontroller and send data to a PC via the serial port. Basically, my program right now sets up peripherals and then goes into a while(1) loop where it samples data from the ADC and then sends them via UART. I'm not using interrupts at this point at all. My code looks like this: unsigned const int BaudRate=5000000;//I've tried with lower data rates, but they're not the problem here. int main(void) { ROM_SysC
  7. This one must have been answered somewhere, but Google isn't helping and I'm getting drowned in a sea of unrelated information. So far my standard procedure when programming a MSP430 using a LaunchPad has been to fire up the CCS and use the debug button. That will at one point program the microcontroller and start debugging as expected. What I don't seem to be able to do is o figure out how do I program the microcontroller without actually entering debug mode (is that even possible?).
  8. I just got a new rev 1.5 Launchpad board with the MSO430G2553IN20 and MSP430G2452IN20 chips and have the Code Composer Studio 5.1 installed. I never did any programming on the MSP430 before (and it's been a while since I used C) and am having problems with the included temperature measurement demo. I've set the project to work with the G2553 and changed the include file. Unfortunately, it seems that the G2553 only works with the version 4 of the compiler and with that version, I'm getting errors on lines which say #pragma vector=TIMERA0_VECTOR and #pragma vector=TIMERA1_VE
  • Create New...