Test application can't access to ATECC608A device via I2C [Embedded Linux]

[victorK8]

Test application can't access to ATECC608A device via I2C the bug

Used platform

• Microchip sam5d27-wlsom1 with custom buildroot's linux distribution.
• ATECC608A with UDFN socket with XPRO connector.

Compiling

We cross-compile cryptoauth library and test app on Ubuntu 20.04 LTS machine (without errors or warnings).

After that, we send all compiled content to platform via scp.

Bug

In sam5d27-wlsom1 platform, we run the test app succesfully.

However, when we are running info attribute, test app returns the next lines:

/home/victor/cryptoauthlib/lib/atca_iface.c:98:e1:Failed to configure HAL
/home/victor/cryptoauthlib/lib/atca_iface.c:54:e1:atinit
atcab_init() failed with ret=0x000000E1

ATECC608A is correctly connected to platform via I2C in XPRO connector. Running i2cdetect -y 1 command, we can check that ATECC608A has 0x60 address in i2c bus. Result of i2cdetect command:

00: -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- UU -- -- -- --
60: 60 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

Any idea?

Thank guys!

[bryan-hunt]

Try to set the communication parameters manually:

info -i i2c 1 -a c0

Subsequent commands will use the cached parameters

[victorK8]

Hi @bryan-hunt

I run test application with ./cryptoauth_test. After that, I try the following commands:

info -i i2c 1 -a c0

info -i i2c 1 -a 0x60

info -i i2c 1 -a 60

As result, test displays atcab_info() failed with ret=0x000000FD in all commands.

Also, I try ecc608nfo -i i2c 1 -a 60 with success (software returns Device Selected.). However, I run info command, and software returns the following error:

/home/victor/cryptoauthlib/lib/calib/calib_read.c:103:f0:calib_read_zone - execution failed
/home/victor/cryptoauthlib/lib/calib/calib_read.c:619:f0:calib_read_zone - falied
atcab_init() failed with ret=0x000000F0

Could it be an error related with device initialization on calib software?

I have no error during compiling phase. I pass my cmake setup for cross-compiling (maybe some needed flag is missing):

CC=arm-linux-gcc CXX=arm-linux-g++ cmake -S .. -B . -DATCA_ATECC608A_SUPPORT=ON -DBUILD_TESTS=ON -DATCA_PRINTF=ON -DATCA_BUILD_SHARED_LIBS=ON -DATCA_HAL_I2C=ON -DATCA_PKCS11=ON -DATCA_USE_ATCAB_FUNCTIONS=ON 

Thanks!!

[bryan-hunt]

I have confirmed in v3.3.1 when the baud rate is changed to 100khz everything is working properly on a raspberry pi. The latest version that has been release v3.3.2 changed the default configuration on linux to 100khz so it should exhibit the same behavior as v3.2x

[bryan-hunt]

I believe everything related to this configuration issue is resolved in v3.3.2 and the corresponding python release 20210620 where the baud rate in the default structures is set to 100khz on linux platforms.

[victorK8]

Hi @bryan-hunt,

Thanks for answering.

I'll try to set baudrate to 100kHz.

Thanks!

[timliang73]

Did you find the root cause? thanks

[victorK8]

Hi, Yeah. It's ok now. Thanks El lun, 6 mar 2023 10:29, timliang73 ***@***.***> escribió:

…

Did you find the root cause? thanks — Reply to this email directly, view it on GitHub <#230 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJ4XRMV2I7RRCSCE4VSPPQTW2WVBNANCNFSM453CUFHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>