cde 334 Posted October 25, 2012 Share Posted October 25, 2012 Trying to see if anyone has had the same issue. I tried porting over my old i2c-explorer code I made for the g2231, over to the g2452 (because it has USI, which I coded the i2c for). It uses NJ's Uart code too. Both are using the default 1mhz calibration. Only one compile error as is, regarding TimerA0_Vector. The g2452 has a slightly different timer (A3 vs A2), and the header file doesn't have the alternative name define. Based on the g2231 header, TimerA0_Vector is also Timer_A0_Vector, a name trivial change in the code. Also changed the include to point to the right msp430 header. Compiled, downloaded, tried to use it. The serial console was really slow, and kept giving back errors (typed a character, and sometimes it would give back a random character, or it would ignore input). The i2c code would sometimes just give all nacks (no acknowledgement, no response from slave), or not work at all. [natch, there is a hardware errata that might explain this, USI4, my really slow clocked i2c might be triggering that, but that doesn't explain the uart issues] I thought it was the new launchpad, maybe I did a crappy job soldering in the crystal (or not disable it) or screwed up adding the 5v/usb testpoint pins, but I pulled the chip onto the working older launchpad that I confirmed was working with the same code (including the vector name change) on the g2231. The family guide places these two as nearly identical, except for number of pins and code space/ram. Any ideas? Has anyone tried NJ's uart code on the g2452 without issue? Maybe I just fried the chip somehow? Or did I miss something in porting the code over, since it didn't error out, and the implementation did worked, just badly. I'll try with fresh one tomorrow. Quote Link to post Share on other sites
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.