jazz 209 Posted October 25, 2013 Share Posted October 25, 2013 Looks like port mapping on the 5529 is only available on P4. :-( Yes, and P4.0, P4.1, P4.2 and P4.3 connection is present on board. Quote Link to post Share on other sites
pabigot 355 Posted October 25, 2013 Share Posted October 25, 2013 Yes, and P4.0, P4.1, P4.2 and P4.3 connection is present on board. P4.0 (D8), P4.1 (A9), P4.2 (A10), and P4.3 (D7) can be remapped, but I need SPI on B8 (P2.6) and A8 (P2.7) for the SENSHUB. Port mapping is a nice feature, but it doesn't help me in this case. (It did give me access to MCLK so I can verify all core clocks are at the rate I've configured.) Quote Link to post Share on other sites
RobG 1,892 Posted October 26, 2013 Share Posted October 26, 2013 I think all outer pins on F based LaunchPads should be PM pins. Quote Link to post Share on other sites
amstan 18 Posted November 1, 2013 Share Posted November 1, 2013 P4.0 (D8), P4.1 (A9), P4.2 (A10), and P4.3 (D7) can be remapped, but I need SPI on B8 (P2.6) and A8 (P2.7) for the SENSHUB. Port mapping is a nice feature, but it doesn't help me in this case. (It did give me access to MCLK so I can verify all core clocks are at the rate I've configured.) Come on... this is SPI. It's trivial to implement in software: unsigned char spi_xfer(unsigned char send) { set_bit(SPIPORT,CS); unsigned char reply=0; for(char bit=7;bit>=0;bit--){ change_bit(SPIPORT,MOSI,test_bit(send,byte)); clear_bit(SPIPORT,CLK); change_bit(reply,bit,test_bit(SPIPORT,MISO)); set_bit(SPIPORT,CLK); } set_bit(SPIPORT,CS); return reply; } Quote Link to post Share on other sites
pabigot 355 Posted November 1, 2013 Share Posted November 1, 2013 Come on... this is SPI. It's trivial to implement in software: The CC3000 can operate with SPI clock rates up to 26 MHz, and sucks power like a 30 year old refrigerator. No, I'm not going to bitbang the thing at 100 kHz. Quote Link to post Share on other sites
nickn 5 Posted November 5, 2013 Share Posted November 5, 2013 How well does serial communication work for this board under Linux? I never successfully managed to get serial over USB working on my MSP430g2553 with my Raspberry Pi. Quote Link to post Share on other sites
amstan 18 Posted November 7, 2013 Share Posted November 7, 2013 How well does serial communication work for this board under Linux? I never successfully managed to get serial over USB working on my MSP430g2553 with my Raspberry Pi. It works pretty well, it's not locked down like the original launchpad works. The firmware on it(the programmer chip) is open source too. Quote Link to post Share on other sites
Abhi 1 Posted November 25, 2013 Share Posted November 25, 2013 Hi guys, i just got my MSP430F5529 launchpad today.I installed the latest CCS studio v5.5 and when i plugged the board,it looked up for the drivers and the MSP debug interface drivers got installed successfully but not for the application UART.I even tried every single CDC driver from their latest MSP debug wiki page but the problem is not resolved.Do anybody know he solution for this and help me how to use this board with ENERGIA.Thanks. Quote Link to post Share on other sites
bluehash 1,581 Posted November 25, 2013 Share Posted November 25, 2013 Hi guys, i just got my MSP430F5529 launchpad today. I installed the latest CCS studio v5.5 and when i plugged the board,it looked up for the drivers and the MSP debug interface drivers got installed successfully but not for the application UART. I even tried every single CDC driver from their latest MSP debug wiki page but the problem is not resolved. Do anybody know he solution for this and help me how to use this board with ENERGIA. Thanks. Crosslink: http://forum.43oh.com/topic/2763-can-not-install-msp430-application-uart-driver/ Abhi 1 Quote Link to post Share on other sites
spirilis 1,265 Posted November 27, 2013 Share Posted November 27, 2013 Doing some development for RobG's Ethernet boosterpack (currently using the old one, but, he did send me a new one which I'll get to soon) ... I keep finding myself choosing the F5529 LP. Its serial interfaces aren't quirky with Linux like the original v1.5 LP, I know its 3.3V power source has grunt and it's got the two serial ports for interfacing with UART stuff while also reserving a backchannel UART (haven't used this particular feature yet but it's nice to know it's there). abecedarian 1 Quote Link to post Share on other sites
timb 15 Posted December 31, 2013 Share Posted December 31, 2013 Ordered mine a couple of weeks ago. The page said it would ship mid-December, but on the Order Status page it said January 20th! It shipped two days later. Reading over the thread, I noticed a lot of you guys got Rev 1.4 boards earlier in the year (September, October). My new board is Rev 1.5, so I wonder what they changed? Quote Link to post Share on other sites
Automate 69 Posted December 31, 2013 Share Posted December 31, 2013 Can you post a picture? Quote Link to post Share on other sites
abecedarian 330 Posted December 31, 2013 Share Posted December 31, 2013 My 1.4 has an H revision chip. Perhaps the 1.5 is using I revision? Quote Link to post Share on other sites
VaZso 3 Posted January 21, 2014 Share Posted January 21, 2014 I have put this board into its box for a while, but today I played a little bit and just set it up under Linux using msp-gcc. I had to recompile mspdebug (http://mspdebug.sourceforge.net/), compile boost (http://www.boost.org/), hidapi (https://github.com/signal11/hidapi/downloads) and tilib (http://processors.wiki.ti.com/index.php/MSPDS_Open_Source_Package) in order to work. In the latter, I had an error during compile, which had to be corrected by adding "#include <stdio.h>" include file to DLL430_v3/src/TI/DLL430/EnergyTrace_TSPA/EnergyTraceProcessorId7.h header. Now I can compile and upload programs using tilib with Eclipse. For USB BSL, ihex2titex.py (http://mspgcc.cvs.sourceforge.net/viewvc/mspgcc/python/) can be used to convert .elf to .txt, then python-msp430-tools (https://pypi.python.org/pypi/python-msp430-tools) to upload it to device. This also works well now. spirilis and bluehash 2 Quote Link to post Share on other sites
VaZso 3 Posted January 21, 2014 Share Posted January 21, 2014 I forgot to mention that Firmware Updater in USBDevelopersPackage (http://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/MSP430_USB_Developers_Package/4_00_02/index_FDS.html) or simply Python_Firmware_Upgrader also work after corrected slashes/backslashes in BSL path. So I modified the following line in TargetGUI.py file: full_bsl_txt = open(os.path.join(basedir, '.\\python-msp430-tools\\msp430\\bsl5\\RAM_BSL.00.07.87.37.txt'), 'rb').read() to this line: full_bsl_txt = open(os.path.join(basedir, './python-msp430-tools/msp430/bsl5/RAM_BSL.00.07.87.37.txt'), 'rb').read() Anyway, I'm currently don't know what are 5529_CDC_echo.txt and 5529_HID_echo.txt good for (what they exactly do), but 5529_LED_Blink.txt works well, so it does its job. Maybe it helps somebody. Edit: This modification only needed for Linux, because Windows uses backslash and Linux uses slash in directory structure. Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.