Posts by Steffen

The FTP
transfer from efusA9X to PC via LAN doesn’t work for large files. The transfer
of files with about 30 Mbytes fails every time. The transfer of files with
about 4 Mbytes fails after some transmissions.

Test
environment:

Eval.-Kit with
efusA9X with kernel from 2016/9/17.

Connection
with PC via 1 Gbit/s network.

Windows
explorer as FTP client

10
PDF-Dateien with identical content of 3.758.922 bytes.

Test sequence:

1. The
files are copied from PC to efusA9X to directory \Temp via FTP (successfully).

2. The
files are copied back to PC sequentially.

Problem:

After some
files the transfer times out. (The count of the files that could be transmitted
before successfully varies.)

After the
failed transmission FTP, telnet and even ping do not work anymore.

Additional info:

Problems
with transmission of large files from efusA9X to PC have been observed also in
case of client server connections via .NET remoting (TCP).

The same
test sequence could be performed successfully via WLAN.

Debug log
info:

Waiting
Send Packets Detected, Busy Count 16 Pending Send 16 @ 10

0x4c00
0x4c00 0x4c00 0x4c00 0x4c00 0x4c00 0x4c00 0x4c00

0x4c00
0x4c00 0x4c00 0x4c00 0x4c00 0x4c00 0x4c00 0x6c00

====>
ENETResetEx

MpFreeQueuedSendNetBufferLists:
status=0xc001000d, list 0xb1f6b110

MpFreeQueuedSendNetBufferLists:
status=0xc001000d, list 0xb20f2420

MpFreeQueuedSendNetBufferLists:
status=0xc001000d, list 0xb20fb920

// some similar
lines deleted

MpFreeQueuedSendNetBufferLists:
status=0xc001000d, list 0xb1f6bda0

MpFreeQueuedSendNetBufferLists:
status=0xc001000d, list 0xb20f4e70

ENETFreeBusySendNetBufferLists:
ABORTED, list 0xb1f6b110

Exception
'Data Abort' (0x4): Thread-Id=0612000a(pth=a30a0000), Proc-Id=00400002(pprc=80664ae0)
'NK.EXE', VM-active=055b0012(pprc=a307cb50) 'servicesd.exe'

PC=efca480b(ndis.dll+0x0002480b)
RA=efca4495(ndis.dll+0x00024495) SP=b1dafcf8, BVA=00000000

Exception
'Raised Exception' (0x116): Thread-Id=0612000a(pth=a30a0000), Proc-Id=00400002(pprc=80664ae0)
'NK.EXE', VM-active=055b0012(pprc=a307cb50) 'servicesd.exe'

PC=effa09e3(k.coredll.dll+0x000109e3)
RA=80246a1f(kernel.dll+0x00006a1f) SP=b1daf380, BVA=ffffffff

It works now. Thank you!

(Verified with OS image based on BSP from 2016/06/23.)

It works now like expected. Thank you!

(Verified with an OS Image based on the BSP from 2016/06/23.)

Hello,

I’m worried about some entries in the debug log arising while switching WiFi power and bindings. I’m not sure whether these entries indicate serious errors or could be ignored. Can you give your estimation, please?

I’ve performed the tests with ndisconfig.exe. The registry setting for HKLM\Drivers\BuiltIn\Ethman\Popup\Popup is word:0.
The log entries are listed related to the performed transition. Some of these entries occur not on every transition.
All possible transitions in this area have been tested. Maybe you can advise which transitions are not appropriate und should not be used.

Transition from D0, Bound to D4, Bound
Command: ndisconfig power set SDIO87871 D4
Resulting log entries: None

Transition from D4, Bound to D0, Bound
Command: ndisconfig power set SDIO87871 D0
Resulting log entries:
T Wj<-75><-23><-127><-103><-123><-91><-79><-107><-111><-127><-47><-67><-127><-51><-107><-47><-127><-91><-71><-103><-55><-123><-127><-75><-67><-111><-107><-127>=% <-79><-127><-107><-55><-55><-67><-55><-127><-59><-59><-39><-35>5)<-1>

Transition from D0, Unbound to D4, Unbound
Command: ndisconfig power set SDIO87871 D4
Resulting log entries: None

