Search the Community

Showing results for tags 'mac'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • News
    • Announcements
    • Suggestions
    • New users say Hi!
  • Spotlight!
    • Sponsor Spotlight
    • Sponsor Giveaways
  • Energia
    • Energia - MSP
    • Energia - TivaC/CC3XXX
    • Energia - C2000
    • Energia Libraries
  • MSP Technical Forums
    • General
    • Compilers and IDEs
    • Development Kits
    • Programmers and Debuggers
    • Code vault
    • Projects
    • Booster Packs
    • Energia
  • Tiva-C, Hercules, CCXXXX ARM Technical Forums
    • General
    • SensorTag
    • Tiva-C, Hercules, CC3XXX Launchpad Booster Packs
    • Code Vault
    • Projects
    • Compilers and IDEs
    • Development Kits and Custom Boards
  • Beagle ARM Cortex A8 Technical Forums
    • General
    • Code Snippets and Scripts
    • Cases, Capes and Plugin Boards
    • Projects
  • General Electronics Forum
    • General Electronics
    • Other Microcontrollers
  • Connect
    • Embedded Systems/Test Equipment Deals
    • Buy, Trade and Sell
    • The 43oh Store
    • Community Projects
    • Fireside Chat
  • C2000 Technical Forums
    • General
    • Development Kits
    • Code Vault
    • Projects
    • BoosterPacks


There are no results to display.

