Jump to content

Lord anubis

  • Content Count

  • Joined

  • Last visited

Everything posted by Lord anubis

  1. Cool project! Eh this is hot, You have a stalker here now.
  2. Just a question, why not just one type of ring design? the part that has/need the mcu with the other elektric parts will morphs that ring element as the master. When there are no parts there is no connection.. Not cheaper? Only need one designed pcb to order.
  3. Ouch, yes I see your in terrible need. You need some advise: please send only one posting and edit your posting to add text, explanation, information or whatever. This looks silly, don't you think so? Does your request has to do with the ledring or using the MSP-EXP430G2? If it is just about a project with CSS with the MSP-EXP430G2, create a new topic.
  4. Hi Claudia, This is nice, please tell us more! Thank you
  5. Thanks, and pitty. Are the known bugs all noted in this topic, or did you found newer ones? If so, any change that the design will be updated?
  6. Wow, just finding this great project. Stil possible to order some parts?
  7. Hi, if I want to use two or three INA219's, do I need to worry about the V- and GND or when two V- are have the same starting point but V+ ( of course ) not, visa versa? I wil do another display of course. Thank you
  8. Lord anubis


    I believe you, but is this documented somewhere? Somebody knows?
  9. Hi, where did you find inf o about attachInterrupt? I did do a google search like "stellaris attachInterrupt" and I found this topic.
  10. Hey Sir. The video is still private.
  11. This is a common/known issue. Annoying, happens sometimes under the osx too. Just FYI, About the code supplied by SirPatrick, it doesn't start from the minimum step till the maximum step. It starts from servo_lut[0] = 661 and ends at servo_lut[180] = arround 2640. 181 steps So the noted duty cycle 0-100% is not managed. The following // Go to 0
  12. The link is damaged. the url is doubled. Should be: http://dl.dropbox.com/u/31742622/stellaris.zip
  13. Great job. Do you have some specs? Can you give some scoop image from the wave? That would be nice. What about SysCtlClockSet(SYSCTL_SYSDIV_2_5, SYSCTL_USE_PLL | SYSCTL_OSC_MAIN_SYSCTL | SYSCTL_XTAL_16MHZ); This give 80Mhz, right? Is that usable? Thank you. Edit. Thank you for the images above and under
  14. Hi, busy making a counter myself using an Stellaris and a 74HC573. I then notice this project. A question, independing of the mcu type, are you playing with a circuit to put in front of the counter input to play it save with voltages from 3,3 till 24V. Like cmos and TTL niveaus and sinus waves? Like to have the brownout zeners to protect the input gates. Any suggestions? Thank you very much.
  15. Compiling was oke, but at the end of linking, the (re)placing of the lib failed. The path showed in the log where the lib will be placed was still in the C:/Stellaware/../... folder. But it fails, nothing/no change to see there. Actually I did expect that the lib files should be created somewhere in the Project folder.
  16. Okay, still didn't work. The result libs where linked/wired to the original place and didn't get build. So the import/copy was not a real 'copy in workspace'. A bug? Anyway not what I did expected. So, I did copy the stellaris folder to a different place, my work folder, did create a new workspace for Libs. From there I did create a Project by importing the lib, build it and it was fine. Add in my other project under the linker search path the lib and search path and that went also fine. I start thinking that there is a Stellaware install problem because I read more about missing part
  17. Thanx, stil confusing. Just for my understanding, I see no change in the .lib. It is not rebuild. Also just a copy doesn't make it a release under BSD license? Most of the time a debug lib is different in size then a release lib. right? Also, shouldn't I choose in your last image the release version instead of the debug version?
  18. During the workbook and some own created test I notice that I have an lib thats build in debug mode. Thanks to the answer there and collecting the reading stuff, I did read a little about the ROM_xxxx, MAP_xxxx. Anyway, I still would like to have the driverlib release build. Specialy during development, can allways later change the calls to ROM_functions. Is there a way, (a tut), to build this under window's. Knows a little about make and the makefiles under windows. Found some make stuff from arround 2003. Did found also at TI the BSD licened LM4 makefiles. Don't have linux but
  19. Thank you, I did read a little about the ROM_xxxx, MAP_xxxx. Anyway, I still would like to have the driverlib release build. Specialy during development, can allways later change the calls to ROM_functions. Any way, is there a way, (a tut), to build this under window's. Knows a little about make and the makefiles under windows. Did found the BSD licened LM4 makefiles. Don't have linux but do have osx, but would like to have it all on one ( win ) platform. There is a lot to read, but would like to be fruitfull asap. Thank you. Btw should I stay in this topic or copy my
  20. Hi, I did add that path before, but I found out that when I presses ok it didn't save the path, even after a CCS restart. After a restart from VMWare it saved the path. So it looks like it is okay. Thank you for the hint that make me look again at that setting. One more question, I did insert the path used in the workbook for lab2 in the debug setting. What about the release settings, do I have to use the same path or is there a release version of the lib?
  21. I am using CCS, the latest stable version. In my post at Posted Today, 02:43 PM you see the path that I included. Your help is appreciated.
  22. Of course, its a copy of the workbook sample lab2 #include "inc/hw_types.h" #include "inc/hw_memmap.h" #include "driverlib/sysctl.h" #include "driverlib/gpio.h" int main(void) { int LED = 2; SysCtlClockSet(SYSCTL_SYSDIV_4|SYSCTL_USE_PLL|SYSCTL_XTAL_16MHZ|SYSCTL_OSC_MAIN); SysCtlPeripheralEnable(SYSCTL_PERIPH_GPIOF); GPIOPinTypeGPIOOutput(GPIO_PORTF_BASE, GPIO_PIN_1|GPIO_PIN_2|GPIO_PIN_3); while(1) { // Turn on the LED GPIOPinWrite(GPIO_PORTF_BASE, GPIO_PIN_1|GPIO_PIN_2|GPIO_PIN_3, LED); // Delay for a bit SysCtlDelay(2000000); // Cycle through Red, Green and Blue
  23. Yes, I have also no question marks. They did disappear when I save the additional include path. Also if I click on a undefined symbol and right click I can find the reference. So it knows where to look and find, I guess. --include_path="C:/Program Files/Ti_tools/StellarisWare/" it is the workbook lab2 code.
  24. Some other weird stuff. I got during linking the following undefined first referenced symbol in file --------- ---------------- GPIOPinTypeGPIOOutput ./main.obj GPIOPinWrite ./main.obj SysCtlClockSet ./main.obj SysCtlDelay ./main.obj SysCtlPeripheralEnable ./main.obj error #10234-D: unresolved symbols remain This is about the main.obj file. It looks like it doesn't find the Libraries. Am I right? After setting a more verbose mode and keeping some asm in
  • Create New...