Member | Action | Date |
---|---|---|
![]() |
Replied
to
I2C software fault
Once you get a result that isn't i2cTransferInProgress or i2cTransferDone, there is no point continuing to call I2C_Transfer. This will exit when appropriate:
Have you tried a simple I2C_FLAG_WRITE_READ ? Also, a simple logic analyzer on the I2C bus can help find issues. |
Jul 04 2019, 1:16 AM |
![]() |
Replied
to
Flat Energy Profile Line Custom BGM Board?
If you are able to debug the board, use the Pause buttton in the debugger and see where it is at.
Show more
|
Jun 29 2019, 6:19 PM |
![]() |
Replied
to
Question regarding custom BGM121 PCB
On my custom BGM121 board, mine differs from yours: 1. Ground plane/pours go to the edge of the PCB (ie. upper on right). 2. Pin 54 is connected to GND on the top layer also. 3. RF pins are connected directly (rather than through 0 ohm/solder bridge) 4. GND stitching to the right of pad 56 5. Trace between pads 55 and 56 is normal (narrower). As the documentation says, "Verify the GND connections for the antenna pads for top layer". I don't use any via-in-pads; just put the vias close to the GND pins. (I have eight GND vias underneath, and none in pads) Martin |
Jun 25 2019, 4:17 PM |
![]() |
Replied
to
I2C software communication error -5
You should post your initialization and transfer code so we can understand see exactly what is being done.
Show more
|
Jun 19 2019, 6:16 PM |
![]() |
Replied
to
Trouble programming BGM111 on custom board using WSTK
Did you remove the board (if any) from the WSTK socket? It will draw power from VTARGET (whatever the switch position). Your external 3.0V supply may also interfere with the 3.3V that AEM mode supplies to VTARGET. (Presumably you have also added a common ground between the external supply and the WSTK.) |
Jun 19 2019, 6:03 PM |
![]() |
Updated
to
I2C Undefined behavior - BGM13P32
(You are correct; I'm a novice when it comes to using the registers directly...) Do you realize you are doing I2C_TransferInit twice?
|
May 24 2019, 4:56 AM |
![]() |
Replied
to
I2C Undefined behavior - BGM13P32
(You are correct; I'm a novice when it comes to using the registers directly...) Do you realize you are doing I2C_TransferInit twice?
|
May 24 2019, 4:55 AM |
![]() |
Replied
to
I2C Undefined behavior - BGM13P32
This is from the EFR32xG1 reference:
I don't see an ACK or NACK after you read RXDATA. Is this done in the tx_callback() ? Even if it is, an ACK/NACK is necessary if a write flag is received. |
May 24 2019, 12:11 AM |
![]() |
Updated
to
I2C Undefined behavior - BGM13P32
Shouldn't this be (since you are not sending any bytes after the address?)
Another post using I2C0 as a slave recommends setting the slave mask:
|
May 23 2019, 4:22 PM |
![]() |
Replied
to
I2C Undefined behavior - BGM13P32
Shouldn't this be (since you are not sending any bytes after the address?)
(Also, you may want to consider using the I2C_* functions for the slave as well.) Another post using I2C0 as a slave recommends setting the slave mask:
|
May 23 2019, 4:14 PM |