Jump to content

Mk_

Members
  • Content Count

    12
  • Joined

  • Last visited

  1. Hi Trey, I already tried connecting this board to another computer, and the problem still. (leds wont blink like they used to do before). Even changing the usb port. (I only had not a chance to run the JTAG test, since I don't have CCS installed with C2000 targets at work) On the PC side everything seems Ok, I use usb to many other things (including msp-launchpad, stellaris-launchpad and many other boards I have). Anyway, this board was really useful for me. I made a control's project, presented it (at class) and then the board got bad. (Lucky me!) I wanted to get it working again, but now my hope is gone... but if you want to make further analysis and try to discover what may have happend, just PM me your address and I can ship you the board. Thanks
  2. Openned another thread on Ti's forum to see if anyone else had a similar problem.. (I know Trey is from TI, but maye others can help too ) http://e2e.ti.com/support/microcontrollers/tms320c2000_32-bit_real-time_mcus/f/171/t/227620.aspx
  3. I've also done another thing.. I took the schematics to find some "known voltage" points and measured them. USBVcc = 4.68 V FTDI_3v3 = 3.27 V FTDI_1v8 = 1.75 V +5V = 4.3 V +3v3 = 3.2 V
  4. Hi Trey, Yes, all of them were always in the UP position. (after the problem i tried all possible configurations, all of them giving the same result) The target is being powered by usb, so the jumpers are connected. Yes, i was able to connect and program it many times. And yesterday (righ after posting here) I tried 2 more things: 1. Reinstall drivers on windows 2. Reprogram FT2232H EEPROM (I made a dump and then reprogrammed using files provided on TI's wiki) None of them recovered it..
  5. I was able to do a JTAG scan test.. here are the results: [start] Execute the command: %ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity [Result] -----[Print the reset-command software log-file]----------------------------- This utility has selected a 100- or 510-class product. This utility will load the adapter 'jioserdesusb.dll'. The library build date was 'Dec 19 2011'. The library build time was '21:32:12'. The library package version is '5.0.569.0'. The library component version is '35.34.39.0'. The controller does not use a programmable FPGA. The controller has a version number of '4' (0x00000004). The controller has an insertion length of '0' (0x00000000). This utility will now attempt to reset the controller. This utility has successfully reset the controller. -----[Print the reset-command hardware log-file]----------------------------- The scan-path will be reset by toggling the JTAG TRST signal. The controller is the FTDI FT2232 with USB interface. The link from controller to target is direct (without cable). The software is configured for FTDI FT2232 features. The controller cannot monitor the value on the EMU[0] pin. The controller cannot monitor the value on the EMU[1] pin. The controller cannot control the timing on output pins. The controller cannot control the timing on input pins. The scan-path link-delay has been set to exactly '0' (0x0000). -----[The log-file for the JTAG TCLK output generated from the PLL]---------- There is no hardware for programming the JTAG TCLK frequency. -----[Measure the source and frequency of the final JTAG TCLKR input]-------- There is no hardware for measuring the JTAG TCLK frequency. -----[Perform the standard path-length test on the JTAG IR and DR]----------- This path-length test uses blocks of 512 32-bit words. The test for the JTAG IR instruction path-length succeeded. The JTAG IR instruction path-length is 0 bits. The test for the JTAG DR bypass path-length succeeded. The JTAG DR bypass path-length is 0 bits. -----[Perform the Integrity scan-test on the JTAG IR]------------------------ This test will use blocks of 512 32-bit words. This test will be applied just once. Do a test using 0xFFFFFFFF. Scan tests: 1, skipped: 0, failed: 0 Do a test using 0x00000000. Scan tests: 2, skipped: 0, failed: 0 Do a test using 0xFE03E0E2. Test 3 Word 0: scanned out 0xFE03E0E2 and scanned in 0xFC03C0C0. Test 3 Word 1: scanned out 0xFE03E0E2 and scanned in 0xFC03C0C0. Test 3 Word 2: scanned out 0xFE03E0E2 and scanned in 0xFC03C0C0. Test 3 Word 3: scanned out 0xFE03E0E2 and scanned in 0xFC03C0C0. Test 3 Word 4: scanned out 0xFE03E0E2 and scanned in 0xFC03C0C0. Test 3 Word 5: scanned out 0xFE03E0E2 and scanned in 0xFC03C0C0. Test 3 Word 6: scanned out 0xFE03E0E2 and scanned in 0xFC03C0C0. Test 3 Word 7: scanned out 0xFE03E0E2 and scanned in 0xFC03C0C0. The details of the first 8 errors have been provided. The utility will now report only the count of failed tests. Scan tests: 3, skipped: 0, failed: 1 Do a test using 0x01FC1F1D. Scan tests: 4, skipped: 0, failed: 2 Do a test using 0x5533CCAA. Scan tests: 5, skipped: 0, failed: 3 Do a test using 0xAACC3355. Scan tests: 6, skipped: 0, failed: 4 Some of the values were corrupted - 66.7 percent. The JTAG IR Integrity scan-test has failed. -----[Perform the Integrity scan-test on the JTAG DR]------------------------ This test will use blocks of 512 32-bit words. This test will be applied just once. Do a test using 0xFFFFFFFF. Scan tests: 1, skipped: 0, failed: 0 Do a test using 0x00000000. Scan tests: 2, skipped: 0, failed: 0 Do a test using 0xFE03E0E2. Test 3 Word 0: scanned out 0xFE03E0E2 and scanned in 0xFC03C0C0. Test 3 Word 1: scanned out 0xFE03E0E2 and scanned in 0xFC03C0C0. Test 3 Word 2: scanned out 0xFE03E0E2 and scanned in 0xFC03C0C0. Test 3 Word 3: scanned out 0xFE03E0E2 and scanned in 0xFC03C0C0. Test 3 Word 4: scanned out 0xFE03E0E2 and scanned in 0xFC03C0C0. Test 3 Word 5: scanned out 0xFE03E0E2 and scanned in 0xFC03C0C0. Test 3 Word 6: scanned out 0xFE03E0E2 and scanned in 0xFC03C0C0. Test 3 Word 7: scanned out 0xFE03E0E2 and scanned in 0xFC03C0C0. The details of the first 8 errors have been provided. The utility will now report only the count of failed tests. Scan tests: 3, skipped: 0, failed: 1 Do a test using 0x01FC1F1D. Scan tests: 4, skipped: 0, failed: 2 Do a test using 0x5533CCAA. Scan tests: 5, skipped: 0, failed: 3 Do a test using 0xAACC3355. Scan tests: 6, skipped: 0, failed: 4 Some of the values were corrupted - 66.7 percent. The JTAG DR Integrity scan-test has failed. [End]
  6. Hi everyone, I have a C2k-Launchpad and was using it to run a program generated from simulink. To do so, I was using CCS4, connecting to the target, downloading the code and running it. Today, while the code was running, code composer showed a message abou the connection being lost, I was a little distracted and just closed the message and tried to connect again. Since then I'm receiving the following message: And if I retry, it changes to: Although it shows up in windows device manager: I don't know what may have happend, and googling around I could not find a way to get it working again. Actually I don't even know if this is a Target or Emulator(XDS) problem.. Does anyone had a similar problem? Is there anything I can do or the board is useless forever? Thank you!
  7. Nice! it shows how to define a "named" memory region, and then how to place a custom defined section there!
  8. SirZusa: Thanks for point this out. I already looked another code that i've found searching ti's wiki, and it does something similar (setting a pointer anywere and writing to it), and it includes the code for the MPU too! oPossum: For sure! I've looked forward on it, and checked slau132f (v4.0 compiler's optimization guide). There in the Section 5.9.21 it talks about a pragma "set_data_section". I've tested it, and it does exactly what you said. With this code: // outside of main... like a "global" variable. #pragma SET_DATA_SECTION (".mydata") unsigned char teste[0x2800]; // 10k #pragma SET_DATA_SECTION () ... // inside of main, only to avoid compiler's optimization int count = 0; for(count = 0; count < 0x2800; count++) { teste[count] = rand(); } I get this linker output (map file) .mydata 0 0000c5e2 00002800 UNINITIALIZED 0000c5e2 00002800 blink.obj (.mydata) The funny thing about all of this is that i already had the FRAM board, and never thought about using it for this.. :!!!:
  9. SirZusa: First i will try with 8bit samples to be easy to send/receive without much effort, but if it shows up to be losing precision, i will then change to more bits. JWoodrell: Since i dont need this really big memory, i will not try the SD card by now. But it will definitly goes to my to do list! It would be nice to have a sort of file system, to do things like open/read/write/close text files, instead of just write bytes to the memory itself. I was looking at the FR57xx user guide (slau272a), and to do this "data storage" in the fram seemed to be as easy as declare a unsigned char[] big enough and write every sample there (and the linker would take care of its placement).. Is that right?
  10. Thanks SirZusa My guess is that 1kSample/s for 10sec will be fine (10kSamples). (I will setup some parameters, run it and grab data for 10sec, then save this data, setup another parameters and so on..). I'll take a look at the FRAM!
  11. Hi all, I want to use the launchpad to build a DC motor position control system (for college). I want to use one channel from the adc (to read a potentiometer) and one pwm (to control the speed of the motor). As the "first step", i would like to only grab data from the adc with a fixed pwm, so to know the behavior of the motor. Since the backchannel UART is limited to 9600 baud rate, i came up with 2 ideas of getting this data: 1 - Use the HW uart (from G2553 for eg.) and a FTDI (or any other Serial->USB). 2 - Use one or more SPI EEPROM chips to save this data, and send them "offline" to the PC, using the 9600 baud. Does anyone know a better (or just simpler) way of getting this data out of the launchpad? I already have a working code, were when you send a character 'c' from the pc, the adc makes one acquisition and send it back through the uart, but i cannot achieve much high rates. Thanks in advance,
  12. Mk_

    Hi

    Hi, I am from Curitiba - Brazil, student of EE, being working with some MCUs in the last 3 years, from 8051 to ARM. had a little touch with MSPs when TI released ez430-CC2500 kit, and now again with launchpad. Recently I joined ti-launchpad list on googlegroups too. Hope I can help others with my knowledge, and learn a lot from them! Regards, Mikhail
×
×
  • Create New...