mspgcc-users — Discussion list for users

[Mspgcc-users] New MSP430-GCC releases available

[Stauber, T. <t-s...@ti...>]

Hello MSP430 GCC-enthusiasts,
We are pleased to announce a new stand-alone & open source production release (v8.3.0.0) of MSP430 GCC available for download:
http://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/MSPGCC/latest/index_FDS.html

This MSP430-GCC release is based on the GCC version 8.3.0.16.
The packages include all binaries, the source code and MSP430 device specific support files. For convenience installers are provided.
The binaries and installers are available for all platforms (Windows 32/64bit, Linux 32/64bit and Mac OSX) and this compiler can be used standalone or selected within Code Composer Studio 9.2.

Main changes in this release are the gcc version update and bug fixes. See the release notes<http://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/MSPGCC/latest/index_FDS.html> for more details.

This MSP430-GCC package based on GCC compiler is maintained by Mitto Systems<http://www.mittosystems.com/>

We would like to continue improving MSP430 GCC offer, so please feel free to send any suggestions or recommendations.
For better tracking and handling please use TI e2e community<https://e2e.ti.com/> to submit your requests.

Best regards,

Thorsten Stauber
________________________________
SW Development Tools • Connected MCUs
Texas Instruments • Freising • +49 8161 80 4079


Texas Instruments Deutschland GmbH, Haggertystr. 1, D-85356 Freising. Amtsgericht München HRB 40960. Geschäftsführer: Andreas Schwaiger. Vorsitzender des Aufsichtsrates: Dr. Klaus Weisel

Re: [Mspgcc-users] flash_firmware_to_msp430fr4133

[Daniel B. <dl...@gm...>]

On Fri, Aug 09, 2019 at 08:58:42AM +0000, arh...@di... wrote:
> # ./mspdebug tilib
> MSPDebug version 0.25 - debugging tool for MSP430 MCUs
> Copyright (C) 2009-2017 Daniel Beer <dl...@gm...>
> 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 <dl...@gm...>
> 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

I'm not sure why your boost libraries are in /usr/local/bin, but it
seems that if you add some more symlinks you'll eventually be able to
load the driver. Do libboost_date_time.so.1.56.0 next, try again, and
keep going until you have no more shared-object errors.

Cheers,
Daniel

-- 
Daniel Beer <dl...@gm...> http://dlbeer.co.nz/
PGP: BA6E 0B26 1F89 246C E3F3  C910 1E58 C43A 160A 553B

[Mspgcc-users] flash_firmware_to_msp430fr4133

[<arh...@di...>]

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 <dl...@gm...>
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: 0xaaaaaaaa
Reset firmware...
hal_proto_execute: HAL exception: 0xffff
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 <dl...@gm...>
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 <dl...@gm...>
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/pci0000:00/0000: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-0000:00:06.0-usb-0:2:1.0
E: DEVPATH=/devices/pci0000:00/0000: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:0a0000:
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-0000:00:06.0-usb-0:2:1.0
E: ID_PATH_TAG=pci-0000_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-0000: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.

Re: [Mspgcc-users] msp430fr4133

[Jozef L. <jo...@mi...>]

Hi,

The version of mspgcc available in the Ubuntu packages is quite old and is
no longer updated.

I would recommend using the new MSP430-GCC toolchain distributed by TI.
Installers and documentation are available here:
http://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/MSPGCC/6_1_1_0/index_FDS.html
The user guide "SLAU646.pdf" that is linked to on that page provides
details on how to run a "Blink the LED" program on your board.

If you wish to use MSP430-GCC in an IDE instead, you can download Code
Composer Studio which is TI's IDE. MSP430-GCC is included in the IDE.
http://software-dl.ti.com/ccs/esd/documents/ccs_downloads.html

If you have issues with MSP430-GCC, we can provide support for you on the
TI e2e forums http://e2e.ti.com/

Regards,
Jozef


On Thu, Aug 1, 2019 at 10:31 AM Arhitektor <arh...@di...> wrote:

> 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:
>    <include msp430fr4133.h>
>    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
> Msp...@li...
> https://lists.sourceforge.net/lists/listinfo/mspgcc-users
>

[Mspgcc-users] msp430fr4133

[Arhitektor <arh...@di...>]

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:
   <include msp430fr4133.h>
   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] New MSP430-GCC releases available

[Stauber, T. <t-s...@ti...>]

Hello MSP430 GCC-enthusiasts,
We are pleased to announce a new stand-alone & open source production release (v8.2.0.52) of MSP430 GCC available for download:
http://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/MSPGCC/latest/index_FDS.html

This MSP430-GCC release is based on the GCC version 8.2.0.
The packages include all binaries, the source code and MSP430 device specific support files.
The binaries are available for all platforms (Windows 32/64bit, Linux 32/64bit and Mac OSX) and this compiler can be used standalone or selected within Code Composer Studio 9.1.

For this specific compiler release, there will be no standalone installer. There will be two further releases based on GCC 8 this year, which will include the latest upstream patches, and additional MSP430-specific bug fixes and features. These releases will include a standalone installer for the toolchain.

