boards: frdm_mcxa166, frdm_mcxa276: add adc,i2c,spi support

[peterwangsz]

1. enable adc,i2c,spi support
2. verified adc samples/drivers/adc/adc_dt and tests/drivers/adc/adc_api
3. verified i2c tests/drivers/i2c/i2c_target_api
4. verified spi tests/drivers/spi/spi_loopback

[hakehuang]

this application need add to platform_allow

[peterwangsz]

updated in new commit, please help to review. thanks.

[hakehuang]

would this be better, that separated PR for separated module? @decsny what do you think?

[hakehuang]

@peterwangsz, fails on frdm_mcxa276 i2c_target_api

*** Booting Zephyr OS build v4.1.0-3916-gf4aec7c85eda ***
Running TESTSUITE i2c_eeprom_target
===================================================================
START - test_eeprom_target
Found EEPROM 0 on I2C bus device i2c@400d4000 at addr 54
Found EEPROM 1 on I2C bus device i2c@400d5000 at addr 56
Testing single-role
Testing full read: Master: i2c@400d5000, address: 0x54

    Assertion failed at WEST_TOPDIR/zephyr/tests/drivers/i2c/i2c_target_api/src/main.c:58: run_full_read: (ret not equal to 0)
Failed to read EEPROM
 FAIL - test_eeprom_target in 0.030 seconds
===================================================================
TESTSUITE i2c_eeprom_target failed.

------ TESTSUITE SUMMARY START ------

SUITE FAIL -   0.00% [i2c_eeprom_target]: pass = 0, fail = 1, skip = 0, total = 1 duration = 0.030 seconds
 - FAIL - [i2c_eeprom_target.test_eeprom_target] duration = 0.030 seconds

------ TESTSUITE SUMMARY END ------

===================================================================
RunID: 92ec7c05e750eb130a01a89883ee523f
PROJECT EXECUTION FAILED

[peterwangsz]

hi @hakehuang ,
to test the i2c_target_api case, please setup board connection as below (see frdm_mcxa166.overlay):
/* To test this sample, connect

• LPI2C2 SCL(J2-20) --> LPI2C3 SCL(J5-5)
• LPI2C2 SDA(J2-18) --> LPI2C3 SDA(J5-6)
  */

[hakehuang]

to test the i2c_target_api case, please setup board connection as below (see frdm_mcxa166.overlay): /* To test this sample, connect

• LPI2C2 SCL(J2-20) --> LPI2C3 SCL(J5-5)
• LPI2C2 SDA(J2-18) --> LPI2C3 SDA(J5-6)
  */

I did so, and frdm_mcxa166 is OK, but frdm_mcxa276 is not @peterwangsz

[peterwangsz]

hi @hakehuang
indeed, this is pin conflict for LPI2C2 pins. I have updated to commit to use LPI2C1 and LPI2C3 in the test case.
Please help to test again.
thanks.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
90.2% Duplication on New Code

See analysis details on SonarQube Cloud

[hakehuang]

board testing pass on v4.1.0-3924-gb28a3871f7a5