You are not logged in.
Pages: 1
I've just found out that as part of my thesis research, I'm going to have to program an MCU-- specifically the TI MSP430. We'll be using the Experimenter's kit for the chip (http://focus.ti.com/docs/toolsw/folders … f5438.html).
Does anyone have some experience with this kind of hardware in Arch? I'd rather not have to work in a windows environment if I don't have to (as it would require me to actually get it...).
Offline
Hopeful bump to get a new batch of eyes to see the thread...
Is there anyone that does MCU programming at all, not necessarily this chip? I'm not certain what I need to do to make my system ready to work with this kind of task.
Offline
Ok, here's what I've been able to do so far:
install from AUR:
gcc-msp430
binutils-msp430
msp430-gdb **with some modifications to the PKGBUILD, as per comment posted on AUR page.
msp430-libc
In order to get the FET430UIF to be recognized, do:
modprobe ti_usb_3410_5052 product_3410=0xf430 vendor_3410=0x0451as per instructions found at this site. I don't know if the product/vendor specifications are necessary or not. Obviously this should be put into rc.conf if I don't want to load the module by hand every time, but how do you add the arguments (assuming they're necessary) to load the module on boot?
Once the module is loaded, the FET is recognized by the computer, but I am unable to test because the package msp430-jtag build fails (see comment posted on AUR page).
I believe the package is necessary, because it appears to install the needed software to use gdbproxy, which gives the instructions necessary for gdb to communicate with the FET. Any ideas how to fix it?
Offline
This project looks very promising, and is in AUR-- but it doesn't look like it works completely yet. It also sounds as though TI is working on their own open source solution to this issue. Good news for the future!
Last edited by beretta (2009-11-02 22:40:56)
Offline
Hi beretta, I've fixed the gdb package and posted something on the jtag AUR page. Please have a look.
Offline
Thanks, stuffcorpse. I'm glad you've done the work to get these things available. Hopefully I can get it working now. I'm kind of surprised to find not many people in the Arch community are doing these things-- but I'm having a great time learning it myself.
What do you know about this fetproxy project? Any ideas when it'll be useable, or the hints they gave that TI may release their own open source version this year?
It seems like the only barrier I have now is gdbproxy-- I'll post up here what I did if I can manage to get it to work right.
Offline
Thanks, stuffcorpse. I'm glad you've done the work to get these things available. Hopefully I can get it working now. I'm kind of surprised to find not many people in the Arch community are doing these things-- but I'm having a great time learning it myself.
What do you know about this fetproxy project? Any ideas when it'll be useable, or the hints they gave that TI may release their own open source version this year?
It seems like the only barrier I have now is gdbproxy-- I'll post up here what I did if I can manage to get it to work right.
You're welcome ![]()
There were others maintaining the AUR package (previously there was only one - everything together). I came and adopted it since it was orphaned. There had been some mailing list discussions about embedded things in Arch in the past few months I think. AVR/ARM are still more popular I guess.
I don't much about fetproxy other than it is still in development. I was kind of excited when it was announced, and hence I created the AUR package for fetching from its git repo. But it turned out dev is very slow and doesn't really work (yet) so hopefully there will be more people involved in it later.
Offline
I don't know what changed-- but it installed cleanly as set up this time around. I wonder what I was doing that kept it from building before?? Maybe I just needed to reboot first.
I should be able to test out the chips at this point, anyway.
Steps completed so far:
yaourt -S gcc-msp430 binutils-msp430 msp430-libc msp430-gdb msp430-jtag
wget http://www.soft-switch.org/downloads/mspgcc/msp430-gdbproxy
wget http://www.soft-switch.org/downloads/mspgcc/libMSP430.so
mv msp430-gdbproxy /usr/bin
mv libMSP430.so /usr/lib
modprobe ti_usb_3410_5052 product_3410=0xf430 vendor_3410=0x0451Last edited by beretta (2009-11-03 14:06:43)
Offline
I don't know what changed-- but it installed cleanly as set up this time around. I wonder what I was doing that kept it from building before?? Maybe I just needed to reboot first.
I should be able to test out the chips at this point, anyway.
Cool. Let me know how it goes, thanks.
Offline
I needed to download one other file before using my parallel port JTAG
wget http://www.soft-switch.org/downloads/mspgcc/libHIL.so
sudo mv libHIL.so /usr/libOffline
I needed to download one other file before using my parallel port JTAG
wget http://www.soft-switch.org/downloads/mspgcc/libHIL.so sudo mv libHIL.so /usr/lib
That file is provided by the msp430-jtag package.
Offline
Hi beretta, I've fixed the gdb package and posted something on the jtag AUR page. Please have a look.
Hi.
I'm trying to compile gcc-msp430 with
yaourt -S gcc-msp430
binutils are comiled successfully but while compiling gcc-msp430 I've got:
/usr/bin/msp430-as: unrecognized option '--64'
make[2]: *** [build/genconstants.o] Error 2
make[2]: Leaving directory `/tmp/yaourt-tmp-i/aur-gcc-msp430/src/build/gcc'
make[1]: *** [all-gcc] Error 2
make[1]: Leaving directory `/tmp/yaourt-tmp-i/aur-gcc-msp430/src/build'
make: *** [all] Error 2
Can you advise something?
Thanks.
Offline
Pages: 1