Transition from D4, Unbound to D0, Unbound
Command: ndisconfig power set SDIO87871 D0
Resulting log entries:
H<-22>U<-107><-91><2>:<-107><-47>]<-91><-55><-107><-79><-107><-51><-51>%<-71><-103><-67><-127><-103><-123><-91><-79><-107><-111><-127><-63><-31><-47><-27><-63>5)<-1>
!NWUI: RefreshAvailableNetwork failed 0x32
!NWUI: RefreshWiFiInterface failed 0x32
!NWUI: GetWirelessInfo failed 0x32
!NWUI: RefreshAvailableNetwork failed 0x32
!NWUI: RefreshWiFiInterface failed 0x32
!NWUI: GetWirelessInfo failed 0x32
or
*<-118><-118><-54>e5<-11>5u<-91><-47><-115><-95>Y<-67><-79><-47><-23><-127><-59><-59><-43><-63><-75>Y<-127><-55><-107><-99>Y<-123><-79><-11><-63><-31><-47><-31><-55><-123><-59><-55>5)<-127><-87><-87><-87><-87><-87><-127><5>I5<-127>
=I§<-127><-31><-63><-63>5!<-23><-127><-87><-87><-87><-87><-87><-87><-87><-127>5)<-1>

Transition from D0, Bound to D0, Unbound
Command: ndisconfig dapter unbind SDIO87871
Resulting log entries:
*<-118><-118><-54>e5<-11>5u<-91><-47><-115><-95>Y<-67><-79><-47><-23><-127><-59><-59><-43><-63><-75>Y<-127><-55><-107><-99>Y<-123><-79><-11><-63><-31><-47><-31><-55><-123><-59><-55>5)<-127><-87><-87><-87><-87><-87><-127><5>I5<-127>
=I§<-127><-31><-63><-63>5!<-23><-127><-87><-87><-87><-87><-87><-87><-87><-127>5)<-1>
[WLANAPI] Failed to reference the client context from the handle, error 6
or
[WLANAPI] Stopped waiting for notification because server returns error (0, 1818)

Transition from D0, Unbound to D0, Bound
Command: ndisconfig dapter bind SDIO87871
Resulting log entries:
*<-118><-118><-54>e5<-11>5u<-91><-47><-115><-95>Y<-67><-79><-47><-23><-127><-59><-59><-43><-63><-75>Y<-127><-55><-107><-99>Y<-123><-79><-11><-63><-31><-47><-31><-55><-123><-59><-55>5)<-127><-87><-87><-87><-87><-87><-127><5>I5<-127>
=I§<-127><-31><-63><-63>5!<-23><-127><-87><-87><-87><-87><-87><-87><-87><-127>5)<-1>
!NWUI: GetWirelessInfo failed 0x490

Transition from D4, Bound to D4, Unbound
Command: ndisconfig dapter unbind SDIO87871
Resulting log entries:
*<-118><-118><-54>e5<-11>5u<-91><-47><-115><-95>Y<-67><-79><-47><-23><-127><-59><-59><-43><-63><-75>Y<-127><-55><-107><-99>Y<-123><-79><-11><-63><-31><-47><-31><-55><-123><-59><-55>5)<-127><-87><-87><-87><-87><-87><-127><5>I5<-127>
=I§<-127><-31><-63><-63>5!<-23><-127><-87><-87><-87><-87><-87><-87><-87><-127>5)<-1>
[WLANAPI] Stopped waiting for notification because server returns error (0, 1818)
or
[WLANAPI] Failed to reference the client context from the handle, error 6

Transition from D4, Unbound to D4, Bound
Command: ndisconfig dapter bind SDIO87871
Resulting log entries:
H<-22>U<-107><-91><2>:<-107><-47>]<-91><-55><-107><-79><-107><-51><-51>%<-71><-103><-67><-127><-103><-123><-91><-79><-107><-111><-127><-63><-31><-47><-27><-63>5)<-1>
FatMsm: failed to initialize adapter, error 31
!NWUI: GetWirelessInfo failed 0x490
!NWUI: GetWirelessInfo failed 0x490

Sometimes not all of the protocols (NDISUIO, TCPIP6 , TCPIP) are bound to the SDIO87871 after this call (NDISUIO every time).

Best regards,
Steffen

Hello,
like suggested, the functionality can be implemented for the efusA9X as follows (add error handling):

