Hi,
Has anyone tired programming the TM4C123G micro-controller with Labview 2013 and was it successful?
Thanks,
Sam Wilson
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hi,
Has anyone tired programming the TM4C123G micro-controller with Labview 2013 and was it successful?
Thanks,
Sam Wilson
Hello Sam
I do know that someone had encapsulated the LMFlashProgrammer using System.vi and then used it for programming.
Regards
Amit
Hi Amit,
Thanks for the reply. Will this also allow me to write commands to the chip and read/write registries. If so, how do I encapsulate LMFlashProgrammer with system.vi?
Thank you,
Sam
Hello Sam,
No this will not help access registers for read or write operations. It is more for Program Bin file download, Erase and Unlock of the device and for UART based bootloader update.
Why not use CCS or any other debugger? This can be integrated in LabView to do what you intend to do. But I haven't done anything like this yet for sure. So the community would be able to be of much assistance here.
Regards
Amit
Hello Sam,
If you're using an MCU and communicating with it using USB, I think you'll find this tutorial helpful:
USB Instrument Control Tutorial
sine.ni.com/np/app/main/p/ap/ictrl/lang/en/pg/1/sn/n17:ictrl,n21:25/fmid/6000/
This will guide you into making a VISA resource from your USB MCU, so that LabVIEW can talk to it as a resource. If you're instrument uses USBTMC, everything should be simple enough from a protocol standpoint. If the MCU uses USB Raw communication, you'll have more work to do in order for the protocol to work fine.
That being said, if you're using NI-VISA, regardless of the protocol (USBTMC, Raw) and bus (PCI, USB, Serial), you will need to know the exact command set that the instrument (MCU, in this case) is expecting in order to communicate with it. On the example, we use a "*IDN?" command which is part of the SCSI command set, which is common to most instruments. What this command does is just return the serial, model number and OEM name.
Other model-specific commands (such as digital read port 0 line 2, write 2V to analog channel 3, etc) should be provided by the OEM of the instrument.
Here are some links that can be useful for you:
USB Raw information
http://zone.ni.com/reference/en-XX/help/371361J-01/lvvisaprop/usb_raw/
http://forums.ni.com/t5/Instrument-Control-GPIB-Serial/Connecting-a-customized-Class-RAW-USB-device-to-Windows-7-by/m-p/2337630
USB Raw Examples
https://decibel.ni.com/content/docs/DOC-2029
https://decibel.ni.com/content/docs/DOC-2022
Thanks,
@cb1-
Pas de quoi, mon ami!
The links where proving to be a problem in the first attempts. Then they all showed up at once.
There is still a lot of work involved with getting it to work, but the tutorial and examples should help.
BTW, got my CC3200 so I'll be dropping in every now and then :)