This MSP430-GCC 8.2.0.0 package based on GCC compiler 8.2.0 is maintained by Mitto Systems<http://www.mittosystems.com/>

We would like to continue improving MSP430 GCC offer, so please feel free to send any suggestions or recommendations.
For better tracking and handling please use TI e2e community<https://e2e.ti.com/> to submit your requests.

Best regards,

Thorsten Stauber
________________________________
SW Development Tools • Connected MCUs
Texas Instruments • Freising • +49 8161 80 4079


Texas Instruments Deutschland GmbH, Haggertystr. 1, D-85356 Freising. Amtsgericht München HRB 40960. Geschäftsführer: Andreas Schwaiger. Vorsitzender des Aufsichtsrates: Dr. Klaus Weisel

Re: [Mspgcc-users] SYSRIVECT and MSP430F534x and suspect stack overlap

[Hynek S. <ec...@ce...>]

I guess You have to find the linker script You are using, make a copy 
and modify it and then to use it for building Your app.

BR,
Hynek Sladky


Dne 3.11.2018 v 20:09 Daniele Banfi napsal(a):
> Dear All
>
> I'm using a board whit MSP430F534x and I would use the interrupt 
> vector RAM mapping via SYSRIVECT.
>
> Seems correct my assigment of address of interrupt procedure in the 
> ram (top of ram) , according different examples, but when I launch 
> application the debug goes in crash after __enable_interrupt() and I 
> suspect that stack RAM use top RAM (as remapped vector) and in fact.
>
> If is true my suspect of stack/heap corruption, I suppose is necessary 
> to modify the ld file
>
> Can someone else help me regarding ld file, to define in correct way 
> stack limit and reserved ram for SYSRIVECT action ?
>
> Thanks , Daniele

[Mspgcc-users] SYSRIVECT and MSP430F534x and suspect stack overlap

[Daniele B. <dan...@wa...>]

Dear All

I'm using a board whit MSP430F534x and I would use the interrupt vector 
RAM mapping via SYSRIVECT.

Seems correct my assigment of address of interrupt procedure in the ram 
(top of ram) , according different examples, but when I launch 
application the debug goes in crash after __enable_interrupt() and I 
suspect that stack RAM use top RAM (as remapped vector) and in fact.

If is true my suspect of stack/heap corruption, I suppose is necessary 
to modify the ld file

Can someone else help me regarding ld file, to define in correct way 
stack limit and reserved ram for SYSRIVECT action ?

Thanks , Daniele

[Mspgcc-users] SYSRIVECT and MSP430F5342

[daniele.banfi <dan...@wa...>]

Dear All,

I would use the vector remapping in RAM for a product develop with
msp430F5342 and compiled with MSPGCC.

Is clear that SYSRIVECT enable remapping RAM at the top and seems correct my
assigment in RAM of address of interrupt procedure.

But when I try to debug, the appliction goes immediatly in crash; I suppose
becuase the heap/stack used by processor overlap the top RAM area (where
remapping vector are stored).

If is true, I'm in trouble to define in linker file (and source file) how to
redefine the stack area and reserve a RAM area for vector remapping.

Can someonelse help me ?

Thanks, Daniele Banfi





--
Sent from: http://msp430-gcc-users.1086195.n5.nabble.com/

Re: [Mspgcc-users] [EXTERNAL] Re: New MSP430-GCC releases available

[Ghannouchi, Y. <y-g...@ti...>]

Thanks Lev! That's the plan. Mitto Systems Limited will continue on the same direction and provide the same packages with same quality.
There are also enhancement and improvement coming later this year.



Texas Instruments Deutschland GmbH, Haggertystr. 1, D-85356 Freising. Amtsgericht München HRB 40960. Geschäftsführer: Andreas Schwaiger. Vorsitzender des Aufsichtsrates: Dr. Klaus Weisel

-----Original Message-----
From: Lev Serebryakov [mailto:le...@se...]
Sent: Wednesday, March 21, 2018 3:36 PM
To: Ghannouchi, Youssef; 'GCC for MSP430 - http://mspgcc.sf.net'
Subject: [EXTERNAL] Re: [Mspgcc-users] New MSP430-GCC releases available

On 20.03.2018 17:45, Ghannouchi, Youssef via Mspgcc-users wrote:

 I, as OS package maintainer, hope, that Mitto Systems Limited will continue good tradition established by SOMNIUM Technologies to produce releases based on official release sources (and not some random
snapshots) which are easy to build on non-Linux systems, like FreeBSD :)

