From 1cfdf37ff5357b327d85ce8b9b36b4eea2dc4586 Mon Sep 17 00:00:00 2001 From: yul Date: Tue, 6 Sep 2022 19:55:30 +0200 Subject: [PATCH] update problem log --- README.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 6cac20e..abb4784 100644 --- a/README.md +++ b/README.md @@ -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