Jump to content


  • Content Count

  • Joined

  • Last visited

About aBUGSworstnightmare

  • Rank
    Advanced Member
  1. Hi, the examples (all of them) compile out-of-the-box! Be shure to import sensorlib and build it (!) before you attempt to compile one of the examples that come with BOOSTXL-SENSHUB. Ensure that the latest TIVAware is installed too. Kind regards aBUGSworstnightmare
  2. Hi, seems you're missing some include files! But, I doubt that anybody will be able to help you without additional information. By the way: There's a polled I2C master driver available here in the forum (http://forum.stellarisiti.com/topic/417-i2c-with-stellaris-lm4f120h5qr-working-driver-api-example-code/ ) and, TI just released an interrupt based I2C master as part of the BOOSTXL-SENSHUB (http://www.ti.com/tool/boostxl-senshub) software package (http://www.ti.com/tool/sw-ek-tm4c123gxl). Rgds aBUGSworstnightmare
  3. Hi bluehash, Yes, I've designed it for use with the Evalbot (search E2E for 'Evalbot Design Files' to find the thread). It was the 'birth' of the C3ii idea. It uses a SIRFSTAR IV GPS which should connect to MEMS (Gyro, Mag) which allows Sensor Data fusion in the GPS. Unfortunately, Quectel has no MEMS support to date ;-( Nevertheless, this tiny GPS module (L50) is very sensitive and fast. aBUGSworstnightmare
  4. Refer here http://forum.stellarisiti.com/topic/617-boostxl-senshub-latest-booster-pack-from-ti/ for more info on the BOOSTXL-SENSHUB. aBUGSworstnightmare
  5. Hi there, just received my BOOSTXL-SENSHUB and only wanted to show you what's in the box aBUGSworstnightmare The box The boosterpack mounted on a Stellaris Launchpad I've added a GPS I've once made for use with the EVALBOT The stack from the side. The GPS uses the RF-interface connectors. They allow easy addition of I2C/UART/SPI devices
  6. Hi, don't know if you've seen this: http://www.ti.com/tool/boostxl-senshub - the Sensor-Hub Booster Pack. The hardware resembles and IMU too, but, what makes this a precious gem - is the software that comes with it: a set of functions to deal with the sensors, and a 9 axis sensor fusion code (and a nice I2C driver which uses interrupts!). Don't miss this! Will save you a lot of work! aBUGSworstnightmare
  7. Yes, shouldn't be a problem when using the same pinheaders as features on the Launchpad itself. Since I have an still unpopulated PCB lying around I will test if it is possible to solder the Launchpad directly to the C3ii INS PCB and then plug the sensor BP ontop of that. Depends on the lenght of the Launchpad pins. In every case the C3ii will not be populated with the sensors! Well, since we know have a interrupt I2C API and a good set of code to deal with the sensors itself (part of the SW-EK-TM4C123GXL - http://www.ti.com/tool/sw-ek-tm4c123gxl ) it should speed up the SW development
  8. Hi Folks, well, too bad that I haven't had the chance to participate in the TI Booster Pack Design contest! I expect I've had good chances to win a price since the guys there seems to like the idea of my C3ii INS Booster pack as they now have released a similar one: the Sensor Hub Booster Pack http://www.ti.com/tool/boostxl-senshub It's in stock at the TI eStore. So, act quickly if you want to have one! I will continue work on the C3ii INS for shure, hoping that the introduction of the TI Sensor Hub Booster Pack will speed up development. Rgds aBUGSworstnightmare
  9. Hi, I've just placed an order for two EK-TM4C123GXL at the TI eStore. No delivery date so far. aBUGSworstnightmare
  10. Hi, been away for some days and returned today, visited the TI website and: What the hell is going on there! Took me quite some time to figure out that Stellaris M4F is now Tiva! All 'old' Stellaris parts were gone (although none of them wnet into full production) and all new Tiva devices. I hope there will be a comparison chart in the NEAR future showing the relationsship Tiva product numer >-> Stellaris M4F designation. Just checked the 'Launchpad' and figured out that the Tiva™ TM4C123GH6PM Microcontroller is identical to LM4F230H5QR. Well, not bad since you now get hardware
  11. Hi, you need to register your 'ISR_I2C1_SlaveDataTx' to 'startup_ccs.c' and you need to enable the coresponding I2C interrupts (and the global interrupt) to get it fired. Refer to the Stellaris Launchpad Workshop Manual for an example on how to use interrupts. aBUGSworstnightmare
  12. Hi gwdeveloper, I'm willing to sell mine at $110 (EKS-EVALBOT --> CCS version) + shipping. It's in mint condition (assembled); I will throw in one of my GPS breakouts that I build for testing with the evalbot (look here http://e2e.ti.com/support/microcontrollers/stellaris_arm/f/471/t/132046.aspx and scroll down a little until you find the pic). If you're interested in pls send me a PM and we can discuss the details. aBUGSworstnightmare
  13. Well, don't be surprised when you'll find out that the ACC on the STM32F3 kit isn't the best one out there in the market. You should have a look at 'baseflight' when you want to stay with the STM part.
  14. Hi, this API is for I2C MASTER MODE only! You're nearly there! Again: look at this example, expand it with a useful routine (I would prefer to check TREQ-bit before each data send transfer) and you got it. Your master should do a data write first to let the slave know how much data it is requesting (Max_I2C_Tx_Size); you can skip this if you have a fixed number of bytes. But remember: You will have to adjust the code each time if your slave has to transmit less or more bytes. aBUGSworstnightmare
  15. Hi, Would be great if you share the 'interrupt' version too. I was also thinking of adding interrupt support to the API, but I will modify it for use with TI-RTOS. aBUGSworstnightmare
  • Create New...