> Hello MSP430 GCC-enthusiasts,
> We are pleased to announce a new stand-alone & open source Production release (v5.1.2.0)  of MSP430 GCC available for download:
> http://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/MSPGCC/5_
> 01_02_00/index_FDS.html The MSP430-GCC 5.1.2.0 standalone package
> based on GCC compiler to 6.4.0 (msp430-gcc 6.4.0.032) which was the last package maintained by SOMNIUM Technologies.
>
> For future MSP430-GCC compiler releases, TI has partnered with Mitto Systems Limited<http://www.mittosystems.com/> to bring you a new and fully supported open source compiler.
> The first version maintained by Mitto Systems Limited is a BETA open source beta release (v6.0.0.900):
> http://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/MSPGCC/6_
> 00_00_900/index_FDS.html The MSP430-GCC 6.0.0.900 is based on GCC
> compiler to 7.3.0 (msp430-gcc 7.3.0.9).
> The production release of MSP430-GCC 7.3.0 is planned for end of May 2018.
>
> Please use TI e2e community<https://e2e.ti.com/> to submit your requests or feedbacks.
>
> Best regards,
> ________________________________
> Youssef Ghannouchi
> Product Manager - Texas Instruments Inc.
>
> Texas Instruments Deutschland GmbH, Haggertystr. 1, D-85356 Freising.
> Amtsgericht München HRB 40960. Geschäftsführer: Andreas Schwaiger.
> Vorsitzender des Aufsichtsrates: Dr. Klaus Weisel
> ----------------------------------------------------------------------
> -------- Check out the vibrant tech community on one of the world's
> most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Mspgcc-users mailing list
> Msp...@li...
> https://lists.sourceforge.net/lists/listinfo/mspgcc-users
>


--
// Black Lion AKA Lev Serebryakov

Re: [Mspgcc-users] New MSP430-GCC releases available

[Lev S. <le...@se...>]

On 20.03.2018 17:45, Ghannouchi, Youssef via Mspgcc-users wrote:

 I, as OS package maintainer, hope, that Mitto Systems Limited will
continue good tradition established by SOMNIUM Technologies to produce
releases based on official release sources (and not some random
snapshots) which are easy to build on non-Linux systems, like FreeBSD :)

> Hello MSP430 GCC-enthusiasts,
> We are pleased to announce a new stand-alone & open source Production release (v5.1.2.0)  of MSP430 GCC available for download:
> http://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/MSPGCC/5_01_02_00/index_FDS.html
> The MSP430-GCC 5.1.2.0 standalone package based on GCC compiler to 6.4.0 (msp430-gcc 6.4.0.032) which was the last package maintained by SOMNIUM Technologies.
> 
> For future MSP430-GCC compiler releases, TI has partnered with Mitto Systems Limited<http://www.mittosystems.com/> to bring you a new and fully supported open source compiler.
> The first version maintained by Mitto Systems Limited is a BETA open source beta release (v6.0.0.900):
> http://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/MSPGCC/6_00_00_900/index_FDS.html
> The MSP430-GCC 6.0.0.900 is based on GCC compiler to 7.3.0 (msp430-gcc 7.3.0.9).
> The production release of MSP430-GCC 7.3.0 is planned for end of May 2018.
> 
> Please use TI e2e community<https://e2e.ti.com/> to submit your requests or feedbacks.
> 
> Best regards,
> ________________________________
> Youssef Ghannouchi
> Product Manager - Texas Instruments Inc.
> 
> Texas Instruments Deutschland GmbH, Haggertystr. 1, D-85356 Freising. Amtsgericht München HRB 40960. Geschäftsführer: Andreas Schwaiger. Vorsitzender des Aufsichtsrates: Dr. Klaus Weisel
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Mspgcc-users mailing list
> Msp...@li...
> https://lists.sourceforge.net/lists/listinfo/mspgcc-users
> 


-- 
// Black Lion AKA Lev Serebryakov

[Mspgcc-users] New MSP430-GCC releases available

[Ghannouchi, Y. <y-g...@ti...>]

Hello MSP430 GCC-enthusiasts,
We are pleased to announce a new stand-alone & open source Production release (v5.1.2.0)  of MSP430 GCC available for download:
http://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/MSPGCC/5_01_02_00/index_FDS.html
The MSP430-GCC 5.1.2.0 standalone package based on GCC compiler to 6.4.0 (msp430-gcc 6.4.0.032) which was the last package maintained by SOMNIUM Technologies.

For future MSP430-GCC compiler releases, TI has partnered with Mitto Systems Limited<http://www.mittosystems.com/> to bring you a new and fully supported open source compiler.
The first version maintained by Mitto Systems Limited is a BETA open source beta release (v6.0.0.900):
http://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/MSPGCC/6_00_00_900/index_FDS.html
The MSP430-GCC 6.0.0.900 is based on GCC compiler to 7.3.0 (msp430-gcc 7.3.0.9).
The production release of MSP430-GCC 7.3.0 is planned for end of May 2018.

Please use TI e2e community<https://e2e.ti.com/> to submit your requests or feedbacks.

Best regards,
________________________________
Youssef Ghannouchi
Product Manager - Texas Instruments Inc.

Texas Instruments Deutschland GmbH, Haggertystr. 1, D-85356 Freising. Amtsgericht München HRB 40960. Geschäftsführer: Andreas Schwaiger. Vorsitzender des Aufsichtsrates: Dr. Klaus Weisel

Re: [Mspgcc-users] Mspgcc-users Digest, Vol 122, Issue 1

[Kees S. <ks...@gm...>]

