• Announcements

    • bluehash

      Forum Upgrade   03/11/2017

      Hello Everyone, Thanks for being patient while the forums were being fixed and upgraded. Please see details and report issues in this thread. Thanks!

Rickta59

Global Moderators
  • Content count

    1,077
  • Joined

  • Last visited

  • Days Won

    57

Everything posted by Rickta59

  1. You can hack your gel script: $ diff tm4c1294ncpdt.gel rk1294ncpdt.gel 127a128,132 > OnRestart() > { > GEL_AdvancedReset("System Reset", 1); > } > $ pwd /home/kimballr/ti/ccsv7/ccs_base/emulation/gel
  2. So ... I just used the offline installer to load the lastest CCS 7.1 on ubuntu 16.04 64 bit. I didn't seem to have any issues debugging the blink.ino program. Maybe you could hop on IRC and explain further. [Edit 1] ... I take that back ... I switched to a TM4C1294 and I see it is faulting right away. [Edit 2] ... appears to be faulting in _init() [Edit 3] ... appears to be faulting in timerInit() ... seems to think I have a tm4c123gxl .. and is trying to set the 80MHz clock ... that is where it crashes ... looking at the properties, look at the GNU Compiler/Symbols I see ${ENERGIA_CORE_SYMBOLS} hovering over that it shows the wrong values [Edit 4] doh ... I had selected the wrong board type .. going back to recreate with proper board [Edit 5] ok .. went back selected proper board no fault, debugging works fine. Maybe you want to check which board you used to create your Energia project are you sure you picked the tm4c1294? It seems picking the wrong board TM4C board will allow you to create a file that is upload and then starts to debug but crashes right alway. Maybe this is your problem?
  3. well that intervention doesn't seem all that bad.That is your only issue?
  4. Looking back at your images, I'm not even sure how debugging with Energia and CCS works. My suggestion, is to use openocd and the arm-none-eabi-gdb that comes in the Energia package directory. In ubuntu, run energia and compile your sketch, note where the /tmp/buildxxxx/ files end up that is where you find the .elf file. Then open two xterms, in one run openocd and in the other run the gdb: [in xterm 1] ... $ openocd -f board/ek-tm4c1294xl.cfg [in xterm 2] .. $ $HOME/.energia15/packages/energia/tools/arm-none-eabi-gcc/4.8.4-20140725/bin/arm-none-eabi-gdb -q -ex 'target remote :3333' /tmp/buildxxxx/yoursketch.ino.elf Reading symbols from /tmp/buildf952838f75b6bd4033bf414decbd1185.tmp/sketch_mar21a.ino.elf...done. Remote debugging using :3333 0x0000041a in delayMicroseconds (us=us@entry=500) at /home/kimballr/.energia15/packages/energia/hardware/tivac/1.0.2/cores/tivac/wiring.c:110 110 elapsedTime = (startTime-(HWREG(NVIC_ST_CURRENT) & NVIC_ST_CURRENT_M )) & NVIC_ST_CURRENT_M; (gdb) mon reset init adapter speed: RCLK - adaptive tm4c123gh6pm.cpu: target state: halted target halted due to debug-request, current mode: Thread xPSR: 0x01000000 pc: 0x000002a8 msp: 0x20008000 (gdb) b ResetISR Breakpoint 1 at 0x2a8: file /home/kimballr/.energia15/packages/energia/hardware/tivac/1.0.2/cores/tivac/startup_gcc.c, line 432. (gdb) c Continuing. Note: automatically using hardware breakpoints for read-only addresses. Breakpoint 1, ResetISR () at /home/kimballr/.energia15/packages/energia/hardware/tivac/1.0.2/cores/tivac/startup_gcc.c:432 432 void ResetISR(void) { (gdb) -rick
  5. I don't have the arm compiler stuff installed in my CCS install, however I did install the tivac library into energia 1.6.10E18 and then tried to debug it with the arm-none-eabi-gcc tools I have installed on my linux setup. I have arm-none-eabi-gcc version 6.2.1 as my default. It won't debug the .elf file generated with the energia compiler which is arm-none-eabi-g++ version 4.8.4. If I use the arm-none-eabi-gdb in from the energia packages with openocd: $ /home/kimballr/.energia15/packages/energia/tools/arm-none-eabi-gcc/4.8.4-20140725/bin/arm-none-eabi-gdb -ex 'target remote :3333' sketch_mar21a.ino.elf It works fine. I can set a break point on ResetISR without issue. $ /home/kimballr/.energia15/packages/energia/tools/arm-none-eabi-gcc/4.8.4-20140725/bin/arm-none-eabi-gdb -q -ex 'target remote :3333' sketch_mar21a.ino.elf Reading symbols from /tmp/buildf952838f75b6bd4033bf414decbd1185.tmp/sketch_mar21a.ino.elf...done. Remote debugging using :3333 0x0000041a in delayMicroseconds (us=us@entry=500) at /home/kimballr/.energia15/packages/energia/hardware/tivac/1.0.2/cores/tivac/wiring.c:110 110 elapsedTime = (startTime-(HWREG(NVIC_ST_CURRENT) & NVIC_ST_CURRENT_M )) & NVIC_ST_CURRENT_M; (gdb) mon reset init adapter speed: RCLK - adaptive tm4c123gh6pm.cpu: target state: halted target halted due to debug-request, current mode: Thread xPSR: 0x01000000 pc: 0x000002a8 msp: 0x20008000 (gdb) b ResetISR Breakpoint 1 at 0x2a8: file /home/kimballr/.energia15/packages/energia/hardware/tivac/1.0.2/cores/tivac/startup_gcc.c, line 432. (gdb) c Continuing. Note: automatically using hardware breakpoints for read-only addresses. Breakpoint 1, ResetISR () at /home/kimballr/.energia15/packages/energia/hardware/tivac/1.0.2/cores/tivac/startup_gcc.c:432 432 void ResetISR(void) { (gdb) You might want to check that the gdb being used in CCS is the same version as the one being used in your energia install. -rick
  6. Also, are you using an msp430g2553? If so, you probably want to use the PUSH2 constant instead of 33.
  7. Don't you want to read the ButtonOne as INPUT?
  8. FWIW: using energia to program an msp430g2231 is an exercise in frustration. If you really want to use this chip, you would be better off using the TI C samples and the CCS IDE. Energia has been becoming less and less friendly to the smaller msp430g series for a long time. It is really focused on the higher end boards like the msp430f5529, msp430frxxxx boards, and msp432. Much of the msp430g support is broken in Energia 1.6.10E18.
  9. For a variety of reasons you can't use 16MHz on the msp430g2231 without a lot of hassle. The answer to your problem was given over in this thread recently:
  10. re: msp430-lg-core in 2 places: I was talking about what ships in energia 1.6.10E18 ... in other words what is in https://github.com/robertinant/EnergiaNG vs what is in https://github.com/energia/msp430-lg-core re: the build process Yes that is how I was able to build a version from EnergiaNG
  11. I have no idea where I would find the source code to version 1.6.10E18 of Energia. I would like to fix issues that I've previously reported and seem to be "sort of fixed" in the msp430-lg-core but aren't. Could you please point me at the source or release tag? Also, do you have a roadmap for the future development of Energia? Its progress seems to have stalled. -rick
  12. Why aren't the release notes here: http://energia.nu/releasenotes/ ? Is there an E18 commit tag I missed in that tree? When I build the latest version of that code I end up with a 1.6.11E18 version. However, it is broken for the msp430g2553, at least that one I haven't checked other msp430 core targets. void setup() { Serial.begin(9600); } void loop() { Serial.println("blah"); delay(1000); } That code will not link and gets an undefine for i2c_txrx_isr() and i2c_state_isr(): If I include <Wire.h> in the code then the problem goes away. But that isn't the point. Also, why is the msp430-lg-core in 2 places. The code in msp430-lg-core seems closer to what shipped but it is still different than what is shipped, at least for the linux platform.
  13. Also, where are the release notes for E18? I see ones for E17 on energia.nu but nothing for E18
  14. yeah .. that is the wrong thing ... which is why I asked. Yeah that is not being maintained any more. Look at the commits compared to the EnergiaNG tree. https://github.com/energia/Energia/commits/master The latest stuff seems to be in https://github.com/robertinant/EnergiaNG someplace. However I don't see a 1.6.10E18 release tag or even a commit that would indicate where the E18 snapshot was done. This core does sort of have what is in E18 however there are differences. In addition, the core is in 2 places. in the robertinant/EnergiaNG tree and also in the msp430-lg-core. The msp430 core in EnergiaNG is broken, you have to include <Wire.h> in all your code to get it to compile. -rick
  15. I guess you are right then it must be the software. I'm just surprised that the scores of other people haven't had this same problem. @Fmilburn just tested with V17 it appears he is using some manner of windows. I'm on linux and it seems to work fine. Maybe it is a platform issue.
  16. Do you have any decoupling caps on the msp430g2553? How about on the nrf24l01+ ?
  17. do you have a g2553 launchpad you can test with?
  18. does a blink test work fine on that setup? It looks like the Orange and Brown are both plugged into P1.6
  19. In v18 it tells you that you can't find SPI.h
  20. the problem is the example code there @fmilburn ... move the #include <SPI.h> ahead of the include <Enrf24.h> ... #include <SPI.h> #include <Enrf24.h> #include <nRF24L01.h> Enrf24 radio(P2_0, P2_1, P2_2); // CE, CSN, IRQ pins ...
  21. can you take a picture of your board and how the wires are connected and post it here?
  22. $ pwd /home/kimballr/energia-1.6.10E18/hardware/energia/msp430/libraries/SPI $ ls examples keywords.txt library.properties SPI.cpp SPI.h utility /edit ... Sorry this is not the place to deal with SPI issues. You might resolve those before continuing to post in this thread about /editoff
  23. I have no idea what you mean about both versions. ... I just went to see what is offered I see a 1.6.10E18 version of Energia are you running that? /rant on ... man this new version of the forum is painful to use ... i just tried to quote .. and i have no idea how i eventually was able to edit after the quote ... I used to have problems but there was an html option which is how i usually created posts ... seems to be gone ... /rant off I was going to post
  24. SPI.h is part of energia if you got your spi from someplace else, it is probably wrong
  25. My point was that I gained 49 posts. 1001+49 = 1050