Jump to content

All Activity

This stream auto-updates     

  1. Last week
  2. 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-model]_TI.xml \hardware\tools\msp430\msp430\lib\ldscripts\[existing-model]\ \hardware\tools\msp430\msp430\include\[existing-model].h Add the new model to the following files: \hardware\energia\msp430\boards.txt \hardware\tools\msp430\msp430\include\msp430.h \hardware\tools\msp430\msp430\lib\msp430mcu.spec Of course, check for differences between the two family members (e.g. missing or added peripherals, memory sizes) and edit the copied files accordingly.
  3. > 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.
  4. 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
  5. If I recall correctly: I do not think you need to do any watchdog setup with Energia. The Energia core sets it up as for use as the timebase for time functions. Any changes you make to the setting outside the Energia envelope will cause issues. See:
  6. I'm new to micro-controller programming and am seeking some help. I'm using the MSP-EXP430G2553 Launchpad. Following examples from online contributors I have inserted the following as the first line of code: // WDTCTL = WDTPW + WDTHOLD; // Stop WDT However, when this is enabled it prevents serial monitoring and interrupts from working. I don't know if it is relevant but the uart jumpers are set to HW.
  7. Earlier
  8. When using the latest version of Energia the wire (I2C) has now the function setClock to set to 400k use setClock(400000UL);
  9. Hello everyone, I am facing a problem in changing the clock frequency of I2C communication in energia i.e 100khz to 400khz. Is there any way to change it? regards, Anirudh
  10. Hi All, ENERGIA is a nice IDE indeed. Very useful to test the LAUNCHPAD in few minutes. I have a couple of LAUNCHXL-CC1310. They come with the RF PACKET ERROR RATE inside preloaded. The question is: since I have loaded some examples using Energia IDE, is it possible to have that EXAMPLE in this IDE? I tried to reload from CCS in cloud without any luck. CCS in cloud works with some basic examples (blinky and so on....) Thank you very much Best Regards Fabio OS: Windows 8.1 IDE: Energia 1.8.11E23 Board: CC1310 LaunchPad -- LAUNCHXL-CC1310 Rev. 1.4.1-- PG2.1 -- FW Rev: 1.0 1638 Display: 430BOOST-SHARP96
  11. 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.
  12. https://www.masterelectronics.com/ https://www.onlinecomponents.com/ great prices, low to no shipping
  13. Thank you for your detailed explanation. That helps a lot.
  14. They are not connected to the relay. They go directly to the load. To turn the load on or off, you need only interrupt one current carrying wire. You usually want to interrupt the HOT lead, so when the switch is off, no part of the controlled device presents a voltage that is a hazard. (This, of course, does not consider parts that store energy, like capacitors) (If you have further questions, ASK. Better to ask than someone get hurt or property get damaged. But please do tell us where you are located. The systems in the US/Canada, UK, rest of the EU, India, etc, all differ, and often differ within a single country based on region) Background: The underlying assumption here is that the source has one line that is essentially at ground (earth ground), and the other is HOT, meaning it it at 120V or 240V (AC RMS) relative to ground. In the US and Canada, this is ensured by connecting one wire at the service entry to the earth ground (this is called BONDING), such that one current carrying wire is within a fraction of a volt of ground (called the NEUTRAL-- formerly called GroundED in the US), the other is 120V RMS relative to ground. Similar systems are use in much of the world. For example, in most of the EU (and UK, which may soon be a separate entity), one stab is grounded at the entry, and the other is therefore 230V relative to ground. When there isn't a stab for the earth ground connection (safety ground), there is some provision in all modern systems. If I recall, the common one in the EU is the bracket (clip?) on the perimeter of the plug. The intent is that the EARTH GROUND (safety ground) only carries current when there is a problem, and that the safety device (fuse, circuit breaker, ground fault interrupt) should interrupt the circuit when that happens. Since the NEUTRAL current carrying wire does not present a safety issue, as it is near or at ground potential, we let it be. The GROUND (safety ground) conductor should NEVER, EVER be interrupted while EITHER THE HOT OR NEUTRAL is connected, which is why modern plugs have a longer stab for this. It connects first, and disconnects last. The line that should be switched is the HOT, which is not at or close to earth ground potential. I could (obviously) go on about why it is done this way, but I will cut it short by saying that it is the easiest way to minimize the number of ways that a fault can occur, and make it practical to protect against faults. ********************* Public safety message: bond your grounds properly. When using a portable generator, ALWAYS use a ground fault interruptor, be sure the ground is connected to a good ground tie (driven rod, metal building frame, etc) and the, when powering a building or gear in a building, tied to the building earth ground bus.
  15. Thank you for the reply and guidance. I am not sure whether I understand what you mean by the NEUTRAL is unswitched. HOT comes into COM, where does the NEUTRAL wire goes to ? Are you saying NEUTRAL and EARTH are not used/connected into the relay ?
  16. Have a look at the Read Me file on the New Compiler branch of the MSP430 core repository. Also of interest, Install release 7.3.1 of the GCC tool-chain for MSP430.
  17. Presuming you are trying to switch the power to an AC-powered device, such as a lamp or small appliance: You generally want the COM and NO (normally open) contacts. When the relay coil is not energized, these are OPEN (disconnected) so the load will be off. If you want the load to be ON when the relay coil is not energized, use COM and NC. If you want to switch between two loads, the loads go on NO and NC, and the source goes to COM. In general, the HOT current carrying wire goes to the relay COM, and the NEUTRAL (grounded) is left unswitched. The EARTH (safety) ground is not involved and should be passed straight through to the EARTH ground lead of the load, if it has one. The color conventions vary in different parts of the world, and not all commercial cords follow the conventions-- they are usually enforced in fixed wiring such as in a home of commercial building, but cords for plug-connected appliances are often not compliant. Several of the conventions are in messages above-- for example, in the US and Canada, the NEUTRAL conductr is WHITE insulated, and the screw or terminal on many devices like outlets is silver, the HOT conductor is BLACK (by preference. RED, BLUE, or any other distinct color than green may be used) and screw or terminal is often brass/copper color, and the EARTH (safety ground) wire is GREEN. The BLACK (or equivalent) should be switched.
  18. 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?
  19. Sorry for this late jump in here. Can you show me how this is connected from an AC source to the Relay module ? ie . Which wire from the mains are connected to the COM and NO/NC of the relay ? Thanks !
  20. can you show how are the AC wires connected to the relay ? Which wire goes to the COM and NO/NC ? Thanks !
  21. 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.
  22. 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.
  23. Odd that it programmed without an error due to the incorrect device. I would figure that there shouldn't be any issues, though. (this may not be clear.... sorry) The device selection for CCS gives the compiler information to select the device specific header file (which is a big part of information about what modules are available), as well as memory size and layout (so the compiler can do the allocation appropriately and know if there isn't sufficient memory-RAM or code memory- for the build). If you had tried to use a module that isn't available in the 2453 or the build needed more memory than the 2453 has, build would fail (probably). If you didn't, the devices are the same in all meaningful ways (address space, peripheral addresses, and so on. In particular, the code protection and JAG lockout) Apparently, there isn't a check that the device is what was specified.
  24. I have to ask if someone knows better. If I have MSP430G2553 controller but in CCS I forget to change the settings for controller and there was chosen the G2453, which is the 8KB version of the same controller..does this somehow damage the controller when I program them? They seem to work but I am not sure if this can cause some surprises or failures as it may happen accidentally when using different controllers??
  25. I will try this out. After some searches on embedXcode, it looks promising.
  26. It’s 10:08pm here in Europe, so I guess the correct answer is next year!
  1. Load more activity
×
×
  • Create New...