#include "ndis.h"
#include "WINIOCTL.h"

void BindWifiAdapter(bool enableBinding)
{
TCHAR adapterNames[] = _T("SDIO87871\0"); // ‘\0’ to finish multi sz

HANDLE hDev = CreateFile(_T("NDS0:"), GENERIC_READ | GENERIC_WRITE,
FILE_SHARE_READ | FILE_SHARE_WRITE, NULL, OPEN_EXISTING, 0, NULL);

if (hDev != INVALID_HANDLE_VALUE)
{
BOOL result = DeviceIoControl(hDev,
enableBinding ? IOCTL_NDIS_BIND_ADAPTER : IOCTL_NDIS_UNBIND_ADAPTER,
adapterNames, sizeof(adapterNames), NULL, 0, NULL, NULL);

CloseHandle(hDev);
}
}

void SwitchWifiAdapter(bool enablePower)
{
SetDevicePower(_T("SDIO87871"), POWER_NAME,
enablePower ? PwrDeviceUnspecified : D4);
}

Best regards,
Steffen

Hello,

for the efusA9X audio output is not available. PlaySound fails and the control panel application “Volume & Sounds” shows an “Error” window.

This was tested with image XIPiMX6SX_C8E_V110_BETA_160324.bin and the evaluation kit (with SGTL5000).

The entry “WAV: Version 1.0, ActiveKey = Drivers\BuiltIn\Audio” appears in the debug log but the driver could not be found afterwards in HKLM\Drivers\Active. The I2C communication with the Audio codec works (tested with an own program).

How can we get the audio output working?

Best regards,
Steffen

Hello,

The pin 86 (I2C_B_IRQ) of the efusA9X is described in the Hardware Documentation as input pin with 100k pull-up. But according to our measurements it behaves like an output pin. Tests were done with the evaluation kit and the image XIPiMX6SX_C8E_V110_BETA_160324.bin

The pin is low immediately after a reset and goes to high at start (probably at driver initialization).

The value stays high (with a voltage decrease of about 9mA) if we pull-down it with 10k which indicates that it works at output. Additionally the pin value can set by a program to high (via IOCTL_DIO_SET_PIN) or low (via IOCTL_DIO_CLR_PIN) successfully. This behavior remains unchanged if the pin is configured (via registry settings in DIGITALIO) both as input pin and as output pin low. (The first test was done without changes to the registry.)

The behavior is similar at the efusA9 with the difference that the level is high after reset and goes to low at start. After start the pin can be set by a program if the pin is not configured, if it is configured as output low and if it is configured as input.

I would expect that this pin could be used for notifications about certain activities from connected I2C devices and should behave therefore as input pin. Can you tell me the reason for the observed behavior and why the configuration via registry does not work?

Best regards,
Steffen

Hello,

I've tested backlight with beta V1.10 from 24.3.16 successfully (directly with mode 9).

Thank you!
Steffen

Fine. Easter eggs are welcome

Hello,

we don't use the adapter of the evaluation kit. We have a direct connection between pin 87 (BL_CTRL, PWM) and the LEDCTL signal of the display and don't use any I2C for backlight control. Therefore we need the PWM signal of pin 87 working.

Best regards,
Steffen

Hello.

how can WLAN be switched on and off from program for efusA9X and WEC2013?

Best regards,
Steffen

Hello,

I've tested both the recommended settings of the previous entry additionally to the entries for Mode19 of the BSP and the recommended settings after deleting the other entries beneath Mode19 without success. The difference is that the log entry regarding the I2C call is "missing" in the latter case.

When I use the remote display I can change the Backlight Control with FSBoardConfig but without any effect.

Last week we've made a test with Mode9 and have seen that the PWM signal was always high. After pulling it down the display was OK (except the rotation that isn't working yet according to the road map) but could not be dimmed afterwards therefore. I guess that the PWM Signal remains high also with Mode19 (not yet measured). What could be the reason?

Best regards,
Steffen

Best regards,
Steffen

Hello,

the display still remains dark. Like I've posted Friday morning. there are some error messages in the debug log (display Driver initialization failed after I2C communication failed). The Display that we use doesn't communicate via I2C. Maybe this is the reason for the error messages.

Best regards,
Steffen

Hello,

if we enable the backlight permanently (by hardware means) the display works (with the desired mode 9). It seems that only the backlight control isn't working like expected.