I would say start the debug session and have it run until you need to
investigate things. You could even
use  'mspdebug' for that.

On Sat, Mar 17, 2018 at 1:11 PM, <msp...@li...
> wrote:

> Send Mspgcc-users mailing list submissions to
>         msp...@li...
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.sourceforge.net/lists/listinfo/mspgcc-users
> or, via email, send a message with subject or body 'help' to
>         msp...@li...
>
> You can reach the person managing the list at
>         msp...@li...
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Mspgcc-users digest..."
>
>
> Today's Topics:
>
>    1. How to connect to a running target using MSPDebug (archie)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 16 Mar 2018 08:30:19 -0700 (MST)
> From: archie <arc...@vt...>
> To: msp...@li...
> Subject: [Mspgcc-users] How to connect to a running target using
>         MSPDebug
> Message-ID: <152...@n5...>
> Content-Type: text/plain; charset=us-ascii
>
> Hello,
>
> I am currently using MSP430FR5994. I program and debug it using MSP430.dll
> v3.3.1.4. I am unable to connect a running device to mspdebug without
> causing a reset to the program.
>
> I want to connect  a running target to mspdebug without stopping it or
> resetting the device. Currently. I connect to my device using 'tilib'
> driver. I get the following status after which the device is reset:
> Using new (SLAC460L+) API
> MSP430_Initialize: /dev/ttyACM0
> Firmware version is 31001600
> MSP430_VCC: 3000 mV
> MSP430_OpenDevice
> MSP430_GetFoundDevice
> Device: MSP430FR5994 (id = 0x01e9)
> 3 breakpoints available
> MSP430_EEM_Init
> Chip ID data:
>   ver_id:         82a1
>   ver_sub_id:     0000
>   revision:       10
>   fab:            55
>   self:           5555
>   config:         10
>   fuses:          55
> warning: unknown chip
>
> Thank you.
>
>
>
>
>
> --
> Sent from: http://msp430-gcc-users.1086195.n5.nabble.com/
>
>
>
> ------------------------------
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Mspgcc-users mailing list
> Msp...@li...
> https://lists.sourceforge.net/lists/listinfo/mspgcc-users
>
>
> ------------------------------
>
> End of Mspgcc-users Digest, Vol 122, Issue 1
> ********************************************
>

[Mspgcc-users] How to connect to a running target using MSPDebug

[archie <arc...@vt...>]

Hello,

I am currently using MSP430FR5994. I program and debug it using MSP430.dll
v3.3.1.4. I am unable to connect a running device to mspdebug without
causing a reset to the program.

I want to connect  a running target to mspdebug without stopping it or
resetting the device. Currently. I connect to my device using 'tilib'
driver. I get the following status after which the device is reset:
Using new (SLAC460L+) API
MSP430_Initialize: /dev/ttyACM0
Firmware version is 31001600
MSP430_VCC: 3000 mV
MSP430_OpenDevice
MSP430_GetFoundDevice
Device: MSP430FR5994 (id = 0x01e9)
3 breakpoints available
MSP430_EEM_Init
Chip ID data:
  ver_id:         82a1
  ver_sub_id:     0000
  revision:       10
  fab:            55
  self:           5555
  config:         10
  fuses:          55
warning: unknown chip

Thank you.





--
Sent from: http://msp430-gcc-users.1086195.n5.nabble.com/

Re: [Mspgcc-users] Problem with new MSP-FET

[Marko C. <mar...@mo...>]

Hello,

Still working on this, no success so far.

Opened the box, and found the following:

A big MSP430F6638 (with onboard USB)
An Actel Proasic3 nano  A3PN125 non-volatile FPGA
A small (14 pin) MSP430G2452
Etc...

This is quite different from what the old FETs are described to contain, so
I guess searching for old versiona of slac460 makes no sense. I will have to
compile the "w" version. Trying to do this, after a small change in one
file, I can get through the compiling steps, but linking fails, as the
specified (and included in slac460) version of hidapi does not produce the
hid-libusb.o required by the final linking step...
 
BTW, did anybody succeed in getting the new "black" FET to work with
mspdebug?

Marko Cebokli


-----Original Message-----
From: Rich Osman [mailto:li...@ri...] 
Sent: 28 November, 2017 9:03 PM
To: msp...@li...
Subject: Re: [Mspgcc-users] Problem with new MSP-FET

On 11/27/2017 11:41 AM, Daniel Beer wrote:
> On Mon, Nov 27, 2017 at 09:57:54AM +0100, Marko Cebokli wrote:
>> FET firmware update is required.
>> Starting firmware update (this may take some time)...
>> Initializing bootloader...
>> Initializing bootloader...
>> Initializing bootloader...
>> tilib: MSP430_FET_FwUpdate: MSP-FET430UIF Firmware erased - 
>> Bootloader active (error = 56)
>> tilib: device initialization failed
> Hi Marko,
>
> What happens if you try with -d /dev/ttyACM0 instead?
>
> Cheers,
> Daniel
>
I don't remember the details, but there are several versions of the FET
firmware for these depending on the client software (not just OS, but
GUI/CLI.) They are largely mutually exclusive.  I saw similar error messages
last year and had to solve it with a reflash of a different tool version. 
Worth a search.

