Jump to content
43oh

LiviuM

Members
  • Content Count

    91
  • Joined

  • Last visited

  • Days Won

    13

Everything posted by LiviuM

  1. Hi, it seems the file energia-1.6.10E18/hardware/tools/msp430/msp430/include/msp430f5529.h has a problem in the USB definition part. I don't know exactly what for a problem, but I was able to compile the above mentioned sketch after commenting out the USB part in msp430f5529.h (between rows ~3430 and ~4227). Maybe it helps you. Regards, Liviu
  2. Hi, which board are you using? I've tested now the "PFatFsFileTest" (library) example and it compiles for the launchpads installed by default by Energia (+TivaC), except MSP-EXP430G5529LP. Regards, Liviu
  3. Hi Spineless, I think you should install it as a library. Liviu
  4. You can try to compensate the diode voltage drop by putting another (series) diode (same type as the protection one) between the GND pin of the 3.3 V LDO and the GND of your circuit board. In this way you will raise the LDO's reference with the same amount you loose on the protection diode.
  5. Sometimes is better to wait some time.
  6. Hi Chris, maybe the installation instructions for CCS under Linux will help? The part I'm meaning is: Regards, Liviu
  7. Hi Robert, Just for the record, is working for me under OpenSuse Leap (64 bit) with TM4C1294XL (Tivac). Installing the TM4C1294XL board just worked. No extensive tests done, just loaded a couple of library examples (Blink and ASCIITable), compiled, programmed in the LP and checked they are working. And are. I have the filling it starts faster than Energia 17. Thanks for your work, Liviu
  8. Hi spirilis, in the attachment are the rules I'm using with my OpenSuse (Leap). I think tivac rules are twice, not sure which one is the good one, maybe you can find the right one. I'm using a tivac TM4C129 and a 430G1 Launchpads as normal user (member of dialout group). Hope it helps a little, Liviu energiaUdevRules.zip
  9. Hello, the EEPROM library comming with Energia doesn't work or me neither, but after some changes I've been able to successfully write and read the EEPROM on my TM4C1294. As stated on e2e forum, the EEPROM should be enabled like any peripheral. I've put the initialization code from the e2e page in a new EEPROM methode: void EEPROMClass::init(void) { SysCtlPeripheralEnable(SYSCTL_PERIPH_EEPROM0); //#include <driverlib/sysctl.h> also necessary EEPROMInit(); } More than that, the ROM functions in driverlib don't work, but the "non ROM" ones do => I've changed the library t
  10. Hello Grant, For the lm4f (TIVAC), Energia.h (../energia/hardware/lm4f/cores/lm4f/) has the following defines: #if defined(__TM4C129XNCZAD__) #define TARGET_IS_SNOWFLAKE_RA0 #define PART_TM4C129XNCZAD #elif defined(__TM4C1294NCPDT__) #define TARGET_IS_SNOWFLAKE_RA0 #define PART_TM4C1294NCPDT #elif defined(__LM4F120H5QR__) || defined(__TM4C123GH6PM__) #define TARGET_IS_BLIZZARD_RB1 #define PART_TM4C1233H6PM #define PART_LM4F120H5QR #else #error "**** No PART defined or unsupported PART ****" #endif Maybe you can use some of these defines? Regards, Liviu
  11. Hello, Unfortunattely I can't help you any furter. All I've done with this library was to connect a card to my Launchpad and make some communication tests. But in my oppinion your plan has big chances to work. Success, Liviu
  12. There are some limitation in using the write function. Calin has listed them in the post 4. Impossibility to change the size of the file is one of them.
  13. PFatFS uses the 8.3 naming convention.That means, a longer name will be "truncated" to 8 characters. In the case of a file with a name as you used ("SD card test.txt"), PFatFS shows me it as "SDCARD~1.TXT". Maybe an ideea will be to start keeping just the directory listing part from the test sketch, to see if you have communication and just the name is wrong, or you don't have communication at all. /*-----------------------------------------------------------------------*/ /* Program Main */ /*-----------------------------------------
  14. I was looking a little more and I think the mistake is in the documentation (or in the way I'm reading it). Sorry for the false report.
  15. Hello all, I think I found a mistake in the CC3200 Launchpad pin map (pins_energia.h). In the file I have (Energia 0101E0013), the push-button 1 is defined as Pin 3 static const uint8_t PUSH1 = 3; but from the map on the energia.nu it should be on the Pin 4 static const uint8_t PUSH1 = 4; Regards,Liviu PS Sorry if this issue was already reported, I've found nothing on the github list.
×
×
  • Create New...