yul
/
uni_d_ete_log_2022
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

update problem log

This commit is contained in:
yul 2022-09-06 19:55:30 +02:00
parent d021889911
commit 1cfdf37ff5
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -12,13 +12,17 @@ Several things could be the cause of it:
- `extern` not done properly maybe? maybe I should use `static`?
- `EXAMPLE_I2C_MASTER` incorrect
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 MSTDAT 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.
---
The I2C_MasterTransferNonBlocking in function i2c_master_write_then_read would return kStatus_I2C_Busy because the transaction is in progress. This is related to the problem of being stuck in `while(!g_MasterCompletionFlag)` (for the moment this while loop is commented out).
# 2022-09-05
##### yu-capteurs branch in function "oximeter2_read_data" optimisation