--
mailto:li...@ri...  http://www.richosman.com Rich Osman;  POB 93167;
Southlake, TX 76092 (Near DFW Airport) ARS: N1OZ




----------------------------------------------------------------------------
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Mspgcc-users mailing list
Msp...@li...
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

Re: [Mspgcc-users] Mspgcc-users Digest, Vol 120, Issue 3

[Kees S. <ks...@gm...>]

Hi,

I don't have the latest MSP FET model (black) but the older grey
version MSP-FET430UIF.

I learned the hard way that it may pay-off to save the i2c eeprom
contents upfront too.
I used Ponyprog2000 with a simple LPT port adapter to access the I2C
bus to the eeprom.
Furthermore use mspdebug -bsl to save the current contents of the FET
firmware for later use. Verify that you got all, don't forget the info
memory.
Now I have 2 versions around, one with the V2 version and one with V3
that understands tilib.

best regards,

Kees


best rega

On 11/29/17, msp...@li...
<msp...@li...> wrote:
> Send Mspgcc-users mailing list submissions to
> 	msp...@li...
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://lists.sourceforge.net/lists/listinfo/mspgcc-users
> or, via email, send a message with subject or body 'help' to
> 	msp...@li...
>
> You can reach the person managing the list at
> 	msp...@li...
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Mspgcc-users digest..."
>
>
> Today's Topics:
>
>    1. Re: Problem with new MSP-FET (Rich Osman)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 28 Nov 2017 14:03:04 -0600
> From: Rich Osman <li...@ri...>
> To: msp...@li...
> Subject: Re: [Mspgcc-users] Problem with new MSP-FET
> Message-ID: <1ab...@ri...>
> Content-Type: text/plain; charset=utf-8
>
> On 11/27/2017 11:41 AM, Daniel Beer wrote:
>> On Mon, Nov 27, 2017 at 09:57:54AM +0100, Marko Cebokli wrote:
>>> FET firmware update is required.
>>> Starting firmware update (this may take some time)...
>>> Initializing bootloader...
>>> Initializing bootloader...
>>> Initializing bootloader...
>>> tilib: MSP430_FET_FwUpdate: MSP-FET430UIF Firmware erased - Bootloader
>>> active (error = 56)
>>> tilib: device initialization failed
>> Hi Marko,
>>
>> What happens if you try with -d /dev/ttyACM0 instead?
>>
>> Cheers,
>> Daniel
>>
> I don't remember the details, but there are several versions of the FET
> firmware for these depending on the client software (not just OS, but
> GUI/CLI.) They are largely mutually exclusive.? I saw similar error
> messages last year and had to solve it with a reflash of a different
> tool version.? Worth a search.
>
> --
> mailto:li...@ri...  http://www.richosman.com
> Rich Osman;  POB 93167; Southlake, TX 76092 (Near DFW Airport) ARS: N1OZ
>
>
>
>
>
>
> ------------------------------
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Mspgcc-users mailing list
> Msp...@li...
> https://lists.sourceforge.net/lists/listinfo/mspgcc-users
>
>
> ------------------------------
>
> End of Mspgcc-users Digest, Vol 120, Issue 3
> ********************************************
>

Re: [Mspgcc-users] Problem with new MSP-FET

[Rich O. <li...@ri...>]

On 11/27/2017 11:41 AM, Daniel Beer wrote:
> On Mon, Nov 27, 2017 at 09:57:54AM +0100, Marko Cebokli wrote:
>> FET firmware update is required.
>> Starting firmware update (this may take some time)...
>> Initializing bootloader...
>> Initializing bootloader...
>> Initializing bootloader...
>> tilib: MSP430_FET_FwUpdate: MSP-FET430UIF Firmware erased - Bootloader active (error = 56)
>> tilib: device initialization failed
> Hi Marko,
>
> What happens if you try with -d /dev/ttyACM0 instead?
>
> Cheers,
> Daniel
>
I don't remember the details, but there are several versions of the FET
firmware for these depending on the client software (not just OS, but
GUI/CLI.) They are largely mutually exclusive.  I saw similar error
messages last year and had to solve it with a reflash of a different
tool version.  Worth a search.

-- 
mailto:li...@ri...  http://www.richosman.com
Rich Osman;  POB 93167; Southlake, TX 76092 (Near DFW Airport) ARS: N1OZ

Re: [Mspgcc-users] Problem with new MSP-FET

[Daniel B. <dl...@gm...>]

On Mon, Nov 27, 2017 at 09:57:54AM +0100, Marko Cebokli wrote:
> FET firmware update is required.
> Starting firmware update (this may take some time)...
> Initializing bootloader...
> Initializing bootloader...
> Initializing bootloader...
> tilib: MSP430_FET_FwUpdate: MSP-FET430UIF Firmware erased - Bootloader active (error = 56)
> tilib: device initialization failed

Hi Marko,

What happens if you try with -d /dev/ttyACM0 instead?

