Jump to content
43oh

gcb

Members
  • Content Count

    16
  • Joined

  • Last visited

About gcb

  • Rank
    Member

Profile Information

  • Sparkfun
    i get all my wishes from china.
  1. sure, did that one the other thread... viewtopic.php?f=38&t=3370 olivluca sent me to the wiki page with the linux driver fix (afraid to call that a fix since it will give problems for other use cases down the road, but hey, i get data and i couldn't do better anyway maybe need to link that wiki page from the main serial page? i thought i had gone trhu all wiki pages until olivluca sent me that link. I think that a generic example on how to probe A10 would sufice for me to understand it. The page you link to is pretty much my new wallpaper but it does not mention anythin
  2. I did a quick look on wiring_analog.c and can't see anything obvious why analogRead on the temp sensor shouldn't work. it even seems to prefer the settings for the internal temp sensor...
  3. in pins_energia.h A10 and P2_2 equal 10. Does that means analogRead is definitely not the way to read the temp sensor? /* attach leds and resistors on pins 1.0 , 1.3 to 2.1 */ // heart beat int ledState = LOW; long previousMillis = 0; // the follow variables is a long because the time, measured in miliseconds, // will quickly become a bigger number than can be stored in an int. long interval = 1000; // interval at which to blink (milliseconds) void setup() { // set the digital pin as output: pinMode(GREEN_LED, OUTPUT); // green led for heart beat // segment leds p
  4. Now that i got serial to work (linux driver issue), i had to move those led pins around... now they are on P1_0 and then P1_3 to P2_1 but still, now i have: x = analogRead(A10); light(x, 120); Serial.println(x); as soon as i run the 1st line here, LED connected to 1.3 goes dark (or dimmed... can't really tell as i'm using a 10segment display and there's some light bleeding from the others) serial is working fine, even though the code before having serial dimmed the leds on TX,RX, now it seems to have no effect on serial communications. on the serial line i keep gett
  5. also, using PIN 1.1 and 1.2 was jamming the data on my other test... i though it was required only for software serial... but if I have a led there as soon as i start the serial code i get led on 1.2 lit.
  6. hum... it didn't showed up on the wiki before ... ah, i was looking at home, not "Pages" let me try this. thanks. update: took some time to build the module... the zip file had a all files with DOS termination and i was getting errors in the build logs such as: "directory /perfectly/valid/dir do not exist" only to find out the ^M at the end of the path didn't show up in the logs as well :? after converting to unix ( vim file -c "set ff=unix" -c "wq" ) install.sh, Makefile, *.c, *.conf it worked. My new dmesg: [26834.944045] usb 3-1: new full-speed USB device number 17
  7. nothing too complex. just used two female jumper cables.
  8. Since I'm having trouble getting my serial to work, i'm thinking of other ways to probe the values from a sensor i have... so i attached a few leds to P1_0 to P1_5 and light them up based on the values i'm getting so i can probe around and find the range the sensor work. before i hook up the sensor i tried to test it out with the internal temperature sensor and found this oddity... it may very well be something extremely dumb with my code... /* attach leds and resistors on pins 1.0 to 1.5 */ // heart beat int ledState = LOW; long previousMillis = 0; // the follow variabl
  9. tried all the ways... with it in parallel (as the board comes) with it crossed, with the pins opens still nothing... I do get different kernel messages depending on how i plug it: dmesg with pins in parallel Oct 14 11:54:10 hobo kernel: [ 4924.852052] usb 3-1: new full-speed USB device number 8 using uhci_hcd Oct 14 11:54:10 hobo kernel: [ 4925.056066] usb 3-1: New USB device found, idVendor=0451, idProduct=f432 Oct 14 11:54:10 hobo kernel: [ 4925.056072] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 14 11:54:10 hobo kernel: [ 4925.056075] usb 3-1: Produc
  10. I can never get any serial output on the serial window. i'm building from source. currently from d5632bb6a844dd59c57029ec7a56d890db80201b (also, my window says "Energia ${version}" so there's may be something wrong with the way i'm building... i.e. just typing `ant`) i'm using a rev1.4 board with a G2553, nothing else attached. also tried using minicom to listen on port /dev/ttyS0 to S3 and ttyACM0 with 8N1 9600, same silence. lsusb Bus 003 Device 003: ID 0451:f432 Texas Instruments, Inc. eZ430 Development Tool Device Descriptor: bLength 18 bDes
  11. I'm trying to make the launchpad talk serial at 57600 or 19200 baud. i tried reading slaa322b, but it mostly passed over my head and the only think i learned from it is that everything will go wrong if i use a crystal... but let's go... first thing i noticed is that even 19200 is more than half the 32760. Can i hope to do anything useful at 0.589x my max clock? I'm still unsure how the clock relates to the cpu instruction cycle... i gathered there's the cpu bound clock at 32khz, and an optional peripheral clock that can go up to 100mhz... but i think those other clocks are moot for m
  12. Is it 100% usable with mainline gcc and vanila kernels? i'm out of touch with msp430s for some time because of the retarded hops i had to take at the time.. granted i didn't look back in some time.
  13. and how do i declare the interrupts? the manual says to use signal.h http://mspgcc.sourceforge.net/manual/x918.html The code i find around uses magic strings that i can't find in msp430.h, e.g. interrupt(PORT1_VECTOR) Port_1(void) { which fail: msp430-gcc -Os -Wall -g -mmcu=msp430g2231 -c uart.c uart.c:36:6: warning: return type of
  14. btw ...should i be using something else than msp430-gcc?
  15. pretty much all the code/tutorials i find about interrupts use signal.h and it's macros. and signal.h on my current headers (msp430-gcc (GCC) 4.5.3) complains it's deprecated and 1) should not be used 2) use legacymsp430.h well, i tried #2 first, it fails. then i tried to see what I should be using instead, and failed. everything i found uses signal.h Any doc/sample code i should be looking? the manuals is all about signal.h (link to manual that i can't include because new users can't post links)
×
×
  • Create New...