Jump to content
43oh

Rickta59

Members
  • Content Count

    1,135
  • Joined

  • Last visited

  • Days Won

    71

Everything posted by Rickta59

  1. Sure if the SHA files weren't hacked you might believe that. What if they hacked wordpress to upload new .tar files that are used in the build process? Since the files that are used to build the Energia distrubition are binary blobs, I don't have a way to build entirely from source. So the fact that the SHA checksums match means nothing.
  2. When I build they seem to download from energia.nu ... untar-unzip-download: [get] Getting: http://energia.nu/tools/energia-builder-linux64-1.3.18.tar.bz2 [get] To: /mnt/vbox/shared/github/EnergiaNG/build/energia-builder-linux64-1.3.18.tar.bz2 [get] .................................................... [get] .................................................... [get] .................................................... [get] .................................................... [get] .................................................... [get] .....
  3. I just downloaded the latest from energia.nu and the linux version is the same size as the one I downloaded a week ago. Did the hack involve any of the tar files that are downloaded when doing a github source build of EnergiaNG?
  4. does that mean the binaries that i've download, like the compiler etc, might be unsafe?
  5. Why use TimerSerial.cpp at all? That code was really for the g2231 and g2452 because they didn't have any real uarts. The msp430fr2433 seems like it has 2 real eUSCI peripherals.
  6. libstdc++ isn't and won't be part of the Arduino. If you want to use the full c++ you shouldn't be using energia. If you are using an msp430g series you are wasting your time wanting that. Which msp430 are you using? Are you even using the msp430?
  7. You could use the msp430-objdump on the compiled program_name.elf to see if the addresses of your ISR handler functions ends up in the proper vector table address.
  8. I don't think you can directly use headers from the new msp430-elf-gcc ( stuff included with CCS ) and the old open source version of msp430-gcc (stuff included with Energia). The biggest change is how they deal with the interrupt vectors. I compared the headers for the file msp430fr5969.h from the 2 compilers. Below is a just a small chunk of the changes ... > 4476,4501c4909,4934 < #define AES256_VECTOR (31) /* 0xFFCC AES256 */ < #define RTC_VECTOR (32) /* 0xFFCE RTC */ < #define PORT4_VECTOR (33)
  9. Seems like C2000 support has stalled ... Last checkin over a year ago https://github.com/energia/Energia/commits/C2000
  10. I see SFP cage slots aren't hideous - "http://www.mouser.com/ProductDetail/Amphenol-Commercial-Products/U77-A1114-100T/?qs=sGAEpiMZZMtLo%2bUrTGGA8Qu%2bjOiyxwrr" and the edge connectors "http://www.mouser.com/ProductDetail/Amphenol-Commercial-Products/UE75A206000T/?qs=sGAEpiMZZMvlX3nhDDO4ADdPO33nqrQcj0jVg%2b39E7Q%3d" - also not too expensive. Damn. I might have to get this rolling soon.
  11. One of the new features of the beta EnergiaNG is that fact that it is now using the standard Arduino 1.6.x IDE. Unfortunately, it doesn't look like it is ready to work as a boards manager package with the standard Arduino IDE. Energia/TI likes their branding and it seems they want to keep TI boards and Arduino board from ever meeting in the same program. At the same time, I noticed a few things that are missing and instead of trying to push those into Energia. I decided to fork the tivac-core and make the changes there. I also moved away from the proprietary dslite uploader in favor of
  12. If you are planning to make your own PCB the atmega328p comes in several small packages. .8 pitch 32 pin tqfp .4 pitch 28 pad vqfn 4x4mm https://octopart.com/search?q=atmega328p I don't see the advantage of using an msp430. Which one do you think is going to be smaller than the AVR version?
  13. ~$2- $5 from aliexpress.com
  14. Is there a specific reason you want to use an msp430?
  15. Show me a successful compile of that code without modification and I'll eat my msp430 launchpad. Those registers are specific to an AVR Atmega processor. There isn't any macro magic that is going to magically convert code written for an AVR Timer peripheral to an msp430 TimerA peripheral. You often see this problem with Arduino code and libraries. They often mix the arduino API with direct register access that is specific to AVR Atmega. That code wouldn't compile for any of the ARM Arduinos boards either. Here is a link that talks about using the AVR Timer peripherals: http://ww
  16. It seems like the only trouble might be the timer register code. TCCR1B &= B11111000; TCCR1B |= B00000001; TCCR2B &= B11111000; TCCR2B |= B00000001; The rest should just port over. Take a look at the TIMERA examples to see how to approach that code. -rick
  17. Could you provide a link to the sketch you are talking about?
  18. The problem with Energia right now is that it is using msp430-gcc. There are plans to move to the RedHat/TI port of msp430-elf-gcc soon but there are issues. Until then you can't use all the FRAM just the FRAM in the first 64k address space, which is typically about 48000 bytes instead of all the fram available at 0x10000 and above. https://github.com/energia/Energia/issues/806
  19. The problem I see with the approach above is the overhead of having pointer to functions instead of direct functions. Using C++ templates you can get compile time polymorphism with zero overhead. I noticed you are exposing the delay_us() function as a HAL method. I'm guessing you aren't expecting to actually get a 1 microsecond delay.
  20. Why LPM3 ? can't you bring it down all the way to LPM4?
  21. So I hope you kick back some cash to him for his knowledge and ours!
  22. It sounds like your board doesn't work. Debugging it in the launchpad is a waste of time. Just take the chip and solder 3 wire directly to the chip. GND, TST and RESET. Connect those wires to the launch pad SBW headers. Plug the chip into board and just debug it.
×
×
  • Create New...