Cheers,
Daniel

-- 
Daniel Beer <dl...@gm...> http://dlbeer.co.nz/
PGP: BA6E 0B26 1F89 246C E3F3  C910 1E58 C43A 160A 553B

[Mspgcc-users] Problem with new MSP-FET

[Marko C. <mar...@mo...>]

Hello,
I just bought a new MSP-FET (Farnell 2460068) and have problems getting it to work.
 
First I downloaded slac460w from the TI site, but it failed to compile, with
DLL430_v3/src/TI/DLL430/UpdateManagerFet.cpp:1279:9: error: ‘MSP_FetFpgaHalImage_sections’ was not declared in this scope

return MSP_FetFpgaHalImage_sections * 2;

Then I downloaded 

 <https://github.com/BuLogics/libMSP430> https://github.com/BuLogics/libMSP430

from which I could compile libmsp430.so.

Next, I downloaded and compiled last version (0.25) of mspdebug.. It works OK with my launchpad (rf2500), but I can't get it to work with then new MSP_FET (serial 170500372). What could be wrong? Below I pasted the output of dmesg, lsusb and some mspdebug commands. (sorry for the big line spacing, but I am sendidng this from a windows machine which has problems with linux .txt files)

Marko Cebokli

 

[ 304.288053] usb 1-6: new full-speed USB device number 3 using xhci_hcd

[ 304.419077] usb 1-6: New USB device found, idVendor=2047, idProduct=0014

[ 304.419080] usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[ 304.419081] usb 1-6: Product: MSP Tools Driver

[ 304.419082] usb 1-6: Manufacturer: Texas Instruments

[ 304.419083] usb 1-6: SerialNumber: ACF713470B001700

[ 304.469789] cdc_acm 1-6:1.0: ttyACM0: USB ACM device

[ 304.469988] cdc_acm 1-6:1.2: ttyACM1: USB ACM device

[ 304.470145] usbcore: registered new interface driver cdc_acm

[ 304.470146] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters

mc@gvdpc7:~/Downloads/mspdebug-0.25> 

mc@gvdpc7:~/Downloads/mspdebug-0.25> 

mc@gvdpc7:~/Downloads/mspdebug-0.25> 

mc@gvdpc7:~/Downloads/mspdebug-0.25> 

mc@gvdpc7:~/Downloads/mspdebug-0.25> lsusb

Bus 003 Device 004: ID 0a5c:216c Broadcom Corp. 

Bus 003 Device 003: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd (Foxlink) 

Bus 003 Device 002: ID 8087:8000 Intel Corp. 

Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Bus 001 Device 003: ID 2047:0014 Texas Instruments 

Bus 001 Device 002: ID 0458:003a KYE Systems Corp. (Mouse Systems) NetScroll+ Mini Traveler / Genius NetScroll 120

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

mc@gvdpc7:~/Downloads/mspdebug-0.25> 

mc@gvdpc7:~/Downloads/mspdebug-0.25> 

mc@gvdpc7:~/Downloads/mspdebug-0.25> mspdebug --usb-list

Devices on bus 003:

003:004 0a5c:216c 

003:003 05c8:036e 

003:002 8087:8000 

003:001 1d6b:0002 

Devices on bus 002:

002:001 1d6b:0003 

Devices on bus 001:

001:003 2047:0014 

001:002 0458:003a 

001:001 1d6b:0002 

mc@gvdpc7:~/Downloads/mspdebug-0.25>

mc@gvdpc7:~/Downloads/mspdebug-0.25> sudo ./mspdebug tilib

[sudo] password for root: 

MSPDebug version 0.25 - debugging tool for MSP430 MCUs

Copyright (C) 2009-2017 Daniel Beer <dl...@gm...>

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.

Using old API

MSP430_GetNumberOfUsbIfs

No unused FET found.

mc@gvdpc7:~/Downloads/mspdebug-0.25> 

mc@gvdpc7:~/Downloads/mspdebug-0.25> ./mspdebug tilib -U 001:003

MSPDebug version 0.25 - debugging tool for MSP430 MCUs

Copyright (C) 2009-2017 Daniel Beer <dl...@gm...>

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.

Using old API

MSP430_GetNumberOfUsbIfs

No unused FET found.

mc@gvdpc7:~/Downloads/mspdebug-0.25> 

mc@gvdpc7:~/Downloads/mspdebug-0.25> sudo ./mspdebug tilib -d /dev/ttyACM1

MSPDebug version 0.25 - debugging tool for MSP430 MCUs

Copyright (C) 2009-2017 Daniel Beer <dl...@gm...>

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.

Using old API

MSP430_Initialize: /dev/ttyACM1

FET firmware update is required.

Re-run with --allow-fw-update to perform a firmware update.

tilib: device initialization failed

mc@gvdpc7:~/Downloads/mspdebug-0.25> 

mc@gvdpc7:~/Downloads/mspdebug-0.25> 

mc@gvdpc7:~/Downloads/mspdebug-0.25> 

