Other Parts Discussed in Thread: MSP-FET, ENERGIA
Tool/software: Linux
I got these 'promo' msp430fr2433 launchpads.
The doc says that it comes pre-flashed with "OutOfBox", and when I power up the board, red LED should flash approx. once in 5 seconds. But in fact, it flashes fast, several times per second, and this pattern does not change when I press J1 or J2 or both. And nothing comes over the backchannel UART.
I try to communicate with it via `mspdebug tilib` on Linux. Mspdebug behaves as if everything goes all right, and the red LED 101 on the probe lights up. I flash the supplied BlinkLED_MSP430FR2433.txt, and it reports no error, but there is no change in the blink pattern.
$ mspdebug tilib --allow-fw-update MSPDebug version 0.22 - debugging tool for MSP430 MCUs Copyright (C) 2009-2013 Daniel Beer <dlbeer@gmail.com> This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. MSP430_GetNumberOfUsbIfs MSP430_GetNameOfUsbIf Found FET: ttyACM0 MSP430_Initialize: ttyACM0 Firmware version is 4294967295 MSP430_VCC: 3000 mV MSP430_OpenDevice MSP430_GetFoundDevice Device: (id = 0x0000) 0 breakpoints available MSP430_EEM_Init Chip ID data: 03 00 55 Available commands: = erase isearch power save_raw simio alias exit load prog set step break fill load_raw read setbreak sym cgraph gdb md regs setwatch verify delbreak help mw reset setwatch_r verify_raw dis hexout opt run setwatch_w Available options: color gdb_loop enable_bsl_access gdbc_xfer_size enable_locked_flash_access iradix fet_block_size quiet gdb_default_port Type "help <topic>" for more information. Use the "opt" command ("help opt") to set options. Press Ctrl+D to quit. (mspdebug) prog BlinkLED_MSP430FR2433.txt Erasing... Programming... Writing 218 bytes at c400... Writing 8 bytes at ff80... Writing 38 bytes at ffda... Done, 264 bytes total (mspdebug) regs ( PC: 00000) ( R4: 00000) ( R8: 00000) (R12: 00000) ( SP: 00000) ( R5: 00000) ( R9: 00000) (R13: 00000) ( SR: 00000) ( R6: 00000) (R10: 00000) (R14: 00000) ( R3: 00000) ( R7: 00000) (R11: 00000) (R15: 00000) 0x0000: 00000: d0 38 JL 0x01a2 00002: ab 97 fc 7f CMP @R7, 0x7ffc(R11) 00006: 00 00 BRA @PC 00008: 01 00 MOVA @PC, SP 0000a: 00 00 BRA @PC 0000c: 00 00 BRA @PC 0000e: 00 00 BRA @PC (mspdebug) regs ( PC: 00000) ( R4: 00010) ( R8: 00000) (R12: d368da60) ( SP: 00000) ( R5: 00000) ( R9: 00000) (R13: da4cce00) ( SR: 97ab33a8) ( R6: 00000) (R10: 00000) (R14: 00000) ( R3: 97ab3440) ( R7: 6884cb94) (R11: d368d560) (R15: 00010) 0x0000: 00000: d0 38 JL 0x01a2 00002: ab 97 fc 7f CMP @R7, 0x7ffc(R11) 00006: 00 00 BRA @PC 00008: 01 00 MOVA @PC, SP 0000a: 00 00 BRA @PC 0000c: 00 00 BRA @PC 0000e: 00 00 BRA @PC (mspdebug) regs ( PC: 00000) ( R4: 00010) ( R8: 00000) (R12: d368da60) ( SP: 00000) ( R5: 00000) ( R9: 00000) (R13: da4cce00) ( SR: 97ab33a8) ( R6: 00000) (R10: 00000) (R14: 00000) ( R3: 97ab3440) ( R7: 6884cb94) (R11: d368d560) (R15: 00010) 0x0000: 00000: d0 38 JL 0x01a2 00002: ab 97 fc 7f CMP @R7, 0x7ffc(R11) 00006: 00 00 BRA @PC 00008: 01 00 MOVA @PC, SP 0000a: 00 00 BRA @PC 0000c: 00 00 BRA @PC 0000e: 00 00 BRA @PC (mspdebug) run Running. Press Ctrl+C to interrupt... ^C ( PC: 00000) ( R4: d368da60) ( R8: 97ab38d0) (R12: 00000) ( SP: 6884d065) ( R5: da4cce00) ( R9: 00001) (R13: 00000) ( SR: 46505845) ( R6: d368da60) (R10: d366ee00) (R14: 00002) ( R3: d368d560) ( R7: 00001) (R11: d324db8c) (R15: 00000) 0x0000: 00000: d0 38 JL 0x01a2 00002: ab 97 fc 7f CMP @R7, 0x7ffc(R11) 00006: 00 00 BRA @PC 00008: 01 00 MOVA @PC, SP 0000a: 00 00 BRA @PC 0000c: 00 00 BRA @PC 0000e: 00 00 BRA @PC (mspdebug)
I got two boards and they behave the same way.
This all works with the old G2 launchpad and rf2500 driver.
Am I doing anything wrong? What's going on?
Thanks!