Jump to content


  • Content Count

  • Joined

  • Last visited

About StupidPig

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Yup, my bad, erasing will get the bit as 1 rather than 0, and write will only able to get a bit become 0. When I type I just assuming "erase" means 0. Anyway, the whole point is about erase is needed before write.
  2. I forgot the flash write routine will clear the flash first or not, but I kind of remember it didn't. If not, you will have to clean the flash before write, as write only able to set 0 to 1, but not the other way.
  3. Thanks for everyone tried to help. Somehow it seems the voltage regulator I used is faulty and only giving out around 2.1v. The strip works fine after I replace the regulator, by simply direct connect clock and data line to P1.5 & P1.6.
  4. Saw this thread awhile ago, and think that would be cool to make some x'mas light with this. So I brought some APA102 strip on ebay and give it a try, but somehow I can't get it work. I get a spare 2231, hook up the clk to P1.5 and data to P1.6, but it only randomly turn on a couple LED on a 72-LED strip. Just to make sure the strip is working, I hook it up with a picaxe 08m (which been collecting dust for many years.... ^.^), write some simple basic code, and the strip seems works fine. Do I need a 3.3v->5v level shifter on the SPI lines? I was thinking 3.3V should be good for logi
  5. Sorry for late to the game...... I just updated to E13 and found the same delay issue during power up. Is that I just need to comment out all calls to enableXtal in wiring.c, to get rid of the delays during power up? My application needs to be start running once the device is powered up, and I don't have the external crystal in my design. Thanks.
  6. Sorry to bring this old thread back to life..... Is the same apply to the new QMathLib & IQMathLib which just released by TI, which we still can't use it with Energia?
  7. Yup, 59116 so far is my favorite TI LED Driver, only 2 pins needed, and all you need just set the intensity for each channel and it will take care of the pwm part all by itself. I'm not using it with my first MSP430 base sequencer two years ago, just because the I2C code is a bit too complicated with CCS, but now with Energia, it's piece of cake.
  8. Hi @@Blurred Talon, welcome! even thought I'm also a pretty new member here. RobG's sample code definately a good start for you. For bluetooth connection, take a look about the HC-06 module and the breakout board on here. I'm playing with that with my LED sequencer project except I'm going to using my own breakout board. Have fun!
  9. After using a hot air station for my smd work for about two years, I think it is time to upgrade my tools to increase my productivity, so I'm looking for adding a reflow oven to my workbench. I searched the web and found many threads about DIY reflow oven, and there are a couple kits looks pretty neat, but somehow all the kits are no longer available for purchase, so I just have to make my own. First is the oven. I brought a cheap one from Amazon. Well, it's cheap, but already better than the one I has in my kitchen. Then I start working on the controller. Originally I was plan
  10. @@PTB, Yeah this screen is great. It is strange that I just use the same (195,1859) range as the original lib y axis range for the x axis, and it works great, let me try the (156,1874) range tonight. And I think I just take it one step further by supporting the touch with all 4 screen orientation. BTW, here is what I used the screen with...... So many threads about making the MSP430 reflow oven kit, but almost none of them available for purchase, so I just got to make my own.
  11. May be the energia lib I got is an order version, as it doesn't include the setOrientation function, and that's why I added myself, plus making the getTouch() function aware of the orientation setting. For the "Y axis inverted", it just means when you touch the top, the Y result from getTouch() call is LCD_HEIGHT, and 0 when you touch the bottom (0,0 at bottom left corner). I tried both the energia lib, and the CCS one from Username, and both yield the same result. So it is very likely the v4 board got that part changed.
  12. OK, I made some change to the Energia lib to get my v4 board work as what I want. Not sure what's the best way to get the lib updated, but here is what I changed, and may be someone more experienced on make lib can include that to the lib. LCD22_Touch.h add the following: // orientation #define ORIENTATION_VERTICAL 0 #define ORIENTATION_HORIZONTAL 1 #define ORIENTATION_VERTICAL_ROTATED 2 #define ORIENTATION_HORIZONTAL_ROTATED 3 class LCD22_Touch { public: void clear(uint8_t x1, uint8_t y1, uint8_t w, uint8_t h); } LCD22_Touch.cpp add/change the following void LCD22_Touch::s
  13. So the Inverted Y is by design? If so I think I can just change the program to invert the Y value and make it work. Thanks. Edit: Yup, the touch work wonderful after I changed the Y axis mapping from (y0, 195, 1859, LCD_HEIGHT, 0) to (y0, 195, 1859, 0, LCD_HEIGHT); BTW, the X mapping seems a little bit off with the (311, 1632) input, but changed it to (195, 1859) sames as the values used for Y and it work perfectly. So, the touch input actually is a square instead of a rectangle? That's strange.
  14. Looking for some help..... I just brought two 2.2 Touch LCD (marked was v4) from Tindie, and the display is great, but somehow the touch part is not quite working right. I tried the CCS hrd_spi_max posted by username, and the energia LCD22_Touch by RobG. X axis reading seems ok, but both got the Y axis reading screwed up. The Energia one seems got the Y upside down, and the hrd_spi_max just keep saying the Y is 7, with some random reading occasionally. Did I do something wrong? And I'm using 2553 Launchpad.
  • Create New...