mc@gvdpc7:~/Downloads/mspdebug-0.25> sudo ./mspdebug tilib -d /dev/ttyACM1 --allow-fw-update

MSPDebug version 0.25 - debugging tool for MSP430 MCUs

Copyright (C) 2009-2017 Daniel Beer <dl...@gm...>

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.

Using old API

MSP430_Initialize: /dev/ttyACM1

FET firmware update is required.

Starting firmware update (this may take some time)...

Initializing bootloader...

Initializing bootloader...

Initializing bootloader...

tilib: MSP430_FET_FwUpdate: MSP-FET430UIF Firmware erased - Bootloader active (error = 56)

tilib: device initialization failed

mc@gvdpc7:~/Downloads/mspdebug-0.25> 

 

Re: [Mspgcc-users] msp430x1612 header

[Peter B. <pa...@pa...>]

The x variants were an early attempt to simplify identifying processors
where part number variation did not affect the compiler, at a time when
the MSP430 product line was quite limited.  Introduction of additional
processor families broke those assumptions, particularly in the need to
vary the addresses and presence of different peripherals.

In 2013 when I last updated msp430mcu (may not have been released) there
were north of 450 distinct chip IDs that affected code generation or
peripheral address.  The generic ID originally spelled msp430x16x
covered six of them.

Peter


On Thu, Mar 30, 2017 at 8:11 PM, Norrathep Rattanavipanon <nra...@uc...>
wrote:

> Thanks I just found out that I need to include periph.x. Just curious is
> there any difference for x1612 vs f1612 in terms of hardware configuration?
> Or is x1612 just renamed to f1612?
>
> On Thu, Mar 30, 2017 at 4:51 PM, David W. Schultz <
> dav...@ea...> wrote:
>
> > On 03/30/2017 06:38 PM, Norrathep Rattanavipanon wrote:
> > > Thank you so much for your help, David. Now it compiles perfectly past
> > > that point but I run into another issue (I'm not sure if this is the
> > > right place to post please let me know if its not):
> > >
> > > /usr/lib/gcc/msp430/4.6.3/../../../../msp430/bin/ld: cannot represent
> > > machine `msp:110'
> > >
> >
> > There should be a linker script available as well in the same location.
> > If you have given the compiler the path to that directory it should find
> > it.
> >
> > -I /usr/ti/gcc/include
> >
> > Is what I use.
> >
> > TI moved a lot of information, like device register addresses, from the
> > .h files into the linker scripts some time ago. You should use the
> > provided linker scripts and they will resolve symbols like WDTCTL.
> >
> > --
> > David W. Schultz
> > http://home.earthlink.net/~david.schultz
> > "Life without stock is barely worth living..." - Anthony Bourdain
> >
> > ------------------------------------------------------------
> > ------------------
> > Check out the vibrant tech community on one of the world's most
> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> > _______________________________________________
> > Mspgcc-users mailing list
> > Msp...@li...
> > https://lists.sourceforge.net/lists/listinfo/mspgcc-users
> >
>
>
>
> --
> Norrathep (Oak) Rattanavipanon
> M.S. in Computer Science
> University of California - Irvine
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Mspgcc-users mailing list
> Msp...@li...
> https://lists.sourceforge.net/lists/listinfo/mspgcc-users
>
>

Re: [Mspgcc-users] msp430x1612 header

[Norrathep R. <nra...@uc...>]

Thanks I just found out that I need to include periph.x. Just curious is
there any difference for x1612 vs f1612 in terms of hardware configuration?
Or is x1612 just renamed to f1612?

On Thu, Mar 30, 2017 at 4:51 PM, David W. Schultz <
dav...@ea...> wrote:

> On 03/30/2017 06:38 PM, Norrathep Rattanavipanon wrote:
> > Thank you so much for your help, David. Now it compiles perfectly past
> > that point but I run into another issue (I'm not sure if this is the
> > right place to post please let me know if its not):
> >
> > /usr/lib/gcc/msp430/4.6.3/../../../../msp430/bin/ld: cannot represent
> > machine `msp:110'
> >
>
> There should be a linker script available as well in the same location.
> If you have given the compiler the path to that directory it should find
> it.
>
> -I /usr/ti/gcc/include
>
> Is what I use.
>
> TI moved a lot of information, like device register addresses, from the
> .h files into the linker scripts some time ago. You should use the
> provided linker scripts and they will resolve symbols like WDTCTL.
>
> --
> David W. Schultz
> http://home.earthlink.net/~david.schultz
> "Life without stock is barely worth living..." - Anthony Bourdain
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Mspgcc-users mailing list
> Msp...@li...
> https://lists.sourceforge.net/lists/listinfo/mspgcc-users
>



-- 
Norrathep (Oak) Rattanavipanon
M.S. in Computer Science
University of California - Irvine

Re: [Mspgcc-users] msp430x1612 header

[David W. S. <dav...@ea...>]

