I2c Not working after waking from sleep

我已经探测了SCL线and there is no activity on the line after the extended sleep.

When it comes out of sleep the I2C status is 0 (disabled).
To get the I2C functional again it was not enough to do hw_i2c_enable(HW_I2C1) I had to also init the bus and set the target address.
Thus the code for the I2C periph_init is now:

=================.
hw_gpio_configure_pin（hw_gpio_port_3，hw_gpio_pin_0，输入，i2c_sda，false）;// IC21数据
hw_gpio_configure_pin(HW_GPIO_PORT_4, HW_GPIO_PIN_7, OUTPUT, I2C_SCL, false); // I2C1 CLK
hw_gpio_configure_pin(HW_GPIO_PORT_4, HW_GPIO_PIN_3, INPUT, GPIO, false); // accel irq

static const i2c_config cfg = {
.speed = hw_i2c_speed_fast，
。mode = HW_I2C_MODE_MASTER,
。addr_mode = HW_I2C_ADDRESSING_7B,
};

hw_i2c_init(HW_I2C1, &cfg);
hw_i2c_set_target_address（hw_i2c1,0x0e）;/ *出现适配器在公共汽车上只有一个I2C设备时，适配器不会设置地址？* /
hw_i2c_enable(HW_I2C1);
=================.===

它没有在示例或文档mention that these init steps needs to be done when coming out of sleep. I only discovered this from the link in the previous response.

The question is: is this initialization needed for proper behaviour after a deep sleep or is this a bug in the i2c adapter or hw_i2c code. Does the adapter update the device address even for busses with only one device.

为什么我要当广告设置TargetAddressapter is suppose to do this for me? If I don't set the address in init, then I get a value of 0x07 for all register reads from the device. Is this an artifact of only having one device on the bus.

是的，这是预期的behaviour but the observed behaviour is that I do need to do those 3 steps otherwise I2C does not respond when waking from extended sleep.

Yes I do an open. The transact call never returns as it is waiting for an I2C to complete. I replaced the transact with write and read but the behaviour I have observed has remained the same. The SDK is 1.0.8.1050.1 for the DA14681

Thanks for keeping with this. I am confused as to why I am not seeing the expected behaviour after the extended sleep.

By the way when I do a hw_i2c_get_enable_status() it returns 0 after an extended sleep unless I have the 3 unnecessary steps in the periph_init.

In the I2C_Handler() call the value for i2c->intr_cb is NULL.

我没有改变任何保留设置，但它看起来像I2C的内存（状态）在延长睡眠期间丢失。

Could there be something there that is causing this behaviour?Do note that we have replaced the 8MBit winbond with a 64MBit winbond Flash part.We have created the new appropriate header file for it.

#define proj_configoptimal_retram（0）

#if！定义（Reford_Build）&&（proj_configoptimal_retram == 1）
/* WARNING: retRAM optimizations are disabled in DEBUG builds! */
#undef proj_configOPTIMAL_RETRAM
#define proj_configoptimal_retram（0）
#elif (dg_configEXEC_MODE != MODE_IS_CACHED)
/* WARNING: retRAM optimizations are not applicable in MIRRORED mode! */
#undef proj_configOPTIMAL_RETRAM
#define proj_configoptimal_retram（0）
#endif

#if (proj_configOPTIMAL_RETRAM == 0)
#define dg_configMEM_RETENTION_MODE (0x1F)
#define dg_configSHUFFLING_MODE (0x3)

It is within a task that is woken by an interrupt. I showed the call chain to kxcjbDevRegisterGet in a previous response.

Since interrupts cannot use adapters to interact with I2C, the task has to clear the interrupt when it reads the interrupt clearing register via I2C.

