update problem log
This commit is contained in:
parent
66fe322b60
commit
d021889911
|
@ -14,6 +14,8 @@ Several things could be the cause of it:
|
||||||
|
|
||||||
After modifying the oximeter2_init function and changing the EXAMPLE_I2C_MASTER's MSDAT value to 0x46(the correct value), the value goes back to the previous wrong value after `I2C_MasterTransferNonBlocking` in `i2c_master_write`.
|
After modifying the oximeter2_init function and changing the EXAMPLE_I2C_MASTER's MSDAT value to 0x46(the correct value), the value goes back to the previous wrong value after `I2C_MasterTransferNonBlocking` in `i2c_master_write`.
|
||||||
|
|
||||||
|
To be more precise, 0x46 is changed to 200 after `I2C_EnableInterrupts(base, (uint32_t)kI2C_MasterIrqFlags)` in function `I2C_MasterTransferNonBlocking`.
|
||||||
|
|
||||||
Another observation is that the value `final_result` read in function oximeter2_logs_results is always 92, regardless if the click sensor oximeter2 is connected to the board or not.
|
Another observation is that the value `final_result` read in function oximeter2_logs_results is always 92, regardless if the click sensor oximeter2 is connected to the board or not.
|
||||||
|
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue