Connection timed out

[chenboshuo]

I'm using MSP430G2553
platform ubuntu 20.04

ls -l /dev/serial/by-id  

then I get

lrwxrwxrwx 1 root root 13 7月   1 20:51 usb-Texas_Instruments_MSP_Tools_Driver_721F896E22000100-if00 -> ../../ttyACM0
lrwxrwxrwx 1 root root 13 7月   1 20:51 usb-Texas_Instruments_MSP_Tools_Driver_721F896E22000100-if02 -> ../../ttyACM1

so I use the command

python msptool.py -f blinky.txt -p /dev/ttyACM0

but it not worked

msptool v0.3
Executing: ./mspdebug/mspdebug rom-bsl -d /dev/ttyACM0 "prog blinky.txt"
MSPDebug version 0.24 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2016 Daniel Beer <[email protected]>
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Chip info database from MSP430.dll v3.3.1.4 Copyright (C) 2013 TI, Inc.

rom_bsl: bad ack character: 5
rom_bsl: bad ack character: 92
rom_bsl: sync failed
rom_bsl: failed on command 0x1e (addr = 0x0000, len = 0x0000)
warning: rom_bsl: failed to read version
Performing mass erase...
rom_bsl: bad ack character: 5
rom_bsl: bad ack character: 92
rom_bsl: sync failed
rom_bsl: failed on command 0x18 (addr = 0xfffe, len = 0xa506)
rom_bsl: initial mass erase failed
rom_bsl: failed to unlock
Resetting...

and I tried

python msptool.py -f blinky.txt -p /dev/ttyACM1

it failed,too

Executing: ./mspdebug/mspdebug rom-bsl -d /dev/ttyACM1 "prog blinky.txt"
MSPDebug version 0.24 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2016 Daniel Beer <[email protected]>
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Chip info database from MSP430.dll v3.3.1.4 Copyright (C) 2013 TI, Inc.

rom_bsl: failed to receive reply: Connection timed out
rom_bsl: failed to receive reply: Connection timed out
rom_bsl: sync failed
rom_bsl: failed on command 0x1e (addr = 0x0000, len = 0x0000)
warning: rom_bsl: failed to read version
Performing mass erase...
rom_bsl: failed to receive reply: Connection timed out
rom_bsl: failed to receive reply: Connection timed out
rom_bsl: sync failed
rom_bsl: failed on command 0x18 (addr = 0xfffe, len = 0xa506)
rom_bsl: initial mass erase failed
rom_bsl: failed to unlock
Resetting...

Could you tell me how to connect? Thank you

[lorforlinux]

Hey @chenboshuo,

Please share the output of $ lsusb after connecting the USB-UART bridge.

and I tried
python msptool.py -f blinky.txt -p /dev/ttyACM1

/dev/ttyACM1 would be something like /dev/ttyUSB0 for the USB to UART bridge.

After getting the correct port follow the connection diagram available in the repository.
Check if you have correctly connected the RST and DTR of the USB-UART bridge to the MSP430G2553 MCU.

[chenboshuo]

Please share the output of $ lsusb after connecting the USB-UART bridge.
The output is

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 004: ID 0cf3:e500 Qualcomm Atheros Communications 
Bus 001 Device 003: ID 5986:06b3 Acer, Inc EasyCamera
Bus 001 Device 009: ID 2047:0013 Texas Instruments MSP Tools Driver
Bus 001 Device 002: ID 25a7:9ab6 BJX 2.4G Mouse
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

In the mainstream manual,
they use /dev/ttyUSB0,
but I don't have it,
when I type

ls /dev/tty*

I get

/dev/tty    /dev/tty21  /dev/tty35  /dev/tty49  /dev/tty62      /dev/ttyS15  /dev/ttyS29
/dev/tty0   /dev/tty22  /dev/tty36  /dev/tty5   /dev/tty63      /dev/ttyS16  /dev/ttyS3
/dev/tty1   /dev/tty23  /dev/tty37  /dev/tty50  /dev/tty7       /dev/ttyS17  /dev/ttyS30
/dev/tty10  /dev/tty24  /dev/tty38  /dev/tty51  /dev/tty8       /dev/ttyS18  /dev/ttyS31
/dev/tty11  /dev/tty25  /dev/tty39  /dev/tty52  /dev/tty9       /dev/ttyS19  /dev/ttyS4
/dev/tty12  /dev/tty26  /dev/tty4   /dev/tty53  /dev/ttyACM0    /dev/ttyS2   /dev/ttyS5
/dev/tty13  /dev/tty27  /dev/tty40  /dev/tty54  /dev/ttyACM1    /dev/ttyS20  /dev/ttyS6
/dev/tty14  /dev/tty28  /dev/tty41  /dev/tty55  /dev/ttyprintk  /dev/ttyS21  /dev/ttyS7
/dev/tty15  /dev/tty29  /dev/tty42  /dev/tty56  /dev/ttyS0      /dev/ttyS22  /dev/ttyS8
/dev/tty16  /dev/tty3   /dev/tty43  /dev/tty57  /dev/ttyS1      /dev/ttyS23  /dev/ttyS9
/dev/tty17  /dev/tty30  /dev/tty44  /dev/tty58  /dev/ttyS10     /dev/ttyS24
/dev/tty18  /dev/tty31  /dev/tty45  /dev/tty59  /dev/ttyS11     /dev/ttyS25
/dev/tty19  /dev/tty32  /dev/tty46  /dev/tty6   /dev/ttyS12     /dev/ttyS26
/dev/tty2   /dev/tty33  /dev/tty47  /dev/tty60  /dev/ttyS13     /dev/ttyS27
/dev/tty20  /dev/tty34  /dev/tty48  /dev/tty61  /dev/ttyS14     /dev/ttyS28

So I use this command

ls -l /dev/serial/by-id  

To find it.
reference:How to match a ttyUSBX device to a usb serial device

[lorforlinux]

Hey @chenboshuo, did you get the issue resolved?