Do we have to do some additional configuration regarding the backlight or the related PWM?

Best regards,
Steffen

Hello,

I've just checked the display behavior with a efusA9 to be sure that the hardware is still operable.

With efusA9 the display works like expected. But I've mentioned another difference to the efusA9X: Immediately after the start / reset the backlight is on. (The display has an undefined grey coloring because the bootscreen is still missing.) With efusA9X the display / backlight stays dark the whole time. Could it be that there is additionally to the XDE setting another option that must be adjusted in the bootloader?

Best regards,
Steffen

Hello,

after setting XDE to 'N' the registry settings for the display can be changed without problems.

After applying the registry changes of your last proposal the display still remains dark.

The log contains the following LCD related messages (I've added Debug = 4):

LCD: Version 1.0, ActiveKey = Drivers\Display\LCD
LCD: Couldn't open key "Drivers\BuiltIn\PXP". Will use 0xfe02fc as default standard background colorkey.
LCD: Read registry settings from Drivers\Display\LCD
LCD: Read registry settings from Drivers\Display\LCD
LCDEXT: Debug = 0x00000004 = 4
I2CDevice = I2C3:
LCDEXT: I2CDeviceAddress = 0x000000c0 = 192
LCDEXT: PWMChannel = 0x00000001 = 1
LCDEXT: PWRConChannel = 0x00000000 = 0
LCDEXT: DisplayResetChannel = 0xffffffff = 4294967295 (Default)
LCDEXT: I2CResetChannel = 0xffffffff = 4294967295 (Default)
LCDEXT: Mode = 0x00000001 = 1 (Default)
LCDEXT: Steps = 0x00000fff = 4095 (Default)
LCDEXT: Freq = 0x00000200 = 512
LCDEXT: DutyCycle = 0x00000050 = 80
I2C_Write(): Message failed (flags=4)
LCD: ASTADPEDT1.dll - Init failed
LCD: Display-Mode 19, Name ET070080
LCD: OutputDevice = DRGB
HW_LCDIF_CTRL1_RD = 0x010f2101

Best regards,
Steffen

Hello,

I've tried to but could not really test with Mode19 and modifies Parameters because there is a strange behavior:

If I've set the display mode to 19 (and made "reg save" and "reg enum" to verify") the display mode is 9 again (like configured in my Image) after a reset.

I guess there is a side effect resetting the display mode and setting other values like OutputDevice (see my previos post).

I've appanded the debug output after changing the display mode to 19 and performing a reset.
I don't know whether the line "Could not initlize LCD interface!" indicates a problem.

Have you any idea about the unexpected registry actions?

Best regards,
Steffen

ClearArmvSysScan()
pInfo@0x80001100
ArmrvSysScan()
pInfo@0x80001100
GetDeviceInfo()
GetProcessorFeatures()
ArchVersion 0x00000003
PU Voltage 0x000004c9
ARM Voltage 0x0000047e
SOC Voltage 0x000004c9
PeriphBase() 0x00a00000
pInfo->NumCpus() 0x00000004
pInfo->TimerClk() 0x00000042
CLIDR=0x09200003
L2CacheType=0x00000000
L2Base=0x00a02000
PL310_ID=0x410000c8
L2 cache found
pInfo->IsExtL2() 0x00000001
pInfo->IsVFPSupported() 0x00000001
CLIDR=0x09200003
L2CacheType=0x00000000
L2Base=0x00a02000
PL310_ID=0x410000c8
L2 cache found
pInfo->GicIntfBase() 0x00a00100
pInfo->GicDistBase() 0x00a01000
pInfo->SecGicIntfBase() 0x00000000
pInfo->SecGicDistBase() 0x00000000
ConfigCpuAuxFeatures()
ConfigCpuDiagCtrl()
0x800011000x00000c09BeforeKernelSta<-6>INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb
======== .ldb div ========
pcscmr2 0x13192c62
pcscmr2_2 0x13192c62
======== .LDB_DI0 ========
pcs2cdr 0xe30c1
======== .lcdfi1 ========
pcscdr2 0x29150
pcscdr2 _2 0x29750
======== .ldb control ========
pLDBCtrl 0x0
======== .LVDS ========
plvds 0x30000
plvds 0x30000
plvds 0x30007
OUTPUT clk: LVDS <4>
pccosr 0x1780100
EBOOT: CCOK1 --
BSPUpda<-4>INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb
Microsoft Windows CE Bootloader Common Library Version 1.2 Built Oct 20 2015 15:37:25
Microsoft Windows CE Bootloader for efusA9X Built Nov 5 2015
Portions copyright (c) 2012 F&S Elektronik Systeme GmbH
Boot Loader, Version 1.0
NBoot, Version VN27
HW rev. 1.10
System ready!
Preparing for download...
Press >S< to step into monitor...
Could not initliaze LCD interface!
AUTO BOOT enabled
+ReadKernelRegionFromNandFlash
Image Signature in Flash Memory found (dwSig=0x43454345)
TOC pointer=0x804831D8
ROMHDR (cTOC = 0x002631d8) ---------------------
DLL First : 0x4001efd9
DLL Last : 0x4012f000
Physical First : 0x80220000
Physical Last : 0x804ef018
Num Modules : 31
RAM Start : 0x80620000
RAM Free : 0x80663000
RAM End : 0x90620000
Num Copy Entries : 2
Copy Entries Offset : 0x8044efc8
Prof Symbol Length : 0x00000000
Prof Symbol Offset : 0x00000000
Num Files : 8
Kernel Flags : 0x00000001
FileSys RAM Percent : 0x20202020
Driver Glob Start : 0x00000000
Driver Glob Length : 0x00000000
CPU : 0x01c4
MiscFlags : 0x0002
Extensions : 0x80222248
Tracking Mem Start : 0x00000000
Tracking Mem Length : 0x00000000
Kernel (2876kB) read from flash disk started finished in 0 milliseconds
Kernel read from NAND
INFO: OEMLaunch: Jumping to Physical Address 0x80220000h (Virtual Address 0x80220000h)...

Jumping to Kernel @ 0x80220000
ArmrvSysScan()
pInfo@0x80001100
GetDeviceInfo()
GetProcessorFeatures()
ArchVersion 0x00000003
PU Voltage 0x000004c9
ARM Voltage 0x0000047e
SOC Voltage 0x000004c9
PeriphBase() 0x00a00000
pInfo->NumCpus() 0x00000004
pInfo->TimerClk() 0x00000042
CLIDR=0x09200003
L2CacheType=0x00000000
L2Base=0x00a02000
PL310_ID=0x410000c8
L2 cache found
pInfo->IsExtL2() 0x00000001
pInfo->IsVFPSupported() 0x00000001
CLIDR=0x09200003
L2CacheType=0x00000000
L2Base=0x00a02000
PL310_ID=0x410000c8
L2 cache found
pInfo->GicIntfBase() 0x00a00100
pInfo->GicDistBase() 0x00a01000
pInfo->SecGicIntfBase() 0x00000000
pInfo->SecGicDistBase() 0x00000000
ConfigCpuAuxFeatures()
ConfigCpuDiagCtrl()
0x800011000x00000c09INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb
Windows CE Kernel for ARM (Thumb Enabled)
+OEMInit
INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0x2b
g_vaL2CtrlBase=0xa0a02000
Enabling L2 cache
OEMInit: silicon rev = 0x0
OAL: Detected 1 CPUs (TODO)
SMP support disabled
efusA9X V1.10 BETA - Firmware Init
Copyright (c) 2015 F&S Elektronik Systeme GmbH
Build: Feb 9 2016/15:30:34
OEMGetRamTable dwMemSize=1024 dwVidMemLen=12
cBoardConfig.chFeatures1=0x0 0 chBoardType=0x8
[OAL] RestartReason: IPP
BINFS: RegisterVolume - Mounted volume '\BINFS'
PM-NETDCU: STARTED
BE2: Version 1.4, ActiveKey = Drivers\Active\01
BE2: Version 1.4, ActiveKey = Drivers\Active\04
ENET: Version 1.2, ActiveKey = Comm\ETHNETA
BSPENETIomuxConfig: Enable RMII 0x2188000.
ENETGetPHYId2: The name for the external PHY is AR8035
BE2: Version 1.4, ActiveKey = Drivers\Active\29
NI2C: Version 0.3, ActiveKey = Drivers\Active\30
NI2C: Version 0.3, ActiveKey = Drivers\Active\31
NI2C: Version 0.3, ActiveKey = Drivers\Active\32
Serial: Port disabled. Serial debug is on !
Serial: Version 1.5, ActiveKey =
Serial: Version 1.5, ActiveKey =
Serial: Version 1.5, ActiveKey =
TCH: Version 1.1, ActiveKey = Drivers\Active\37
SHC: Version 1.3, ActiveKey = Drivers\Active\38
Using Polling Mode
NSPI: Version 3.6, ActiveKey = Drivers\Active\39
EXTRTC: Version 1.2, ActiveKey = Drivers\Active\40
ETHMAN: Version 1.0, ActiveKey = Drivers\Active\42
WAV: Version 1.0, ActiveKey = Drivers\BuiltIn\Audio
BCS: Version 1.4, ActiveKey = Drivers\Active\44
DIO: Version 1.4, ActiveKey = Drivers\Active\45
SpiOverGpio: SPI_Init++ dwContex:aecf9ea0
SpiOverGpio: SPI_Init-- hOpenDevice: a6c62b00
SHC: [USDHC1] SD card inserted
LCD: Version 1.0, ActiveKey = Drivers\Display\LCD
LCD: Couldn't open key "Drivers\BuiltIn\PXP". Will use 0xfe02fc as default standard background colorkey.
LCD: Read registry settings from Drivers\Display\LCD
LCD: Read registry settings from Drivers\Display\LCD
LCD: Display-Mode 9, Name ET043080
LCD: OutputDevice = DRGB
HW_LCDIF_CTRL1_RD = 0x010f2101
AutoLaunch_BloodReader_Settings: Entry
AutoLaunch_BloodReader_Settings: SignalStarted(45) called.
AutoLaunch_BloodReader_Settings: Exit
NDCUCFG V 62 started. Platform: efusA9X
NDCUCFG Open COM1: at 115200 Baud
CreateFile() failed -> ERROR COM1:
SoftRTC disabled
Detecting new link
ENETParsePHYLink: Adapter->MIISeqDone = FALSE;
ENET: LinkState: DISCONNECTED
ENETCheckForHangEx- Start Update Link Status
ENETParsePHYLink: Adapter->MIISeqDone = FALSE;
ENETCheckForHangEx- Start Update Link Status
ENETParsePHYLink: Adapter->MIISeqDone = FALSE;

Hello,

unfortunately it doesn't work. (I've used "reg open \Drivers\Display\lcd\mode9" instead of ...\builtin\..., see below).

