Jump to content
43oh

NurseBob

Members
  • Content Count

    277
  • Joined

  • Last visited

  • Days Won

    40

Everything posted by NurseBob

  1. @stenkiste I spent the entire day fighting with this and after many, many attempts and hours of frustration I finally got the system working. Note: I am working with an MSP-EXP430F5529LP and am running energia-1.8.10E23. Given how the day has gone, I can't offer any guarantees that my "solution" will work for you. Ulitmately the steps that worked: 1: Via the disturbingly buggy board manager update to version 1.0.7 for the built-in boards (mine was on 1.0.6), which I believe applies to your board too. 2. Make sure Energia is using the right "platform.txt" file. I found that there
  2. Likely a dumb question/observation, but wondering about uint8_t: size_t printNumberCopied(unsigned long n, uint8_t base) Why uint8_t? I believe the Arduino code from which this was likely drawn is an 8-bit mcu. The msp430 are 16-bit. Is the printNumberCopied running into an overflow???
  3. I'm afraid I can't help with your specific problem. However, on any support site, regardless of device, OS, etc., error messages are absolutely required when asking for help, otherwise no one will be able to help you solve your problem. FWIW, merely changing the pin mapping from an Arduino to a launchpad device is only going to work in the simplest of cases. I know there are links on this site regarding porting Arduino libraries to msp43* devices. There are numerous examples of how to read/write microSD cards for the various TI launchpads. So, while you've proved the Arduino librar
  4. Considering that frmwhatsapp requires the Android OS, I don't see how you can do what want. You might consider googling "msp430 android interface." What I saw were references to a usb-connected f5529 to smartphone. Others were aimed at ble interfaces.
  5. LPM4 can be problematic. There is a bit you can set to enable ACLK in LPM4, but the default is for the clock to be off, and of course, the cpu is off. If I read the docs correctly, in LPM4 if ACLK is enabled, it uses the VLO as its source, approx. 10KHz, and is susceptible to temperature. See Table 3-2. System Clocks, Power Modes, and Clock Requests in slau367p.pdf For a quick read on the RTC take a look at slap113.pdf
  6. >energia also has in its software serial library error Well, no. The 5529 has hardware serial. Don't use software serial. FWIW, it's not an error in Energia, but a limitation of the software serial library that it can't run with the faster clock. HTH
  7. The first line in the error log says it all: java.io.IOException: Cannot run program "{runtime.tools.dslite-9.2.0.1793-e1.path}/DebugServer/bin/DSLite": CreateProcess error=2, The system cannot find the file specified It's not about the launchpad but your Energia/system configuration. In short, a "file not found" error for the compiler. So, an environment/path setting? On my system the compiler is found @ C:\ti\Energia\energia-1.8.10E23\hardware\tools\DSLite\DebugServer\bin if you search for dslite under your Energia installation is it found?
  8. It appears you're working with CCS and based on the device you reference, I'd suggest looking at the "Register Level" code examples in the Simplelink MSP432P4 SDK. (Resource Explorer) The one I found that is likely a good starting place for a simple timer A0 interrupt handler is found in the msp432p401xta0_01 code example for CCS.
  9. A quick look at your code reveals: You have a typo in your port_2 interrupt handler; you call ICC_read, but the implementation is in IIC_read... I didn't read further as the above is a show-stopper... There are numerous tutorials available for both I2C and interrupt handling to you to help get you started. Since you're using CCS, I'd suggest also posting your code & question on the TI e2e forum.
  10. Google is your friend... I did this lookup (msp430f5529 "write to flash" memory energia)and in under 5 minutes found this reference, which might serve as a starting point for you... FWIW, TI's example code for CCS/IAR can also serve as an educational reference. HTH
  11. > This is why I said it is odd, but I have never tried it myself with devices that are so closely related. I don't know if it actually was programmed with the wrong device specified, but I can see no reason there would be damage IF it was programmed this way < Agreed. Like you, I've never tried with such closely related devices.
  12. This is "expected behavior." When the watchdog is enabled, it needs to be serviced regularly on a schedule that's far shorter than serial communication. The intent of the watchdog is to restart the device in the event of an unexpected endless loop, or other conditions that result in the mcu hanging. This reference on Wikipedia will explain it better. FWIW - it is not at all unusual for makers (or others) to disable the watchdo. Bob
  13. Interesting. My experience with both IAR and CCS is that they refuse to load images to a device when it's different than what the project specifies and they both clearly report it as an error.
  14. " Multiple libraries were found for..." You've got a configuration error message. Time to read the docs on porting from other libraries. How-To: Porting Libraries Posting a Library for Energia Some Misconceptions about Libraries The above may provide guidance. I am not able to help much beyond this suggestion as I'm deeply involved in other non-coding projects at this time.
  15. Have you attempted #1 ? If so, what error messages, if any. If you've not even tried, time to edit code and see what happens. Re: #2 - time to read the docs... The calls to SoftwareSerial are well documented. As to the speed limit, yes. Google is your friend regarding both questions; there are dozens, if not hundreds of answered questions and coding examples on the topics of porting and serial communications.
  16. With C/C++ compilers you want to address/fix errors in the order they are presented - that is, read and understand that first error. Generally, compilers will cascade a long series of errors that all are triggered by that first error. FWIW, a missing semi-colon can trigger a similar long list of errors. So, looking at your first error message: " C:\Users\Harizazmi\Desktop\energia-1.8.7E21\hardware\energia\msp430\libraries\SoftwareSerial\SoftwareSerial.cpp:81:2: error: #error This version of SoftwareSerial supports only 16MHz processors" It's telling you that you have not select
  17. There's far too little information in your question to be able to answer. A screenshot or text file of the Actual errors will help point to the first problem. Debugging compile and link errors requires a structured approach, usually starting with a google search of the reported error statement. 1) Have you updated (ported) the Gamebuino-Meta.h for Energia compatibility? 2) Have you converted the bitmaps to a "C" representation - TI offers both sample code (CCS) and tools for that display with a '5529. Take a look at the MSPWare library for CCS sample code and comments, which may hel
  18. I can't specifically answer for Entergia, but from what I can see, it looks like you'll need to use CCS and perhaps the driver library.
  19. You've described the problem, but supplied no information to allow remote diagnosis. Without a schematic and related code, there's really no way to help, aside from the most general suggestions regarding jumpers, pins and I2C pullup resistors, all of which you've likely read (and hopefully applied). Finally, you mention migrating an existing project; did you have that working, and if so, under what version of Energia? Re: UART - there may be no hardware UART on your chip. "If your Launchpad is version 1.4 or earlier, the chips that it shipped with have no hardware UART and thus, n
  20. @Anshikajain Sorry, I've been offline for a couple of days. Not really sure what your question was, but FWIW, I rarely use Energia. That said, when I2C fails in Energia, it's almost always a configuration problem. My suggestion with the video was focused on how they configured the '430 jumpers. The G25 devices were significantly different from the later versions, and many have tripped over jumpers incorrectly configured. In your photo it appears you have the jumper P1.6 placed for the LED, and that was the very first comment in the video - the device will not work in I2C mode if that jumpe
  21. Take a look at this youtube, it may help...
  22. > I am currently studying for a computer engineering degree Cool > My first project (besides a blinking led) is to play a classical piece on an electric buzzer! A couple of thoughts: 1) Buzzers are not speakers; typically they have a very limited repertoire, like a single frequency... 2) Depending on the device you are using, you may find significant memory limitations. So, as always, RTFM the specs before you buy... Have fun
  23. Glad to be of assistance! :)
  24. To enable a hardware reset of the device. If the RST/NMI pin is low, the device is held in a perpetual reset. It needs to be high for the chip to run. Having made a similar omission years back I found out the need. Take a look at any of the LP schematics, or better yet, the specs. In SLAS590M.pdf (for a msp430F5529) you'll find a description on pg. 18. RST/NMI/SBWTDIO - Nonmaskable interrupt input, Spy-Bi-Wire data input/output when Spy-Bi-Wire operation activated
  25. @birgilfan, a simple schematic would be much more useful. Impossible to tell from the photo how you have wired the system. Do you have a 47K resistor between Vcc and reset? If not, nothing will work. The '430 needs a pullup on the reset line. I can see there's a resistor for the LED, but can't tell if it's also on the RST/SPWTDIO pin.
×
×
  • Create New...