Jump to content

rando

Members
  • Content Count

    23
  • Joined

  • Last visited

  1. Howdy! There are so many good ideas here, I don't know quite where to start. I don't have my development machine working as it is in the middle of an upgrade, but I did download the MSP430G2553 flavor of SIMPL and flash it to a spare Launchpad. Do you have some example sessions of talking to it anywhere, I assume it's running at 9600 baud on the LP? I would like to gets some hands on experience. I can help with the port to the 16F1XXX, actually the 16F1455 might be an elegant, minimal fit. Best, Randy
  2. All, This fault was corrected when in desperation, I tried to re-establish a link via a CCS session, with the EPB MKII off the board. I was able to hit the reset button, on another example, debug correctly and then reattach the EPB MKII and run the FFT demo properly. So the error message regarding manually resetting the DAP debugger, via the reset button was correct. Be advised, the FFT demo requires patching, the demo that ships in the examples, is broken fatally. Best, Randy
  3. Thanks all! To be more specific, the Energia, EBP MK II samples, shipped with v.16 do not support the graphic LCD found on the EPB MK II, for the new MSP432 LP. However there are example(s) for CCS, that ship within the support for the Education BoosterPack, as demonstrated aptly here. https://www.youtube.com/watch?v=0BdCLLynk4Y, in the "Out of Box Demo" I have a recently upgraded version of CCS 6.1, and I tried one of the Out of box demos on the CCS Cloud (very very impressive business, CCS Cloud!) Here's the error I have... Error connecting to the target: (Error -1063 @ 0x0) Device ID is not recognized or is not supported by driver. Confirm device and debug probe configuration is correct, or update device driver. (Emulation package 6.0.14.5) And in a similar vein for Energia 16 ... Fatal: CORTEX_M4_0: Error connecting to the target: (Error -1063 @ 0x0) Device ID is not recognized or is not supported by driver. Confirm device and debug probe configuration is correct, or update device driver. (Emulation package 5.1.641.0) Failed: Failed to evaluate GEL_Connect(): Connect failed I've tried reinstalling TI Emulators and downgrading to 6.0.14.0, without success. There was in attempt to upgrade the firmware on the the MSP432 LP I think, this may have failed? R.
  4. Folks, FYI, for anyone with the new LP MSP432, and MK II booster pack, form a Energia perspective, might be smart to wait awhile before purchasing. Doesn't seem quite supported yet! R.
  5. All, So disappointed today to see that the LCD checkout examples do not support the MSP432. Does anyone know of a simple sketch to exercise the LCD on the Education Booster-pack MK II, for the MSP432 ARM Launchpad? I would run the CCS based projects, but the CCS update for the debug probe broke that today. . Any help much appreciated! Best, R.
  6. All, I have a MSP430F5529 USB LaunchPad Evaluation Kit in storage, I will try it with the MK II and see if that's the issue. R.
  7. Howdy All!, I just un-boxed a Education PB MK II, the back light jumper works fine, all the serial examples compile OK on my Tiva-C 123GXL, I'm seeing the debug messages at 9600 baud perfectly. The screen is just gray, so no sign of activity on any of the LCD Energia examples I tried. Before I RMA it back to TI, anyone have an idea what might be wrong? Thanks, R.
  8. Hi folks! Anyone have some insight on when Energia will become sensor tag 2 "aware". I see on their site that they are advertising compatibility... http://www.ti.com/ww/en/wireless_connectivity/sensortag2015/gettingStarted.html Best, Randy
  9. Folks, Seems that Energia 15 runs without lagging issues, and no back channel comport failures on Ubuntu velvet. Make sure to use the recommended udev rules posted on the Energia web site. "No drivers are needed for this LaunchPad under Linux. You do need to add this LaunchPad to udev rules. To do so, follow the steps below: Download the udev rules: TI udev rules Open a terminal and execute the following command: sudo mv /71-ti-permissions.rules /etc/udev/rules.d/ If your Linux distribution supports the service command you can active the new rules with sudo service udev restart. If your Linux distribution does not support this command or if you are not able to upload to the LaunchPad with Energia, then restart your computer to activate the rules." Testing with both the '2452 and '2553, was fine with the ASCIITable example. (Don't forget the jumper change for the hardware UART on the '2553). I guess the comport driver issue is finally resolved. Best, R.
  10. Would it be impolite to inquire, on the status of TI's response on this matter? Thanks! R.
  11. Anyone, Does anyone know what happened regarding the manufacture and sale of the Education Booster Packs, both I & II? I asked this question a while ago and wanted to refresh the question. R.
  12. All, Does anyone have a notion how best to insure that... The newly build cdcacm.ko file is ... "sudo modprobe -r cdc_acm (just in case it's been already loaded) sudo insmod ./cdcacm.ko" happens and automagically "sticks" until the next reboot? Does it make sense to keep the old copy? R.
  13. Here's what I was hoping to get working, Fired up minicom, set for 4800, brought up the board in mspdebug and told it to run. Voila!
  14. Everyone, Thanks! These instructions worked perfectly and has seemed to corrected most the issues I was having. Will post more when I've test more completely. I need to think about if I can still program the board, and what it takes to get the new module to "stick", (if anything) My compile issue was I think, I was not in proper directory when I issued the make command. That being some other directory than where the kernel headers were located. At least the serial demo, ASCHIITable, runs after reset and I can see the ouput in Energia's serial terminal on /dev/ttyACTM0 now. Just to review I am on Ubuntu 12.04 LTS, 3.2.0-34-generic-pae. R.
  15. r. I've seen these posts before, but forgot about their significance... oops! Hey I'm getting this error when I attempt to use the make file to rebuld a new cdc,etc. make[1]: Entering directory `/usr/src/linux-headers-3.2.0-34-generic-pae' make[1]: *** No rule to make target `Launchpad'. Stop. make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-34-generic-pae' make: *** [all] Error 2 Have you seen this? Thanks Randy
×
×
  • Create New...