-
Content Count
1,135 -
Joined
-
Last visited
-
Days Won
71
Rickta59 last won the day on April 17 2019
Rickta59 had the most liked content!
About Rickta59
-
Rank
Level 4
Contact Methods
-
Website URL
http://fabooh.com
Profile Information
-
Gender
Not Telling
-
Location
Eastern NC
-
Interests
CNC, 3D Printing, Microcontrollers
-
Github
http://github.com/RickKimball/fabooh
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
@GarryJones @bluehash SPAM SPAM SPAM SPAM
-
Command line tools for MSP430F5529 launchpad under OsX
Rickta59 replied to AnttiST's topic in Compilers and IDEs
I'm not an OSX person so I'm not familiar with what people use for the msp430. However, this seems to be available for download to program your device: http://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/MSP430Flasher/latest/index_FDS.html -
Command line tools for MSP430F5529 launchpad under OsX
Rickta59 replied to AnttiST's topic in Compilers and IDEs
I did look at the CCS 9 zip download for OSX. It does contain a msp430-elf-gcc. You need to look harder for it. Install CCS and the msp430-elf-gcc and you will have all the command line tools you need. -
Command line tools for MSP430F5529 launchpad under OsX
Rickta59 replied to AnttiST's topic in Compilers and IDEs
Sometimes the MSP430-GCC-OPENSOURCE is not exactly the same revision. The msp430f5529 is old in terms of the compiler. It is probably fine for what you are doing. The mspdebug is the opensource programmer I use for msp430 chips. https://github.com/dlbeer/mspdebug For the msp430f5529 launchpad you can use: $ mspdebug tilib 'prog foo.out' CCS also provides a gdb proxy program. I've used it but I find mspdebug more convenient. I can run mspdebug on a raspberry pi, that is never going to happen with CCS. If you have installed dslite that will allow you to upload. Look at how ener -
Command line tools for MSP430F5529 launchpad under OsX
Rickta59 replied to AnttiST's topic in Compilers and IDEs
I used the msp430-elf-gcc that is installed in CCS. That makes it more convenient to get updates to both the compiler and the libmsp430.so that you can use with mspdebug tilib. It will save you from having to ping pong back and forth updating the firmware on your msp430f5529 launchpad if you switch between CCS and your VS code setup. I tried to use the gdb client built into VS code. On linux however there is a bug that prevents me from interrupting the execution to pause, so it was useless to me. I setup a makefile target called debug that launches mspdebug in one xterm and msp430-elf-g -
Aida DSP Boosterpack
Rickta59 replied to maxpenna's topic in Tiva-C, Hercules, CC3XXX Launchpad Booster Packs
@robertroth your spam is sneaky. @admin you seem to be targeted by spam bots -
sneaky spammer bots Eric Emily
-
You sound like a bot Shivkumar, are you?
-
This is the change in Oct of 2015 that broke it: https://github.com/energia/Energia/commit/3a79177338cab6e9724144038947db820a70e4b1#diff-ef6c05942e53197e6f1507545468bf55
-
I see that I mentioned it on this site: April 2016 I even created an issue for was closed but never addressed: https://github.com/energia/Energia/issues/874
-
It didn't, it has been broken for years and years. It stopped working when 1.6 was released.
-
So I spent some time with the latest energia 1.8.7E21. It is still using msp430-gcc. That project I linked in the previous post won't work because that code is using the newer msp430-elf-gcc. I did put together an example of using msp430-gcc style code and the blink project above that compiles and create asm only project .. well almost main has to jump to our asm code so there are a couple of instructions to get there. Three files are needed: blink_with_msp430-gcc_asm.ino /* blink_with_msp430-gcc_asm.ino */ /* * we aren't going to use the .ino file */ main.cpp // We overri
-
Interesting stuff. Here are some things that seem like they might cause you issues: Rewriting in C++ can be small. Using the Energia API will defeat that and not result in a 1k sd card bootloader. Cross Platform issues, Energia supports Windows, OS/X, and Linux. You need to supply the binaries for all the tools you are using that run on all platforms. It is easiest to stick with the gcc object tools for manipulating the .hex file. Naken asm source - No one has that so you either provide the naken assembler binary. Alternatively, if you want to just go with assembler + Ener
-
not json but instructions given for linux https://github.com/RickKimball/tivac-core Assumes you have openocd and arm-none-eabi-gcc in your path. Probably won't work for windows. Probably will work for OSX.