Checking these changes I've mentioned that there are some values in the "lcd" directory (like OutputDevice, see below) that can be deleted but will occur again after the next start. I'm not sure if this is expected.
Could any bootloader option have impact?

The changed registry:

!>\: HKEY_LOCAL_MACHINE\drivers\display\lcd
OK
!>OK -> reg enum key \
00 "Mode9" \
01 "Mode19" \
OK -> reg enum value \
00 "UseBootInit"=dword:1 \
01 "OutputDevice"=dword:32768 \
02 "VidMemBase"=dword:-1086324736 \
03 "VidMemLen"=dword:12 \
04 "Mode"=dword:9 \
OK
!>\: HKEY_LOCAL_MACHINE\drivers\display\lcd\mode9
OK
!>OK -> reg enum key \
00 "mode9" \
OK -> reg enum value \
00 "contrastvalue"=dword:1234 \
01 "contrastenable"=dword:1 \
02 "contrastfreq"=dword:4095 \
OK
!>

Best regards,
Steffen

Hello,

what is the meaning of the entry “IntPullUp” for the native I2C driver?
According to the document “Device Driver Documentation” (Version 1.04, 2015-04-09) the registry entry “IntPullUp” for the native I2C driver supports the following values:
0: Disable internal pull-up (default)
1: 100k pull-down
2: 47k pull-up
3: 100k pull-up
4: 22k pull-up

The description of the soft I2C driver states that the IntPullUp value is related to SCL and SDA.
Because the F&S image for the efusA9 / efusA9X has this value configured to 1 and SDA and SCL are high I’m not sure about the meaning of this parameter.

Best regards,
Steffen

Hello,

what is the intended application of the I2C reset?

(I'm using efusA9 / efusA9X and could not find any explanation in the related documents.)

Best regards,
Steffen