Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by LiviuM

  1. Hi Curtis, never done this, but I suppose you can generate the i2c behavior by switching the pins between input (with pull-up) for logic high and output low for logic low. Cheers, Liviu
  2. Hello Curtis, is this the file I posted some time ago, or you've made some changes? Wit other words, can I keep my file, or should I update it? Thanks, Liviu
  3. Hi @@fritzk9, I wouldn't give up so fast. Your board has some buttons (BSL) I don't know from my boards. Maybe reading the user manual (Ch. 2.2.2 & 2.2.3) will helps you to go further? Good luck, Liviu
  4. Hm, it seems to me that your Launchpad is seen as HID & mass storage device, not as a CDC/Serial one. I don't know how it works, sorry.
  5. Hi @@fritzk9, regarding your Linux tries, have you installed and "activated" the udev rules for your board as explained on energia.nu? What shows the dmesg after connecting the board to the Linux box? If I connect my Launchpad I see [327268.534687] usb 1-2: new full-speed USB device number 3 using xhci_hcd [327268.741651] usb 1-2: New USB device found, idVendor=0451, idProduct=f432 [327268.741654] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [327268.741655] usb 1-2: Product: Texas Instruments MSP-FET430UIF [327268.741656] usb 1-2: Manufacturer: Texas Instruments [32726
  6. Hello Curtis, in my opinion, your pins file has a problem with the (hardware) i2c pins. In my opinion, the TWISDA should be == with TWISDA0 and TWISCL should be == with TWISCL0. In your file there are defined as: static const uint8_t TWISDA = 22; /* P1.7 */ static const uint8_t TWISCL = 21; /* P1.6 */ static const uint8_t TWISDA0 = 23; /* P1.7 */ static const uint8_t TWISCL0 = 22; /* P1.6 */ I think they should be static const uint8_t TWISDA = 22; /* P1.7 */ static const uint8_t TWISCL = 21; /* P1.6 */ static const uint8_t TWISDA0 = 22; /* P1.7 */ static const uint8_t TWISC
  7. The selection of included LP, starting with the "worst" one and bringing the "good" ones few days later, disappointed me. So, I bought an (almost) useless LP *) to acquire an (almost) useless CCS license. Useless for me, as I already had one, no need for a second.
  8. Hi Curtis, looking in one of your previous posts to the pin map for the 32 pins devices, there are some defines that maybe are wrong? I mean, at the beginning of the map you have static const uint8_t TWISDA = 22; /* P1.6 */ static const uint8_t TWISCL = 21; /* P1.7 */ and later: #define PIN_SCL P1_3 #define PIN_SDA P3_1 Are you sure the later defines are OK?
  9. They used the "CCS promotion" to sell some 10$ Launchpads...
  10. Hi Bob, If there it is a current flowing through the resistor (to be throttled), then Vin != Vout (Vin = Vout + I*R). A resistor (+ the ESD protection diode) can be seen as the simplest "level adapting" structure, if the resistor is large enough to keep the current in the Pin's specification. As for the actual case, with a 3.3V output driving a 5V CMOS input, as the input is practically floating, I don't see any reason for a damage to the output. In the worst case, the 3.3V wouldn't be enough to switch the input, if it is a Schmitt trigger input, for example (the most Schmitt triggers I
  11. The license check is missing already in the last Linux version of CCS 6 (
  12. You should add your board it using the Boards Manager: Tools -> Board -> Boards Manager. After, the board data will be in energia15 folder, as in my example above.
  13. Actually you can copy each folder that interest you in the libraries folder for your board. On my linux machine and for my board (TM4C1294), the libraries directory is located under /home/liviu/.energia15/packages/energia/hardware/tivac/1.0.2/libraries/ Putting there a new folder with a .cpp and a .h files inside, is enough to "create" a new library. If you put inside an examples sub-folder, containing example sketches, you'll have also the examples in Energia -> File -> Examples. HTH, Liviu
  14. Strange, I was thinking the English is my week point... What I tried to say is, if you look the diagram at page 4 in the Microchips AN, you'll see that every time the bit value changes (0->1 or 1->0) you don't have a transition at the end of bit, but if the bit repeats, you have a transition in the middle of the bit (the active one) and one transition at the end of bit. But looking now to the same diagram, I see now that if you can detect the start edge (first H->L transition), there are maybe better criteria to decode the bits.
  15. For Manchester decoding (not on micro controllers, on other equipment), I've measured the time distance between consecutive edges. If the distance is half of the bit length, the last bit is repeated, if the distance is the bit length, the last bit is inverted. If you use in interrupt to detect the falling edge and to start a timer, and as you know the first (start) bit is a zero, detecting the next bits shouldn't be to difficult.
  16. Hi Rick, Thanks for the correction, it seems I have an older version (1.0.2) for the tivac package. But the exactly name is not so important, it was just an example. Idea remains - one can use the board name from the boards.txt file in #ifdef tests. Best regards, Liviu
  17. Hi, you can use the for sure the uC name: #if defined(__TM4C1294NCPDT__) /*tivac LM4C1294 writes 4 locations at once;*/ In older Arduino IDE's I've used the board name as well, but not sure how the newer IDEs work: #if defined(ARDUINO_AVR_UNO) || defined(ARDUINO_AVR_NANO) Regards, Liviu LE Because of the "command line defines" (-D compiling option), I think in the last Energia (1.6.10E18) you can use "ENERGIA_board-name", with the "board-name" found in the boards.txt file. For my TivaC TM41294XL, the boards.txt shows: EK-TM4C1294XL.build.board=EK-TM4C1294XL and the compile
  18. Hi, in the data sheets of some PIC uC (PIC18F13K50, for example), in the description of the EUSART synchronous mode, there is specified: Maybe it is what you are looking for? Regards, Liviu
  19. Maybe the solution in this topic will help you as well?
  20. Hi, on the energia.nu you find the documentation of your board, including the pin assignment. As you can see, your board has two SPI "modules" - 0, the default one (pins 7, 8, 14, 15) and module 1 (pins 9, 10, 33, 34). From the SPI library's documentation, you can see how to change the used module (setModule() function) and how to use the SPI interface. Rergards, Liviu
  21. Hi, Glad to hear it's working for you. Since the changed library seems to work (I've also updated the example and replaced the library in the post above), maybe Calin or a moderator can update the download on the first post of the topic. Liviu
  22. Try to locate (I suppose even Macs have a search program ) the PFatFs directory and delete it. Unzip and put the content of the changed library in place of it.
  23. I've changed the DIR with FSDIR in the PFatFs library; I'm attaching the changed library here. Just replace the one on your PC with the attached one. On my PC I've put it in ../energia-1.6.10E18/libraries/PFatFs/ You should probably change your sketches too. Regards, Liviu EDIT: updated the library (fixed the examples too). PFatFs.zip
  24. Hi, fount it. It seems, the DIR definition in energia-1.6.10E18/hardware/tools/msp430/msp430/include/msp430f5529.h /* USBCTL Control Bits */ #define DIR (0x0001) /* USB - Data Response Bit */ conflicts with the DIR in the energia-1.6.10E18/libraries/PFatFs/utility/pff.h: /* Directory object structure */ typedef struct { WORD index; /* Current read/write index number */ BYTE* fn; /* Pointer to the SFN (in/out) {file[8],ext[3],status[1]} */ CLUST sclust; /* Table start cluster (0:Static table) */ CLUST clust; /* Current cluster */ DWORD sect; /* Current sector */
  • Create New...