Jump to content
43oh

pjacobs4

Members
  • Content Count

    14
  • Joined

  • Last visited

  1. Works great! This has been killing me for the last month!
  2. What is the fix for optimize for size?
  3. If I comment out all the sprintf commands, the sketch will compile and it is ~87k. If I include just one sprintf command, it won't compile and says it is 23000 bytes over the limit. I am just looking to change a float with one decimal place and wrote a small function that does it one digit at a time.
  4. Isn't too bad, seems about the same as one the Tiva 123. I have found that using the sprintf function kills my memory usage and won't compile. I had to write a small custom float to int routine without using malloc to make sure I have enoug memory.....
  5. I got it to work with the LCD library, went back and started from scratch.
  6. The communication is UART, and I can see the Serial.Print statements as the sketch runs. What I meant by SPI1 was this: SPI.setModule(1); SPI.begin(); I set the port numbers to the following: _pinScreenChipSelect = 18; //2; _pinSerialClock = 7; _pinSerialDataMOSI = 15; _pinSerialDataMISO = 14; _pinDataCommand = 6; _pinTouchChipSelect = (version==1) ? 9 : 10; _pinReset = 11;
  7. I am using the LCD library and modified it heavily to change the pin numbers to match the SPI output on the CC3200, use SPI1, and included the hardware in the conditional statements in each of the .c and .h files. I am trying to run the basic .ino that comes with the library. I am seeing the serial output updating and finishing the program, but the screen just stays bright white. I also wired using jumper wires as one of the pins moved for SPI. Anyone have any ideas as to where to start. I haven't included the code as it is so many files. I have tried the nightly build as well a
  8. Sorry autocorrect gone wild. What meant was as it seems to be the same chip as in the tiva 123, will energia work with this board if I select it?
  9. As this seems to be a time chip at 80 my, will energia work if you select the 123 board?
  10. My UDP with the NTP server has been crashing my 129. I am going to see if this helps...
  11. Below in responesProcess() is where it breaks. I did a workaround and set the update time to 60 seconds and created 2 clients, one to get data and one to put data. When the get is complete it changes a boolean and the put fires on it's own client. I made a thermostat and am using two vars on Xively to know when to change the set temperature and mode. It then uploads the current temp and operating conditions which can then be plotted. I have posted the example code as it happens there as well. #include <Ethernet.h> #define APIKEY "YOUR API KEY GOES HERE" // repl
  12. I am using a Connected launchpad (129) and the stock example from Energia v12 for Xively Client Actuator. When I upload to Xively, everything works great and the client.stop() command works as expected. When requesting data and parsing the response, if I call stop it kills the loop[ and the board hangs until I reset. If I don't call the client.stop() it will eventually time out the connection and allow me to loop, request and then parse the data with no issues. I am just looking for a starting point for this as it is a pretty new board and there aren't many posts about it yet.
  13. Definitely sped things up about 5 times. Are these considered normal? *** LCD_protocol (All times in ms) LCD 2.2 Touch BoosterPack 176x220 Square(100) 102 Square(50) 26 10xFontSolid(true) 1580 10xFontSolid(false) 3005 Ratio% 52 Original(=1) 390 point(readPixel()) 368 copyPaste() 0 ---
  14. I changed the required lines and the code compiles and uploads, but there are a few issues. When using the test ino script: 1. the text on the squares is not rendered 2. The text rendering screen takes 5 and 7 seconds, way longer than my 123 The speed is just so slow, is there something in the clock divider settings that I need to tweak?
×
×
  • Create New...