Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Lyon

  1. Hi, A few words about your problem: 1) since you need a sd-card example, maybe the best way is to download the Tiva package from TI - there is an example which run on CCS (and i suggest to move to CCS, since the Energia does not have a debugger, AFAIK). The sd-card configuration starts by sending some data at the rate of 400KHz, in SPI mode 0, toggling CS on every byte. Then after that, when the communication is established, the frequency is changed to 12MHz. 2) since you made some test on another device type (and function) - many devices uses mode 0 and mode 3 or mode 1 and mode 3, so you
  2. Hi, A nice application note on SAR ADCs can be found here: https://www.ti.com/seclit/sl/slyc140/slyc140.pdf Useful for using ADCs on Tiva and not only.
  3. After (f=='2'), f is changed to '3' where there is not any option to process for that. Shouldn't be f=1 again to toggle between the two options? L
  4. Hi, A nice GUI for MAC can be build from Eclipse + the plugin from this link: http://gnuarmeclipse.github.io The result is something powerful as CCS, if you add openOCD. Also openOCD can be used from terminal, so you have another tool to flash a .bin file.
  5. Hi, Please see this link: http://www.elecfreaks.com/wiki/index.php?title=Bluetooth_Bee#Programming It is stated that your device is/ has AT compatible protocol, so your commands should be prefixed by AT. The link has a test program written in Energia, you may try that. As for your code, while you claim starting with qs-rgb, your file is uart-stdio, which may be unsuitable for your purpose. Depending on ypur real application, you must make new software functions to include these AT commands. L
  6. Hi, But the driverlib functions are consistent with the user manual! In general, it is useful to use these instead direct register addressing, for fast programming. This will ease your work. Some other people may comment that this is time consuming. If it is your case, at least look at them and use the function content, without wrapping (some time is really spent in those functions - the ASSERT takes some time, but once the program is debugged, these can be removed). Sometime it is really more convenient to use direct registers - but after you have more experience with this micro. In your ca
  7. Hi, In this case, I suggest to download/install/run the application Pinmux from TI - select then your micro type, configure the pins as you need and the application will generate the initialization code for you. Then compare with your code. Take care will be different, since the Pinmux uses driverlib - you may replace your code or you may inspect the functions used there to see the registers used to initialize the pins. L
  8. Hi, PF3 is on PWM module 1 - PWM7 - so please see what you need to use in chapter PWM of your user manual - and decide then corrections/modifications. L
  9. Hi, For the moment you can trust the samples. Try to test/check other pins also, try an UART or SPI. Since it is your board, check/ double check your board for shorts with other pins/traces - sometimes it may happen to have small, near invisible shorts... Worth to try also a second board if you have. L
  10. Hi, First of all, your JTAG pins must have a pull-up resistors mounted on-board. Second, if you use your Lauchpad board as debug-out ( to debug another board) then you must disable your LP target micro ( the test/target micro from LP board, the debug one should be active). You can do that by short-circuit of reset capacitor on LP board. L
  11. Hi, For your temperature sensor you may search this forum or TI's Tiva forum, it is possible to find out some posting related to this. The alternative is to use TI's I2C libray and of coarse to dig into the data sheet of your sensor. I know it is bulky, but that is for all specialized sensors. And the interface it is not a simple one, but can be used. L
  12. Hi, At the motobike battery voltage, the ADC offset mostly does not matter, or is within a good accuracy. It can be measured and used into a formula to get better results, but at the expense of some external components. More, you must scale down the voltage to be within the ADC range, (the maximum scaled battery voltage should be less than maximum ADC range) and the scaling is better to be done with resistors and an op-amp, since the ADC input impedance is not so high. TI has all sort of components to make measurements, including temperature sensors. Choose whatever is convenient to you. I p
  13. Hi, We need more info from you - what is your battery voltage (i.e. CR2032, or car battery, or other? We have in production line battery systems even for 110V dc ) and also what kind of themperature do you need to measure - ambient one, battery temperature, chip temperature (there is a temperature sensor on-chip). And what is your temperature sensor? L
  14. Hi, Sorry, do not understand - what do you mean by "make a JTAG circuit manual"? If you mean what alternative you have to get an ICDI device able to debug/flash your board - the answer is yes, there are alternatives, including from TI, one of them (XDS100) can be either baught, ready to use, either you have the whole design available for DIY. L
  15. Hi, First this one: http://www.ti.com/lit/an/spma059/spma059.pdf The second, Launchpad board manual, hope you have it. One word of caution: you say: "can use all function as a Tiva Launchpad without JTAG." but design the board with JTAG connector, otherwise you are lost... L
  16. Hi, For TM4C129x micros, the function SysCtlClockFreqSet() returns the running frequency if the setting was OK or 0 if the result is not OK, so you may have the possibility to save the value and check it in a separate statement. SysCtlClockGet() function should be used only with Tiva123 series, but note there is a small bug inside. Another possibility is the 129 series allow a special pin to be configured as to get out the clock, so you can check it or use it for other purposes. Take care, for testing should be OK, but for production/qualification could be wrong, since this may induce EMC re
  17. Hi, I think the technique is/should be a little bit different - most users/brands uses JTAG chaining for such purposes, and a special PC software, since each micro can be in a different state (i.e.OK, running or Error or...). See this link: http://e2e.ti.com/support/microcontrollers/stellaris_arm/f/471/t/123310.aspx for a small discussion. L
  18. Hi, Today is still sunday, you have several hours to go out with/for girls, tomorrow wold be another good day to aquire new data.... L
  19. Hi, Two small observations: a) UART Studio is a new name, original one is "uartstdio", -stdio comes from standard input-output. UARTprintf provides formatted output only for integers, pointers, strings and chars, while floats or even doubles are avoided. L
  20. Hi, You can add the DEBUG directive with -DDEBUG in Makefile. You may use also the Eclipse to get an IDE with automatic makefile generation. L
  21. Hi, This is related to Digital Function selection (GPIOPCTL PMCx Bit Field Encoding)- see page 648/Table10-2 (GPIO Pins and Alternate Functions). It is the value to be written into PMCx, x=0..7, corresponding to the pin. L
  22. Hi, Unfortunately you forgot to attach the file... L
  23. Hi, Nothing is wrong, all is perfect as it should be. This is the usual behaviour of Cortex-Mx micros, where the interrupt routines (all, including reset_isr) gets an odd address when placed into interrupt vector routines, for signalling the fact the micro should use thumb(2) instructions, and not original ARM. It would be an error to get even address in interrupt vector, and that would lead to interrupt fault. L
  24. Lyon

    Timer prescale

    Hi, Well, mostly No! When counting up in one-shot or periodic modes, the prescaler acts as a timer extension and holds the most-significant bits of the count. In input edge count, input edge time and PWM mode, the prescaler always acts as a timer extension, regardless of the count direction. (From user manual) Since the counting is up and both edges are selected, then the pulse duration is measured - seems this was the goal, reading the code snippet. But: you may verify this with an oscilloscope to confirm the results. Also: since both edges are enabled for capture, then to have
  • Create New...