Jump to content
43oh

StefanSch

Members
  • Content Count

    61
  • Joined

  • Last visited

  • Days Won

    7

StefanSch last won the day on December 9 2020

StefanSch had the most liked content!

1 Follower

About StefanSch

  • Rank
    Level 1

Recent Profile Visitors

702 profile views
  1. As far as I can remember, the G2553 has a very small serial buffer. Just try to reduce the number of byte to send, e.g. AT: Instead of Enter AT commands:
  2. G2553 has a Hardware Serial Interface, so do not use the Software implementation. Serial BTSerial..... Should work
  3. Have you removed the jumper for the Red LED, they share the some port from the MSP430 and the load of the LED is to high for I2C. Also ensure your sensor board has the pull up resistors on the I2C data lines.
  4. So it gets stuck in the function for the bioHub. How have you connected the bio sensor?
  5. do a print before this line: Wire.begin(); To ensure the code does not get stuck in this function: int result = bioHub.begin();
  6. Have you tried a simple example for the UART already? So without the Bio sensor code How have you attached the sensor? Try to dump something on the UART before accessing the bio sensor - to ensure / check that this one is not blocking the UART.
  7. Which I2C port do you use - at which pins have you attached your Gyro? Which pin do you use for the servo?
  8. If you need help you should provide some more details: Which launchpad are you using? Which components are you using and how have you connected them? Is gyro running on its own? Is servo running on its own? What step to debug the issue have you already done?
  9. A look into the Schematic resolves the mystic: The signal is not connected as R63 is marked as DNP (Do not populate)
  10. Yes, of course you can do that. Just for the Launchpad the numbering is always done on the boarder of the PCB = Pin Headers of the board, as this is the point where a typical user would connect something. If you prefer for your own board to have the device pin numbers used - you can do that. Doing the updates as you mentioned above should do that 🙂 To get the board in the GUI you need to - add a device in the variants folder - as just discussed with the update of the pins_energia.h file - add a section into the boards.txt file (located in the folder above) in a s
  11. Hi, you are right the pins_energia.h file is the correct location for that. Just let me give you one example of how the mapping works. (line numbers are based on latest released version (1.0.7) line 45 : = pin header static const uint8_t SS0 = 47; /* P4.0 */ line 216: = pin header static const uint8_t P4_0 = 47; Beginning with line 457 the mapping from the pin header to the device function is done With the function above line 505 - tells it has not Timer line 560 - tell it is on Port 4 line 615 - tell it is on Port4 but now mo
  12. Hi Berry, i am not the expert on the cc3220 as this uses RTOS functions to implement the multi threading features. In this implementation a lot of the functions are inside the RTOS library. So check following files: Board_init.c - to adopt pins for SPI, ADC, UART Board.h - to adopt pins for I2C, LEDs, SPI pins.c - maps function to board pin (not CC3220 pin) pins_energia.h - maps function to board pin (not CC3220 pin) Note: DIOxx is pin xx on CC3220 - sometimes the use of board pins and CC3220 can be confusing but needs to be handled carefully.
  13. in the board.txt file you also need to change the prefix CC3220SF-LAUNCHXL.xxxxx
  14. Hi Josef, thanks for highlighting the availability of the newer GCC version. Unfortunately i made a link to the GCC page at TI but this page did not point to the latest compiler (9.x.x) anymore but still to the 8.x.x version. I have just uploaded a new Energia elf GCC compiler version with the 9.2.0.50 compiler (Energia package 2.0.9). Stefan
  15. Thanks, for the feedback. I have already implemented the fixes based on your findings and planning for an update release of this package.
×
×
  • Create New...