Jump to content
43oh

jmparatte

Members
  • Content Count

    11
  • Joined

  • Last visited

Everything posted by jmparatte

  1. Now, I've 6 MSP-EXP430G2 to trash... I'm a little bit furious against TI which couldn't hear desperate customers !
  2. Today, I've received my new LaunchPad MSP-EXP430F5529LP. The W8.1x64 MSP430 Application UART works like a charm... Apparently same with OpenWrt /dev/ttyACMx. No sorrry, the serial hangs after a couple of minutes ! (verified many times)
  3. The above technics don't solve the Windows driver problem !
  4. Many thanks to spirilis, I confirm the "do not send any characters before open the driver". I can add it's the same to close the driver. My configuration is LaunchPad msp430g2 connected to TL-MR3020 freshly flashed with OpenWrt attitude, and associative packages. I've used picocom to connect to /dev/ttyACM0 and do checks. The msp430 program sends a character every seconds. So I've connected like that: 1/ Maintain pressed the Reset button of msp430 LaunchPad. 2/ Connect the LaunchPad to USB while maintaining Reset. 3/ Start picocom /dev/ttyACM0 4/ Observe that the message "Term
  5. I'm developping some codes with Energia or TI CCS for the TI LaunchPad MSP-EXP430G2, v1.4 and v1.5, with G2553 and G2452 chips. I organize DIY workshops. I'm playing with various computers, I enumarate them: 1x W7Pro32, 1x W7Starter, 1x W8.1x64, 1x TP-Link TL-MR3020+OpenWrt, 1x TP-Link WR710N+OpenWrt. Nothing is going right with serial, only my old W7Pro32 can read/write thru the USB serial ! Even my 2 OpenWrt TP-Link can't communicate ! If I play with some Arduino in place of TI LaunchPad, all USB serial is working fine (except the known reset problem of Arduino USB serial). Y
  6. Thanks Peter, I will investigate MSPGCC and its compatibility with CCS.
  7. Hi pabigot, Is it difficult to switch from the internal CCS compiler to MSPGCC? And preserve CCS environment! jmP
  8. Hi oPossum, Simplified inline functions push and pop as your propose are unfortunately not a good solution because the compiler doesn't follow the mormal rules of calling parameters and returns. The compiler (CCS 4.2) inserts the source of the inline function and makes a global optimization of the code, so doesn't systematically use R12 calling arguments and return, neither put CALL and RET. Your first solution which is to place a single asm("...") referring an external variable is interesting. In practice it's a little waste of codes because the foo referred variable must be a global
  9. I've build a console language. It's a "tiny Forth" crossed with some "C syntaxes". I've named it "Corth". Arguments and results are pushed/poped on/from the stack processor. The heap is free for other needs or simply unused.
  10. Moving from AVR and GCC compiler to MSP430 and CCS, I wish 2 new intrinsics like my old: static inline void PUSH (uint16_t u) { asm volatile ( "push %B0" "\n\t" "push %A0" "\n\t" : : "r" (u) ); } static inline uint16_t POP () { uint16_t result; asm volatile ( "pop %A0" "\n\t" "pop %B0" "\n\t" : "=r" (result) ); return result; } At moment, I've solved with: inline void PUSH (uint16_t u) { _set_R4_register(u); asm(" PUSH.W R4"); } inline uint16_t POP () { asm(" POP.W R4"); return _get_R4_register(); } I think it's inelegant because I need to use the register R4.
  11. I've made also some experimentations about clocking the G2231 with an external clock 16MHz. Before reading your code, I experimented a solution near yours, but with a little change: the ACLK is driven with an external clock and the MCLK is driven with the internal DCO. I will explain it far. First I tried your code. It works. See below my code test: void main (void) { WDTCTL = WDTPW + WDTHOLD; // Stop watchdog timer BCSCTL3 = LFXT1S_3 | XCAP_0; // Digital external 0.4- to 16-MHz clock source // Drive ACLK, MCLK & SMCLK with digital external clock source on XIN pin... // LFXT1C
×
×
  • Create New...