Bosch Shared
- Top Results
See all results
- About punitjain8695
- About punitjain8695
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
About punitjain8695
since
03-24-2021
06-01-2021
punitjain8695
Member
10
Posts
0
Likes
1
Solution
05-18-2021
10:56 AM
625 us is fine for me. The problem right now is, I want it to happen. I'm checking the interrupts on an oscilloscope right now, and I'm not understanding why it's not happening. I'll take a look at the FIFO example. I want to do very fixed rate, synchronous measurements along with some other sensors in the system, and thus, I think maybe reading individual samples is better than the FIFO thing. Edit 1: Can you please let me know why I'm not getting data ready interrupt at 625us even when I configure it to be. Also, it's staying at 5ms interval no matter what ODR I program it for. even lower ODR like 25Hz. Edit 2: Okay, I figured out the problem with the configuration bits. I'm now able to get interrupts properly. I still want to know if I could actually do it using the FIFO, but still have some sort of time stamps, and synchronize with the other sensors in time domain. I checked it with the microcontroller only reading the values without any interruption. The values are changing only after 5ms. I don't think the BMI270 has been configured correctly.
... View more
05-17-2021
08:40 PM
Hello I'm using a BMI270 shuttle board, and I want to get the accelerometer and gyroscope values at the maximum ODR possible, that is 1600Hz. I'm using the board via the SPI bus, using the BMI270 API https://github.com/BoschSensortec/BMI270-Sensor-API on github. I have set the registers for PWR_CTRL, ACC_CONF, GYR CONF and PWR_CONF for performance mode as said on page 20 of the datasheet. I have also setup a data ready interrupt on the INT1 pin, by modifying the registers: INT_MAP_DATA, INT_IO_CTRL, and INT_LATCH. The interrupts that I'm receiving on the microcontroller are always at 5ms interval (200 Hz) irrespective of the acc_odr values set in the ACC_CONF register for the accelerometer and correspondingly for gyroscope. Am I missing something? or some step. Please guide. P.S: I'm using TI's TM4C1294NCPDT based eval board.
... View more
04-21-2021
06:31 PM
Hi, Really thanks for all the help you've been. I'm sure I'll need more help on the way, but this seems to be working now. I played around with the code a lot in the past couple of days and then searched about this kind of weird behavior (Code getting stuck at a position that it was able to run through, with the only difference being that there is a little more code or little more variable declarations. ) I found out that it was due to the very heavy hierarchy of functions being present in the BMI270_API and a relatively small stack space (512 bytes) being allocated. Both of these combined, basically resulted in stack overflow, which then resulted in Fault_ISR being called. a reference link (TI's E2E forum): https://e2e.ti.com/support/microcontrollers/other/f/other-microcontrollers-forum/430818/launchpad-s-strange-faultisr I increased the stack space to 1024 bytes from 512 bytes, and the program runs fine. The conversion has some issues, but I was not interested in the conversion anyway. Again, lots of thanks for helping me through this. I've left the link for the reference above, just in case someone else has similar issues again in the future. Thanks and Regards, Punit Jain
... View more
04-19-2021
03:59 PM
I checked further, it happens that, whenever I assign anything related to "struct bmi2_sensor_data sensor_data", The code compiles, but results in runtime error and ends up in Fault_ISR while loop. even a part of the code which is simple as this: // Assign accel and gyro sensor.
sensor_data[ACCEL].type = BMI2_ACCEL;
sensor_data[GYRO].type = BMI2_GYRO; throws an error. The code is able to read the chip ID, however. but fails in the bmi270_init(). My guess is, this structure contains a uint8_t type variable and a union. As in C, union's size will be limited to the max of the sized of it's elements, it is not able to work properly. Should I convert all of the unions to struct types?
... View more
04-18-2021
06:02 PM
I tried implementing the whole startup sequence using bmi270_init(); I figured out that the error was, that I was not clearing the RX buffers after transmitting in legacy mode. But that is taken care of now. As of now, the bmi270_init runs fine (the return for that function is BMI_OK (0x00)). and the register at 0x21, has it's LSB as 1, which means that the initialization has been successful. But when I try to run this: bmi270_get_sensor_config(), it gets stuck in the first SPI read function. From bmi270_get_sensor_config(), it goes to bmi2_get_sensor_config(), and then to get_accel_config() and then to bmi2_get_regs(), where it terminates with an error to Fault dead loop. I tried debugging the error, and found out that the size of the data space allocated for the read function is not enough for the read to be done. Edit: I checked further, the size of the array is sufficient. The issue is something different, it seems. It is getting stuck when reading two bytes from Register 0x40, so, 0x40 and 0x41. I tried reading those two registers directly by using the bmi2_get_regs() function, and it is reading the registers properly. The values are @0x40: 0xa8; @0x41: 0x02;
... View more
Still looking for something?
- Top Results
See all results