On 03/30/2017 06:38 PM, Norrathep Rattanavipanon wrote:
> Thank you so much for your help, David. Now it compiles perfectly past
> that point but I run into another issue (I'm not sure if this is the
> right place to post please let me know if its not): 
> 
> /usr/lib/gcc/msp430/4.6.3/../../../../msp430/bin/ld: cannot represent
> machine `msp:110'
> 

There should be a linker script available as well in the same location.
If you have given the compiler the path to that directory it should find it.

-I /usr/ti/gcc/include

Is what I use.

TI moved a lot of information, like device register addresses, from the
.h files into the linker scripts some time ago. You should use the
provided linker scripts and they will resolve symbols like WDTCTL.

-- 
David W. Schultz
http://home.earthlink.net/~david.schultz
"Life without stock is barely worth living..." - Anthony Bourdain

Re: [Mspgcc-users] msp430x1612 header

[Norrathep R. <nra...@uc...>]

Thank you so much for your help, David. Now it compiles perfectly past that
point but I run into another issue (I'm not sure if this is the right place
to post please let me know if its not):

/usr/lib/gcc/msp430/4.6.3/../../../../msp430/bin/ld: cannot represent
machine `msp:110'

I put the following in the linker script - link-MSP430x:

OUTPUT_FORMAT("elf32-msp430","elf32-msp430","elf32-msp430")
OUTPUT_ARCH(msp:110)
,,,

And it compiles using the following command: msp430-gcc -T link-MSP430.x
.... -mmcu=msp430f1612 ...

Then, I tried changing OUTPUT_ARCH(msp:110) to OUTPUT_ARCH(msp430). But I
get a lot of undefined references:

/usr/lib/gcc/msp430/4.6.3/mmpy-16/libcrt0.a(__watchdog_support.o): In
function `__watchdog_support':
/build/buildd/gcc-msp430-4.6.3~mspgcc-20120406/./gcc-4.6.3/gcc/config/msp430/crt0.S:105:
undefined reference to `__WDTCTL'
/usr/lib/gcc/msp430/4.6.3/mmpy-16/libcrt0.a(_copy_data.o): In function
`__do_copy_data':
/build/buildd/gcc-msp430-4.6.3~mspgcc-20120406/./gcc-4.6.3/gcc/config/msp430/crt0.S:193:
undefined reference to `__WDTCTL'
/usr/lib/gcc/msp430/4.6.3/mmpy-16/libcrt0.a(_clear_bss.o): In function
`__do_clear_bss':
/build/buildd/gcc-msp430-4.6.3~mspgcc-20120406/./gcc-4.6.3/gcc/config/msp430/crt0.S:219:
undefined reference to `__WDTCTL'

Thank you for your help.




On Thu, Mar 30, 2017 at 3:03 PM, David W. Schultz <
dav...@ea...> wrote:

> On 03/30/2017 04:43 PM, Norrathep Rattanavipanon wrote:
> > Hello,
> >
> > I have an old code that compiles with " msp430-gcc -mmcu=msp430x1612
> ...".
> > However, I'm very new and dont have any prior experience in msp430 so I
> > tried to compile it but it said "warning unable to identify and include
> MCU
> > header". So I looked into msp430.h and it does not have any
> msp430x1612.h.
> > Is there anyway to run this code with the latest version of mspgcc?
>
> Identify a specific part: -mmcu=msp430f1612
>
> --
> David W. Schultz
> http://home.earthlink.net/~david.schultz
> "Life without stock is barely worth living..." - Anthony Bourdain
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Mspgcc-users mailing list
> Msp...@li...
> https://lists.sourceforge.net/lists/listinfo/mspgcc-users
>



-- 
Norrathep (Oak) Rattanavipanon
M.S. in Computer Science
University of California - Irvine

Re: [Mspgcc-users] msp430x1612 header

[David W. S. <dav...@ea...>]

On 03/30/2017 04:43 PM, Norrathep Rattanavipanon wrote:
> Hello,
> 
> I have an old code that compiles with " msp430-gcc -mmcu=msp430x1612 ...".
> However, I'm very new and dont have any prior experience in msp430 so I
> tried to compile it but it said "warning unable to identify and include MCU
> header". So I looked into msp430.h and it does not have any msp430x1612.h.
> Is there anyway to run this code with the latest version of mspgcc?

Identify a specific part: -mmcu=msp430f1612

-- 
David W. Schultz
http://home.earthlink.net/~david.schultz
"Life without stock is barely worth living..." - Anthony Bourdain

[Mspgcc-users] msp430x1612 header

[Norrathep R. <nra...@uc...>]

Hello,

I have an old code that compiles with " msp430-gcc -mmcu=msp430x1612 ...".
However, I'm very new and dont have any prior experience in msp430 so I
tried to compile it but it said "warning unable to identify and include MCU
header". So I looked into msp430.h and it does not have any msp430x1612.h.
Is there anyway to run this code with the latest version of mspgcc?

I also notice that msp430.h mentioned "Generic names, such as msp430x1611,
are recognized only if they are sufficient to uniquely identify a device."
but I'm not really sure what it means nor what I have to do to fix this.
I'd appreciate any help.

Thanks,

Oak


-- 
Norrathep (Oak) Rattanavipanon
M.S. in Computer Science
University of California - Irvine