Found 13 results

  1. Hi Everyone! I've just received a Tiva C launchpad and was wondering if you are able to write C code in Energia or if you have to use their Processing-based language? And if not, is there a way to use just write C code on Mac OS X (with or without an IDE) and upload it to the device? After a quick search of this forum and Google, most C compilers are meant for a Windows environment and I haven't been able to find much information for OS X other than Energia or possibly embedXCode. Thanks, Miles
  2. So, Indeed YELLOW_LED controls the red LED on the board. 8^) But I still can't get serial on my Mac to work reliably. I have set the baud to 115200 (Launchpad and Energia Terminal). I have tried Serial and Serial1. I have tried both usbmodems that show up, I do have USB 3.0, but I have no control over that. I have also tried the macOSX screen command which turns a terminal session into a serial console. The kicker is, one time I *did* get serial output to show up using this method. I was printing to Serial and Serial1 at the time. So I modified it to do one or the other but never again got any joy. One frustrating thing is that once I try something, I have to unplug and re-plug the USB to prevent "resource already in use" errors. Any thoughts?
  3. Hello. New here and having trouble getting my Mac Mini (10.12) to recognise the 3200 LauchpadXL. Other non-TI boards and FTDI adaptors show up fine in Arduino/Energia. Anybody got experience of why the port would not show? No obvious devices are showing in /dev Many thanks.
  4. Using a tm4c123gxl, on a mac (10.11.6) the online documentation says no drivers are required, but when I plug the board in, there is no recognition and no LEDs come on. I checked the mac ports and it also doesn't show there. Is there a driver that must be installed to start using my board?
  5. Oh I hope someone can help me out of this headache. I run the msp430g2452 from my MAC (Yosemite), Ran fine after installing drives and all. Now suddenly the "Serial Port" has gone grey and I try to re install, reboot, re everything. No way I can connect again. I was playing with digital out and also in. Seemed like it was when I was trying to read the switch on pin5 that things went bad for me. I know many have had problems on a mac and I have looked intense on this Forum and other on the net. Now I try this. I hope someone can help. Greetings from Brazil and thanks any help. Peter
  6. Energia's installation instructions for Mac specify a USB FTDI driver that apparently hasn't been updated since OS 10.7. Has anyone verified that it works on Mavericks and/or Yosemite? I believe that Yosemite in particular now requires "kext signing" of drivers, which has apparently caused a lot of problems for third-party software.
  7. Hi all, I've been lurking for a while but I finally joined up! I recently received the MSP430FR5969 FRAM Launchpad with EnergyTrace, and I'm trying to upload code to it with OS X 10.9.4 and mspdebug. I am successfully able to upload code to the standard Launchpad with the MSP430G2553 but I cannot upload to the FRAM Launchpad. Looking at this makes me think that a work around has not been found yet, is this true? Or has someone gotten the new FRAM Launchpads working with OS X? Thanks in advance for any help!
  8. I have been trying to learn how to program the Tiva/Stellaris using a Mac. Got Energia working-- version 0101E0010 has a bug where lm4flash doesn't work and needs to be replaced with a working version. Figuring out slowly how to use the Tiva driverlib. What was missing was debug capabilities. I wanted to share what I have learned so far and also solicit help from people who know more. I installed openocd from macport. ti-icdi support is available on 0.7.0 but the build options need to be changed. This is somewhat of a kludge but it worked OK. Basically ad a ti-icdi variant to opened and then build it. cd `port dir openocd` #then append the following to the Portfile variant ti description {TI-ICDI interface on Stellaris Launchpad} { configure.args-append --enable-ti-icdi depends_lib-append port:libusb } #now install ti-icdi variant sudo port install openocd +ti Make a copy of the cfg file from /opt/local/share/openocd/scripts/board/ek-lm4f120xl.cfg to the directory you want to work in. I changed 'set CHIPNAME lm4f120h5qr' to 'set CHIPNAME lm4f230h5qr'. I don't know if it actually changes anything but why not. Start openocd openocd ek-lm4f120xl.cfg Open another terminal window and start gdb. You can find the arm gdb in the bundle so you don't have to build it yourself-- I added /Applications/ to my $PATH so that I could invoke gdb from anywhere. One quirk of gdb: if you start gdb with a symbol file , you can't connect to the Stellaris. If you don't specify the symbol file, you can connect, but you can't do much because the symbols aren't loaded. To overcome this problem, load the symbol file AFTER connecting to the Stellaris. So, write your program in Energia, compile and upload it. Go to the Compilation folder (Sketch->Show Compilation Folder). Go to this directory in a terminal window. Look for the .elf file (should be program.cpp.elf). Start gdb: arm-none-eabi-gdbtui Connect to the remote target: target extended :3333 Load the symbol file: file progName.cpp.elf You might need to reset the board to make openocd happy. You should see the source code in the top of the window. You can run, cont, stop the program. I am still trying to figure out the other parts of gdb right now. Update: macports has added the ti variant to add icdi support. No need to edit the Portfile. You can now 'port install openocd +ti' after doing a 'port selfupdate'.
  9. I'm currently working on cross platform build tool named PlatformIO. It has pre-built MSP430 GCC toolchain & mspdebug for Mac, Linux 32/64 & Windows OS. 1. How often do you use external standalone toolchain to build your code? In which case? 2. What is your favourite IDE+Toolchain? 3. What would you like to have in paltformio tool? Thanks a lot for answers! P.S: The main idea of this tool is to compile code with different platforms. See Wiring Framework (Arduino + Energia) Blink Example.
  10. I recently installed openOCD on my computer and was able to get command line debugging working. Reading the gdb tutorials, I started doubting whether this was something I wanted to learn and wanted to see if I could get a GUI debugger working instead. I started fiddling around with Eclipse on my Mac and wanted to get a complete Tiva IDE. I followed a great tutorial for installing Stellarisware on Linux at Perhaps because of the changes from Stellarisware to Tivaware and/or Linux to Mac, there were many things that needed to be tweaked, adjusted, and fiddled with. But in the end, everything works! First, off, I have in /Applications. I installed openOCD using macports and installed Eclipse IDE for C/C++ Developers. Make sure gdb and openOCD are working properly before trying to get it to work in eclipse. I will describe here the changes from the tutorial above-- do all the other steps in the tutorial above. I copied the TivaWare files extracted on a Windows machine (because TI distributes this as an EXE file!) to ~/Projects/TivaWare_C_Series-1.1 (you can choose elsewhere but will need to change paths accordingly). I also created a folder for openOCD in ~/Projects/openocdDir containing the file ek-lm4f230xl.cfg which contains # # TI Stellaris Launchpad ek-lm4f120xl Evaluation Kits # # # # # NOTE: using the bundled ICDI interface is optional! # This interface is not ftdi based as previous boards were # source [find interface/ti-icdi.cfg] set WORKAREASIZE 0x8000 #set CHIPNAME lm4f120h5qr set CHIPNAME lm4f230h5qr source [find target/stellaris_icdi.cfg] Step 6: in Cross Settings, change Prefix to arm-none-eabi- and set Path to /Applications/ Step 7: Same except define PART_TM4C123GH6PM instead of PART_LM4F120H5QR. I don't know if this makes a difference but be consistent. Step 8: set include path to /Users/pjkim/Projects/TivaWare_C_Series-1.1 Step 9: Misc section. Set other flags to "-c -fmessage-length=0 -mthumb -mcpu=cortex-m4 -mfpu=fpv4-sp-d16 -mfloat-abi=softfp -ffunction-sections -fdata-sections -MD -std=c99 -Wall -pedantic" Step 9.5: Change Cross Gcc Linker to ld. I think it defaulted to gcc for some reason. Step 10: Linker Libraries. Leave Libraries blank. Change search path to /Applications/ Step 11: Linker Misc. Change linker flags to "--gc-sections -T../LM4F.ld" Once everything is done, check your flags. If you click on the "Cross GCC Compiler" item under Tool Settings, you can see "All options:" it should look like -DARM_MATH_CM4 -DTARGET_IS_BLIZZARD_RA1 -DPART_TM4C123GH6PM -I/Users/pjkim/Projects/TivaWare_C_Series-1.1 -O0 -g3 -Wall -c -fmessage-length=0 -mthumb -mcpu=cortex-m4 -mfpu=fpv4-sp-d16 -mfloat-abi=softfp -ffunction-sections -fdata-sections -MD -std=c99 -Wall -pedantic Check the Cross GCC Linker options. They should be something like this. -L/Applications/ --gc-sections -T../LM4F.ld You will need to supply a linker description file LM4F.ld in the main folder of your project. You can copy any one of the .ld files from the TivaWare examples folder. You basically needs this in the file: * This is part of revision 1.1 of the EK-TM4C123GXL Firmware Package. MEMORY { FLASH (rx) : ORIGIN = 0x00000000, LENGTH = 0x00040000 SRAM (rwx) : ORIGIN = 0x20000000, LENGTH = 0x00008000 } SECTIONS { .text : { _text = .; KEEP(*(.isr_vector)) *(.text*) *(.rodata*) _etext = .; } > FLASH .data : AT(ADDR(.text) + SIZEOF(.text)) { _data = .; *(vtable) *(.data*) _edata = .; } > SRAM .bss : { _bss = .; *(.bss*) *(COMMON) _ebss = .; } > SRAM } Go back to the appropriate sections to fix any errors. My username is pjkim. Change to yours. This should give you a working IDE for compiling your projects into an .elf and .bin file. Get this working before going to the next step, "Flashing Programs." Step 3: He was flashing the Release version which doesn't include the debug symbols in the .elf file. I chose to use the Debug version for this reason. Name "Debug flash." Location "/Applications/" Working Directory: "${workspace_loc:/${project_name}/Debug}" and Arguments: "${project_name}.bin" This should give you compile and flashing capabilities. N.B. lm4flash in the current version of Energia (0101E0010) is broken. You will need to replace it from the prior version or as I did, build from source ( The last part of the puzzle is in IDE debugging. This part works now but it was tricky to get working and I am not exactly why it is so fidgety. If it is not working properly, I suggest trying to isolate the problem by running openocd in a terminal window and gdb from eclipse. If this works, do it the other way around, run openocd in eclipse and connect to the board using gdb in a terminal window. That way you can narrow down where you need to fix things. Debuggin: Step 2: Location: "/opt/local/bin/openocd" Working Directory: "/Users/pjkim/Projects/openocdDir" and Arguments: "--file ek-lm4f230xl.cfg" You will need to create a openocdDir folder and put in the file ek-lm4f230xl.cfg. The contents are: # # Comments go here # source [find interface/ti-icdi.cfg] set WORKAREASIZE 0x8000 set CHIPNAME lm4f230h5qr source [find target/stellaris_icdi.cfg] Step 7: There is a known bug in gdb or openocd that can cause connection problems. The workaround is described in Get the target.xml file from and rename it. Put the file in your Project/Debug folder. If anyone knows how to do this better/automatically, I would appreciate it. Change the Initialization commands to set tdesc filename ../target.xml target extended-remote :3333 monitor reset halt And you should have a working IDE. Here is a screenshot of the IDE in action: Wouldn't it be nice if TI could package all of this into a .dmg file?
  11. Hello I'm not sure where to post, so I do it here, please feel free to give me the correct topic to go to, Sorry !-) I am new to MSP-EXP430F5529LP and Energia. I tried to install Energia 0101E0010 following the getting started webpage ( Everything looks correct but Serial Port is grey, no ways to get it... So, I tried to install 0101E0009. Here, Serial ports are looking correct (although I have 2 potential candidate ports that I have seen nowhere in the topics on this forum: /dev/cu.Z530i-SerialPort-1 or /dev/cu.Z530i-Dial-upNetworking-2, or the corresponding ones with tty instead of cu), but the MSP-EXP430F5529LP is not on the list of available boards... Could anyone help? Thanks a lot Pablo
  12. I'm trying to start working with a TI Launchpad on my Mac (I also have a Ubuntu virtual machine I can work in), and I want to program it in assembly using mspgcc. However, I'm getting confused with a lot of the information I'm finding about how to actually write code for this! Any assembly tutorials I find (even in the MSP430 Microcrontroller Basics book) use references such as #WDTPW|WDTHOLD, &WDTCTL or &P2OUT, and whenever I try to compile assembly files with those, mspgcc throws a bunch of errors about how it can't refernce those. So, what is the best way for a beginner looking to program in assembly on a TI Launchpad to get started? What am I doing wrong when I compile all of these test files? (If I didn't provide enough information, feel free to ask for more)