Jump to content

nbm

Members
  • Content Count

    3
  • Joined

  • Last visited

Everything posted by nbm

  1. Found a solution that works, given a Windows machine: https://blog.kutej.net/2019/03/msp-exp430g2et-linux This is a pretty serious bug if you want to claim to have Linux support.
  2. Checked out and tried the latest version of mspdebug.
  3. I got an MSP-EXP430G2ET yesterday, and after installing drivers and Energia (Debian unstable) I plugged it in and opened up the blink example. Energia spat out some messages about the firmware needing updating, and started the process. I don't have the log (it's fallen off my console's buffer) but it did not appear to complete successfully. Now, when I try to use Energia to flash the blink example, I get this: Sketch uses 386 bytes (2%) of program storage space. Maximum is 16384 bytes. Global variables use 20 bytes (3%) of dynamic memory, leaving 492 bytes for local variables. Maximum is 512 bytes. DSLite version 9.3.0.1863 Configuring Debugger (may take a few minutes on first launch)... Initializing Register Database... Initializing: MSP430 error: MSP430: Error initializing emulator: One of the connected MSP-FETs / eZ-FETs debuggers needs recovery. Select 'Recover' to start the recovery process. Note: Only one MSP-FET / eZ-FET debugger can be connected to your system during recovery. Updating Firmware error: MSP430: Error: MSP-FET / eZ-FET recovery failed Failed: MSP430: Error initializing emulator: MSP-FET / eZ-FET recovery failed the selected serial port does not exist or your board is not connected It's interesting that it says DSLite even though I selected mspdebug through the tools menu. So I figured I'd try just compiling a trivial C program and flashing it manually. $ mspdebug tilib appears to work, as long as I have the appropriate .so file in my dynamic loader's search path. However, this happens when I try to flash anything. $ LD_LIBRARY_PATH=energia-1.8.10E23/hardware/tools/DSLite/DebugServer/drivers/ mspdebug tilib 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: HID_FET MSP430_Initialize: HID_FET Firmware version is 4294967294 MSP430_VCC: 3000 mV MSP430_OpenDevice MSP430_GetFoundDevice Device: (id = 0x0000) 0 breakpoints available MSP430_EEM_Init Chip ID data: 02 00 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 minimal.elf Erasing... Programming... Writing 80 bytes at c000 [section: .text]... Writing 32 bytes at ffe0 [section: .vectors]... Done, 112 bytes total (mspdebug) verify minimal.elf Verifying 80 bytes at c000 [section: .text]... ERROR: mismatch at c000 (read 00, expected 55) (mspdebug) I suspect this is a problem with the on-board debugger. Any information on how to fix this would be appreciated.
×
×
  • Create New...