Mostly for my own reference for the next time I have to set it up on a new machine, but may help others on their first time install. Valid as of Feb. or so this year.<\/p>\n
Software ‘shopping’ list<\/b> (all free\/OSS tools) mspgcc-win32: MinGW\/msys (provides ‘make’ and some utilities) : CoreUtils (provides unix-like ‘rm’ tool required by make) : Skipping the debugger for now until I figure out how to use it myself ;-) Seems to work occasionally under win32, but it’s flaky.<\/p>\n Required Knowledge<\/b> Assuming you already know C and have the appropriate chip documentation\/datasheets. The manual contains a lot of advanced stuff you can skip at first, or Get familiar with ‘make’. Outside of kinky application-specific tools How make works is you specify one or more ‘targets’, i.e. things make Since the top half of the ez430 kit is essentially the USB Sy-Bi-Wire programmer, you have to change the download command to:<\/p>\n msp430-jtag –spy-bi-wire -lpt=USBFET -e leds.elf<\/p>\n I.e. in the Makefile you’d find and change the download section to:<\/p>\n download-jtag: all As long as you have the Makefile open, now is a good time to find the Now when you #include the base generic Mostly for my own reference for the next time I have to set it up on a new machine, but may help others on their first time install. Valid as of Feb. or so this year. Software ‘shopping’ list (all free\/OSS tools) Set up the toolchain (mspgcc). There seem to be several important tools missing […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_FSMCFIC_featured_image_caption":"","_FSMCFIC_featured_image_nocaption":"","_FSMCFIC_featured_image_hide":"","iawp_total_views":9,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-674","post","type-post","status-publish","format-standard","hentry","category-general"],"_links":{"self":[{"href":"https:\/\/tim.cexx.org\/index.php?rest_route=\/wp\/v2\/posts\/674","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tim.cexx.org\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/tim.cexx.org\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/tim.cexx.org\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/tim.cexx.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=674"}],"version-history":[{"count":4,"href":"https:\/\/tim.cexx.org\/index.php?rest_route=\/wp\/v2\/posts\/674\/revisions"}],"predecessor-version":[{"id":678,"href":"https:\/\/tim.cexx.org\/index.php?rest_route=\/wp\/v2\/posts\/674\/revisions\/678"}],"wp:attachment":[{"href":"https:\/\/tim.cexx.org\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=674"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/tim.cexx.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=674"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/tim.cexx.org\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=674"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\nSet up the toolchain (mspgcc)<\/a>. There seem to be several important tools
\nmissing from the mspgcc distro as of this writing, including ‘make’ and
\nmsp430-insight (graphical debugger) that the docs claim are included
\nwith the package. So the complete shopping list is:<\/p>\n
\nhttp:\/\/downloads.sourceforge.net\/mspgcc\/mspgcc-20081230.exe?use_mirror=voxel<\/a>
\nNOTE: This binary IIRC was not linked on Sourceforge’s downloads page at the time; there was only an older build and this link had to be fished from semi-private newsgroup postings. If there is a newer binary available, download that one.<\/p>\n
\nhttp:\/\/downloads.sourceforge.net\/mingw\/MinGW-5.1.4.exe?use_mirror=voxel<\/a>
\nIf it gives you the options of installing minGW and msys, say YES to both.<\/p>\n
\nhttp:\/\/gnuwin32.sourceforge.net\/packages\/coreutils.htm<\/a><\/p>\n
\nHave a quick read-through of the mspgcc FAQ and manual. Both are
\nreasonably short for what they are.
\nFAQ: http:\/\/mspgcc.sourceforge.net\/faq\/t2.html<\/a>
\nManual: http:\/\/mspgcc.sourceforge.net\/manual\/<\/a><\/p>\n
\nskip entirely. This includes (at minimum) the stuff about customizing
\nthe startup\/end procedures, stack, the entire ABI section, inline
\nassembly, and stuff about building mspgcc (the package you get is
\nalready built).<\/p>\n
\nlike the Microchip assembler\/compiler and ‘IAR Kickstart’, the rest of
\nthe free world uses make<\/i> to automate compiling, linking,
\ninstalling\/running and packaging their code. Go into the mspgcc
\n‘examples’ folder and find the blinking LEDs example (e.g.
\nE:\\mspgcc\\examples\\leds). Open up the file called Makefile in Wordpad
\nand have a look inside. This is the master script that will smartly
\nhandle all your compiling, programming the chip, and avoid you rewriting
\nlots of code whenever you change chips. The contents will probably look
\nlike gibberish, there are only a few parts that are important for our
\npurposes. The make tool installed by mingw32 is named ‘mingw32-make’.<\/p>\n
\ncan do. Running make with no target specified compiles your program.
\nSome other targets are ‘mingw32-make clean’ (delete your old build and
\nany scratch files), or ‘mingw32-make download’ (compiles your program,
\ndownloads it to the chip and runs it). All the necessary commands to
\nhandle each target are in the Makefile.<\/p>\n
\n msp430-jtag –spy-bi-wire -lpt=USBFET -e ${NAME}.elf<\/p>\n
\nCPU= line and change it to match the msp430 variant you are actually
\nusing. In the case of the eZ430 board:
\nCPU = msp430x2274<\/p>\n
\nmspgcc project, it will automatically switch in the correct headers and
\nperipheral support for that specific CPU.
\n<\/io><\/p>\n","protected":false},"excerpt":{"rendered":"