Here is the interrupt handler (The clearing of the HW GPIO is done by the WKUP handler I wrote. Tasks register with WKUP to have their handler called when a certain PORT/PIN interrupt is detected.

//这个想法是，这是中断的顶部，即它向稍后的时间运行的下半部分（任务）的信号。
static void kxcjbTapEventInterrupt(void* eventData)
{
//tp_interruptEventData p_eventData = (tp_interruptEventData) eventData;
baseType_t xhigherprioritytaskwoken = pdfalse;

xTaskNotifyFromISR( accelInterruptTaskHandle, ACCEL_INTR_NOTIFY, eSetBits,
&xHigherPriorityTaskWoken);
portYIELD_FROM_ISR( xHigherPriorityTaskWoken );
返回;
}

// HERE IS THE TASK //
//the idea is that this is the bottom Half of the interrupt that is scheduled to run at a later time.

static void accelTaskHL( void *pvParameters )
{
/* define variables static to get it off the stack */
static uint8_t accelSource[2];
t_errorcode错误码;
bool st;

bool datavalid = false;
UINT32_T NotifyValue;
uint8_t data;
const TimerHandle_t accelTimer = xTimerCreate( "accelTaskTimer",
pdMS_TO_TICKS(750),
pdFALSE,
(void *)0,
accelTimerCallback);

while (1)
{
xTaskNotifyWait(0x00, ULONG_MAX, ¬ifyValue, portMAX_DELAY); // WAIT here for the next signal: Interrupt, Timeout, or control message

kxcjbDevRegisterGet(NULL, WHOAMI_ADDR, &data);// Within this function I do the ad_i2c_transact()
if (notifyValue&ACCEL_ENABLE_NOTIFY) {
g_accelState=ACCEL_STATE_0;
kxcjbInterruptEnable();
i2c_device dev = ad_i2c_open(ACCEL_KXCJB);
errCode = kxcjbBitsSet( dev, CTRL_REG1_ADDR, CTRL_REG1_PC1_EN);
assert(errCode==ERRORCODE_OK);
ad_i2c_close（dev）;

}
else if (notifyValue&ACCEL_DISABLE_NOTIFY) {
kxcjbInterruptDisable();
i2c_device dev = ad_i2c_open(ACCEL_KXCJB);
errcode = kxcjbbitleclear（dev，ctrl_reg1_addr，ctrl_reg1_pc1_en）;
assert(errCode==ERRORCODE_OK);
ad_i2c_close（dev）;

g_accelState=ACCEL_STATE_DISABLE;
}
else
{
switch (g_accelState) {
案例Accel_State_disable：
/* 没做什么 */
break;
case ACCEL_STATE_0:
if（notifyValue＆Accel_Intr_Notify）{
kxcjbInterruptSrc(NULL, &accelSource[ACCEL_STATE_0]);

/ *将处理计时器已经运行的情况，
*should not happen
* /
xTimerReset(accelTimer, 0);

g_accelState=ACCEL_STATE_1;
}
/* else we are ignoring the timer interrupt, should not happen */
break;
case ACCEL_STATE_1:

if（notifyValue＆Accel_Intr_Notify）{
kxcjbInterruptSrc(NULL, &accelSource[ACCEL_STATE_1]);
printf ("0=0x%02x\n\r1=0x%02x\n\r",accelSource[0],accelSource[1]);
fflush(stdout);
/ *测试是否在同一轴上有源中断
*as occurred in previous interrupt
* /
if（（（Accelsource [Accel_State_0]＆（int_source2_xpwu | Int_source2_xnwu））
&&(accelSource[ACCEL_STATE_1]&(INT_SOURCE2_XPWU|INT_SOURCE2_XNWU))
）||
( (accelSource[ACCEL_STATE_0]&(INT_SOURCE2_YPWU|INT_SOURCE2_YNWU))
&&(accelSource[ACCEL_STATE_1]&(INT_SOURCE2_YPWU|INT_SOURCE2_YNWU))
）||
( (accelSource[ACCEL_STATE_0]&(INT_SOURCE2_ZPWU|INT_SOURCE2_ZNWU))
&&(accelSource[ACCEL_STATE_1]&(INT_SOURCE2_ZPWU|INT_SOURCE2_ZNWU))
）
）{
xTimerStop(accelTimer, 0);
if (ACCEL_TASK_DISABLE_ON_TAP_DETECT) {
g_accelState = ACCEL_STATE_DISABLE;
kxcjbInterruptDisable();
}
else {
g_accelstate = Accel_State_0;
}

if (gfp_tapEventCb) {
gfp_tapeventcb（g_appinfo）;
}
}
else {
printf("AC:TO\n\r");
fflush(stdout);

xTimerReset(accelTimer, 0);
Accelsource [Accel_State_0] = Accelsource [Accel_State_1];
g_accelState = ACCEL_STATE_1; /* reenter the same state */
}
}
else if (notifyValue & ACCEL_TIMER_NOTIFY) {
g_accelState=ACCEL_STATE_0;
}
else {
断言（0 == 1）;
}
}
}
}
}

// Here is the code that creates the task,

uint32_t status = OS_TASK_CREATE("AccelInterruptHL", /* The text name assigned to the task, for
debug only; not used by the kernel. */
accelTaskHL, /* The System Initialization task. */
( void * ) 0, /* The parameter passed to the task. */
configMINIMAL_STACK_SIZE * OS_STACK_WORD_SIZE * 2,
/* The number of bytes to allocate to the
stack of the task. */
OS_TASK_PRIORITY_HIGHEST，/ *分配给任务的优先级。* /
accelInterruptTaskHandle ); /* The task handle */

It appears to be due to using gcc-arm-none-eabi-6-2017-q1-update ( with this tool chain I have to use the extra steps to get I2C to work).
With the provided gcc tool chain: 4_9-2015q3 the I2C works as advertised.

Thanks for your assistance and perseverance on this.
Hopefully this saves others time, knowing that the tool chain affects the documented behaviour.