update problem log
This commit is contained in:
		@@ -1,3 +1,6 @@
 | 
				
			|||||||
 | 
					# 2022-09-07
 | 
				
			||||||
 | 
					[ ] Fix the callback and the calling of it on oximeter and have a reading that is not 92.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
# 2022-09-06
 | 
					# 2022-09-06
 | 
				
			||||||
 | 
					
 | 
				
			||||||
**Problem/Confusion:**
 | 
					**Problem/Confusion:**
 | 
				
			||||||
@@ -23,6 +26,9 @@ Another observation is that the value `final_result` read in function oximeter2_
 | 
				
			|||||||
 | 
					
 | 
				
			||||||
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).
 | 
					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).
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					---
 | 
				
			||||||
 | 
					Task for tomorrow: figure out why oximeter2.c callback function is not entered.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
# 2022-09-05
 | 
					# 2022-09-05
 | 
				
			||||||
 | 
					
 | 
				
			||||||
##### yu-capteurs branch in function "oximeter2_read_data" optimisation
 | 
					##### yu-capteurs branch in function "oximeter2_read_data" optimisation
 | 
				
			||||||
 
 | 
				
			|||||||
		Reference in New Issue
	
	Block a user