[Mspgcc-users] msp430fr4133

2019-08-01 Thread Arhitektor
Hello. I am newbe in microcontrollers. I have msp430fr4133. And I want to make 
"hello world" - led blinking on it. For this purpose I used resources:
https://github.com/jlhonora/mspgcc-install
www.simplyembedded.org/tutorials/build-msp340-gcc-toolchain/

So I 
- installed lubuntu in virtualbox;
- apt-get install gcc-msp430;
- write this code:
   
   into main (void)
{

  return 0;
}

- then compiled: 
$ msp430gcc -mmcu=msp430fr4133 main.c
/use/lib/GCC/msp430/4.6.3/../../../..msp430/bin/LD: cannot open linker script 
file memory.x: No such file or directory
collect2: LD returned 1 exit status


In general before previous step I manually add libraries to /usr/msp430/include 
from 
http://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/MSPGCC/latest/index_FDS.html
 
msp430-gcc-support-files-1.207.zip
because compiler complained to lack of msp430fr4133 header.

I'll be thankful for any help.


___
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users


[Mspgcc-users] flash_firmware_to_msp430fr4133

2019-08-09 Thread arhitektor
Hello. I need your help again.
Program for msp430fr4133 compiled succefully. Next step according to the 
tutorial http://www.simplyembedded.org/tutorials/blinking-led/ is flash *.hex 
file with mspdebug. Mspdebug from debian repository v0.22 without a driver 
(ezfet) for my msp430fr4133. So build mspdebug v0.25 from source. When I launch

# ./mspdebug ezfet
MSPDebug version 0.25 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2017 Daniel Beer 
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.13.0.601 Copyright (C) 2013 TI, Inc.
Reset communications...
Version: 2.4.1.901, HW: 0x
Reset firmware...
hal_proto_execute: HAL exception: 0x
hal_proto_execute: fid: 0x51 
And red led101 fired on board.

Searching for HAL exception (https://github.com/dlbeer/mspdebug/issues/43) show 
a solution - use tilib driver. --> Need to build libmsp430.so from source. 
Correspond to libmsp430 readme file I built it with libboost_v.1.56. According 
to information about tilib driver in mspdebug man page

root@msp430:/home/user/msp430/mspdebug/mspdebug-master# whereis libmsp430.so
libmsp430: /usr/local/bin/libmsp430.so /usr/local/lib/libmsp430.so
root@msp430:/home/user/msp430/mspdebug/mspdebug-master# export 
MSPDEBUG_TILIB_PATH=/usr/local/bin
root@msp430:/home/user# ldconfig

When I launch

# ./mspdebug tilib
MSPDebug version 0.25 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2017 Daniel Beer 
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.13.0.601 Copyright (C) 2013 TI, Inc.
tilib_api: can't find libmsp430.so: libboost_filesystem.so.1.56.0: cannot open 
shared object file: No such file or directory

Some attempts to solve this error myself show that I think wrong

root@msp430:/home/user/msp430/mspdebug/mspdebug-master# ln -s 
/usr/local/bin/libboost_filesystem.so.1.56.0 /lib/libboost_filesystem.so.1.56.0 
 
root@msp430:/home/user/msp430/mspdebug/mspdebug-master# ln -s 
/usr/local/bin/libboost_system.so.1.56.0 /lib/libboost_system.so.1.56.0
root@msp430:/home/user/msp430/mspdebug/mspdebug-master# ldconfig
root@msp430:/home/user/msp430/mspdebug/mspdebug-master# ./mspdebug tilib
MSPDebug version 0.25 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2017 Daniel Beer 
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.13.0.601 Copyright (C) 2013 TI, Inc.

tilib_api: can't find libmsp430.so: libboost_date_time.so.1.56.0: cannot open 
shared object file: No such file or directory

How can I flash board with *.hex file?
---
# uname -a
Linux msp430 4.19.0-5-amd64 #1 SMP Debian 4.19.37-5+deb10u1 (2019-07-19) x86_64 
GNU/Linux

# udevadm info /dev/ttyACM0
P: /devices/pci:00/:00:06.0/usb2/2-2/2-2:1.0/tty/ttyACM0
N: ttyACM0
L: 0
S: serial/by-id/usb-Texas_Instruments_MSP_Tools_Driver_0EAEB46F09000500-if00
S: serial/by-path/pci-:00:06.0-usb-0:2:1.0
E: DEVPATH=/devices/pci:00/:00:06.0/usb2/2-2/2-2:1.0/tty/ttyACM0
E: DEVNAME=/dev/ttyACM0
E: MAJOR=166
E: MINOR=0
E: SUBSYSTEM=tty
E: USEC_INITIALIZED=21161867622
E: ID_BUS=usb
E: ID_VENDOR_ID=2047
E: ID_MODEL_ID=0013
E: ID_PCI_CLASS_FROM_DATABASE=Serial bus controller
E: ID_PCI_SUBCLASS_FROM_DATABASE=USB controller
E: ID_PCI_INTERFACE_FROM_DATABASE=OHCI
E: ID_VENDOR_FROM_DATABASE=Texas Instruments
E: ID_MODEL_FROM_DATABASE=KeyLargo/Intrepid USB
E: ID_VENDOR=Texas_Instruments
E: ID_VENDOR_ENC=Texas\x20Instruments
E: ID_MODEL=MSP_Tools_Driver
E: ID_MODEL_ENC=MSP\x20Tools\x20Driver
E: ID_REVISION=0200
E: ID_SERIAL=Texas_Instruments_MSP_Tools_Driver_0EAEB46F09000500
E: ID_SERIAL_SHORT=0EAEB46F09000500
E: ID_TYPE=generic
E: ID_USB_INTERFACES=:020201:0a:
E: ID_USB_INTERFACE_NUM=00
E: ID_USB_DRIVER=cdc_acm
E: ID_USB_CLASS_FROM_DATABASE=Miscellaneous Device
E: ID_USB_PROTOCOL_FROM_DATABASE=Interface Association
E: ID_PATH=pci-:00:06.0-usb-0:2:1.0
E: ID_PATH_TAG=pci-_00_06_0-usb-0_2_1_0
E: ID_MM_CANDIDATE=1
E: 
DEVLINKS=/dev/serial/by-id/usb-Texas_Instruments_MSP_Tools_Driver_0EAEB46F09000500-if00
 /dev/serial/by-path/pci-:00:06.0-usb-0:2:1.0
E: TAGS=:systemd:

# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 006: ID 2047:0013 Texas Instruments 
Bus 002 Device 005: ID 80ee:0021 VirtualBox USB Tablet
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

# apt install patch ncurses-dev build-essential bison flex libgmp3-dev 
libmpfr-dev libmpc-dev texinfo zlib1g-dev libusb-dev libreadline6-dev libz-dev 
<--this packets installed.


___
Mspgcc-users mailing list