Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


LIJsselstein last won the day on January 18 2020

LIJsselstein had the most liked content!

About LIJsselstein

  • Rank
    Level 1
  1. As a form of documenting... I just added another new MCU to Energia and -in short- had to do the following to get it working: In Energia 1.8.7E21: Copy from a close family member the following files and replace the model name with the new model name in the directory-/filename and file content: \hardware\energia\msp430\variants\[existing-model]\ \hardware\tools\DSLite\common\targetdb\devices\[existing-model].xml \hardware\tools\DSLite\common\targetdb\options\[existing-model]_GNU.xml \hardware\tools\DSLite\common\targetdb\options\[existing-mode
  2. Thanks for pointing me to right location. 👍 I always assumed that msp430-lg-core stood for legacy so didn't look further in the tree... I haven't been able to try this yet because the make_mito_release.sh script tries to download this file but the website constantly reports that it's offline due to maintenance for 2 days. Edit: Searching for the correct link via the Design Resources webpage on the ti.com website I get a new link to the latest Linux compiler.
  3. Perhaps I have missed something but it seems that the latest Energia 1.8.7E21 with Eneriga MSP430 boards package 1.05 is still using gcc 4.6.3 from 2012. Where can I find the updated board package with the msp430-elf-gcc compiler? If this project hasn't been completed yet, what can be done to help it forward, how can I help?
  4. Might be related to this pull request: https://github.com/energia/Energia/pull/1032
  5. I believe that the documentation in wiring.c is wrong so I suggested a fix for that in this PR. I didn’t know that VLO could not be chosen for ACLK on the FR2433...so thanks for that. This topic on E2E essentially mirrors this thread.
  6. Energia on the msp430fr2xxx-4xxx range falls back to using the REFO 32kHz clock when the external 32kHz crystal is not populated. REFO is a nice stable/accurate clock, but when you look it up in the datasheet (e.g. p24 in FR2433) you’ll notice the consumption is 15uA. See also line 139 in wiring.c. So, to get really low power with Energia (~1uA in LPM3 with sleep/sleepSeconds), either customise wiring.c to use VLO clock instead of REFO (but you loose clock accuracy) or add external LF crystal. Using driverlib/CCS without ext. LF crystal is basically the same: lowest power=inaccurate clock
  7. I think this is because, when there is no external XTAL connected, Energia (wiring) usually falls back to the VLO source (~12k Hz). But on the FR2433 the clock falls back to the REFO source which runs about 3x faster ( ~32768 Hz). However the code in wiring.h does not reflect this. Please look around line 144 in wiring.c (hardware/energia/msp430/cores/msp430/wiring.c): /* ACLK = VLO = ~ 12 KHz */ vlo_freq = 8000; /* Source ACLK from REFO */ CSCTL4 |= SELA__REFOCLK; Where I think it should be: /* ACLK = REFO = ~ 32 KHz */ vlo_freq = 32768; /* Source ACLK from REFO */ CSCTL4 |= S
  8. I'm using mspflasher and, indeed, another launchpad (5969 or 6989) to program my custom board. Haven't done any online debugging yet (not necessary so far). Some shell scrips help create the info sections and flash the info&program.
  9. @energia Below is the relevant section from boards.txt: LL-MSP430FR2433.vid.0=0x2341 LL-MSP430FR2433.pid.0=0x0c9f LL-MSP430FR2433.name=LoRa Logger w/ MSP430FR2433 LL-MSP430FR2433.build.mcu=msp430fr2433 LL-MSP430FR2433.build.f_cpu=8000000L LL-MSP430FR2433.build.core=msp430 LL-MSP430FR2433.build.variant=lora_logger_fr2433 LL-MSP430FR2433.build.board=lora_logger_fr2433 LL-MSP430FR2433.upload.tool=dslite LL-MSP430FR2433.upload.protocol=dslite LL-MSP430FR2433.upload.maximum_size=15360 LL-MSP430FR2433.upload.maximum_data_size=4096
  10. @energiaDo you know if the CCS team is planning to support importing Energia projects for non-launchpad boards? I have an Energia project with a custom MSP430FR2433 board and would like to use the CCS debugging features, but when trying to import the project CCS does not import the board definition as well, it only allows you to select Launchpads.
  11. Thanks, wat was your criteria for singling out these libraries/protocols? There are a gazillion protocols and software tools that could be used for remote communication, ranging from very simple to very complex, form propitiatory/manufacturer specific to modbus, mqtt and IEC 60870-5. An xkcd cartoon would be appropriate.
  12. If you see noise than that could be ringing caused by fast rise times of the digital I/O. You can try to add a ~50 Ohm resistor in series the SDA and SDL lines, place the resistor close to the transmitter.
  13. Yes, a collegue and I have been doing all of the above with a G2553 (and other chips like the 28 pin version and the FR2433) using sleep (LPM0), sleepSeconds (LPM3), interrupts, ADC and master/slave I2C. We found two bugs in the I2C implementations and made bugreports and pull-requests for them. At least one pull-request is over a year old and has not been pulled-in, not sure why. So, it depends a bit on your specific situation if you'll run into any problems or not. CCS we found especially useful to do register level debugging of our I2C problems after importing the Energia sketch (which does
  14. To answer my own question: the error is triggered because, for 16 or 32 bit operations, the variable must be aligned on an even memory address, however the INFOMEM_CORRECTION_VALUE variable was defined on an odd address. Moving it from 0x1855 to 0x1856 solved the compiler error.
  15. I also often have problems with libraries in Energia where the compiler says 'No such file or directory' while the library is clearly installed correctly. In at least one instance I was able to fix this, perhaps this works for you as well: When the "#include <BlynkSimpleTI_CC3200_LaunchXL.h>" statement is in a header file but only the accompanying .cpp file is referencing anything in the Blynk library then you could try to move the #include to the .cpp instead.
  • Create New...