Skip to content

UBLOX_EVK_ODIN_W2 Issues #2955

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
screamerbg opened this issue Oct 6, 2016 · 11 comments
Closed

UBLOX_EVK_ODIN_W2 Issues #2955

screamerbg opened this issue Oct 6, 2016 · 11 comments
Labels
devices: ublox

Comments

@screamerbg
Copy link
Contributor

screamerbg commented Oct 6, 2016 •
edited
Loading

Description

  • Type: Bug
  • Priority: Major

Cannot set A0, A3 high (via DigitalOut)

Attach an LED and try it yourself

Digital loop tests failures (DigitalIn + DigitalOut)

Digital I/O loop on D2 -> D3
Digital I/O loop on D3 -> D2

Analog In failures (AnalogIn)

Analog Input on A1
Analog Input on A2
Analog Input on A3
Analog Input on A4 (suspecting that the app crashed)

## I2C failures with EEPROM (I2C)
I2C - EEProm Read (fails with ARMCC, GCC)
I2C - TMP102 Temperature Read (fails with GCC)

SPI Failures

Toolchain:
GCC_ARM, ARM

meed-os sha:
22ec73b Merge pull request #2948 from jamike/Fixed_iarm_debug_built_failed

Steps to reproduce
Tests available here https://github.com/armmbed/ci-test-shield
Hardware components here https://github.com/ARMmbed/mbed-HDK/tree/master/Production%20Design%20Projects/CITestShield

CC @andreaslarssonublox
@screamerbg screamerbg changed the title UBLOX_EVK_ODIN_W2 - Pinout issues UBLOX_EVK_ODIN_W2 Issues Oct 6, 2016
@screamerbg
Copy link
Contributor Author

I2C no longer an issue thanks to PR #2972. cc @adustm @bcostm @betzw @andreaslarssonublox

@ramtin-r
Copy link

ramtin-r commented Oct 26, 2016 •
edited
Loading

  1. Only A1 and A2 can be as digital pins.
  2. D2 is used for UART and can not be used for testing digital loop case.
  3. A4 can not be used as analog.
  4. SPI Failures -> Not clear what the problem is

cc @adustm @bcostm @betzw @andreaslarssonublox @screamerbg

@bcostm
Copy link
Contributor

bcostm commented May 22, 2017

Can you please remove the ST label and add Ublox label instead ?

@0xc0170
Copy link
Contributor

0xc0170 commented May 25, 2017

@andreaslarssonublox bump

@andreaslarssonublox
Copy link

We ran the tests again with this SW:
mbed-os: SHA-1: 598cbdf
ci-shield: SHA-1: 691997cf918090584844c67f02d866df08b5fe5f

+---------------------------+-------------------+-----------------------+------------------------------------+--------+--------+--------+--------------------+
| target | platform_name | test suite | test case | passed | failed | result | elapsed_time (sec) |
+---------------------------+-------------------+-----------------------+------------------------------------+--------+--------+--------+--------------------+
| UBLOX_EVK_ODIN_W2-GCC_ARM | UBLOX_EVK_ODIN_W2 | tests-api-analogin | Analog Input on AIN_0 | 0 | 2 | FAIL | 0.27 |
| UBLOX_EVK_ODIN_W2-GCC_ARM | UBLOX_EVK_ODIN_W2 | tests-api-analogin | Analog Input on AIN_1 | 0 | 4 | FAIL | 0.49 |
| UBLOX_EVK_ODIN_W2-GCC_ARM | UBLOX_EVK_ODIN_W2 | tests-api-analogin | Analog Input on AIN_2 | 0 | 1 | FAIL | 0.17 |
| UBLOX_EVK_ODIN_W2-GCC_ARM | UBLOX_EVK_ODIN_W2 | tests-api-analogin | Analog Input on AIN_3 | 0 | 3 | FAIL | 0.37 |
| UBLOX_EVK_ODIN_W2-GCC_ARM | UBLOX_EVK_ODIN_W2 | tests-api-analogin | Analog Input on AIN_4 | 0 | 0 | ERROR | 0.0 |
| UBLOX_EVK_ODIN_W2-GCC_ARM | UBLOX_EVK_ODIN_W2 | tests-api-businout | tests-api-businout | 0 | 1 | ERROR | 48.46 |
| UBLOX_EVK_ODIN_W2-GCC_ARM | UBLOX_EVK_ODIN_W2 | tests-api-digitalio | Digital I/O on DIO_2/DIO_3 | 0 | 1 | FAIL | 0.12 |
| UBLOX_EVK_ODIN_W2-GCC_ARM | UBLOX_EVK_ODIN_W2 | tests-api-digitalio | Digital I/O on DIO_3/DIO_2 | 0 | 1 | FAIL | 0.12 |
| UBLOX_EVK_ODIN_W2-GCC_ARM | UBLOX_EVK_ODIN_W2 | tests-api-digitalio | Digital I/O on DIO_4/DIO_5 | 1 | 0 | OK | 0.06 |
| UBLOX_EVK_ODIN_W2-GCC_ARM | UBLOX_EVK_ODIN_W2 | tests-api-digitalio | Digital I/O on DIO_5/DIO_4 | 1 | 0 | OK | 0.06 |
| UBLOX_EVK_ODIN_W2-GCC_ARM | UBLOX_EVK_ODIN_W2 | tests-api-digitalio | Digital I/O on DIO_6/DIO_7 | 1 | 0 | OK | 0.05 |
| UBLOX_EVK_ODIN_W2-GCC_ARM | UBLOX_EVK_ODIN_W2 | tests-api-digitalio | Digital I/O on DIO_7/DIO_6 | 1 | 0 | OK | 0.05 |
| UBLOX_EVK_ODIN_W2-GCC_ARM | UBLOX_EVK_ODIN_W2 | tests-api-i2c | I2C - EEProm 2nd WR 10 Bytes | 1 | 0 | OK | 0.06 |
| UBLOX_EVK_ODIN_W2-GCC_ARM | UBLOX_EVK_ODIN_W2 | tests-api-i2c | I2C - EEProm 2nd WR 100 Bytes | 1 | 0 | OK | 0.08 |
| UBLOX_EVK_ODIN_W2-GCC_ARM | UBLOX_EVK_ODIN_W2 | tests-api-i2c | I2C - EEProm 2nd WR 2 Bytes | 1 | 0 | OK | 0.06 |
| UBLOX_EVK_ODIN_W2-GCC_ARM | UBLOX_EVK_ODIN_W2 | tests-api-i2c | I2C - EEProm 2nd WR Single Byte | 1 | 0 | OK | 0.06 |
| UBLOX_EVK_ODIN_W2-GCC_ARM | UBLOX_EVK_ODIN_W2 | tests-api-i2c | I2C - EEProm WR 10 Bytes | 1 | 0 | OK | 0.06 |
| UBLOX_EVK_ODIN_W2-GCC_ARM | UBLOX_EVK_ODIN_W2 | tests-api-i2c | I2C - EEProm WR 100 Bytes | 1 | 0 | OK | 0.07 |
| UBLOX_EVK_ODIN_W2-GCC_ARM | UBLOX_EVK_ODIN_W2 | tests-api-i2c | I2C - EEProm WR 2 Bytes | 1 | 0 | OK | 0.05 |
| UBLOX_EVK_ODIN_W2-GCC_ARM | UBLOX_EVK_ODIN_W2 | tests-api-i2c | I2C - EEProm WR Single Byte | 1 | 0 | OK | 0.06 |
| UBLOX_EVK_ODIN_W2-GCC_ARM | UBLOX_EVK_ODIN_W2 | tests-api-i2c | I2C - Instantiation of I2C Object | 1 | 0 | OK | 0.06 |
| UBLOX_EVK_ODIN_W2-GCC_ARM | UBLOX_EVK_ODIN_W2 | tests-api-i2c | I2C - LM75B Temperature Read | 1 | 0 | OK | 0.06 |
| UBLOX_EVK_ODIN_W2-GCC_ARM | UBLOX_EVK_ODIN_W2 | tests-api-interruptin | InterruptIn on DIO_2 | 0 | 2 | FAIL | 0.16 |
| UBLOX_EVK_ODIN_W2-GCC_ARM | UBLOX_EVK_ODIN_W2 | tests-api-interruptin | InterruptIn on DIO_3 | 0 | 2 | FAIL | 0.17 |
| UBLOX_EVK_ODIN_W2-GCC_ARM | UBLOX_EVK_ODIN_W2 | tests-api-interruptin | InterruptIn on DIO_4 | 1 | 0 | OK | 0.06 |
| UBLOX_EVK_ODIN_W2-GCC_ARM | UBLOX_EVK_ODIN_W2 | tests-api-interruptin | InterruptIn on DIO_5 | 1 | 0 | OK | 0.05 |
| UBLOX_EVK_ODIN_W2-GCC_ARM | UBLOX_EVK_ODIN_W2 | tests-api-interruptin | InterruptIn on DIO_6 | 1 | 0 | OK | 0.04 |
| UBLOX_EVK_ODIN_W2-GCC_ARM | UBLOX_EVK_ODIN_W2 | tests-api-interruptin | InterruptIn on DIO_7 | 1 | 0 | OK | 0.05 |
| UBLOX_EVK_ODIN_W2-GCC_ARM | UBLOX_EVK_ODIN_W2 | tests-api-pwm | Pwm object definable | 0 | 0 | ERROR | 0.0 |
| UBLOX_EVK_ODIN_W2-GCC_ARM | UBLOX_EVK_ODIN_W2 | tests-api-spi | SPI - Object Definable | 1 | 0 | OK | 0.05 |
| UBLOX_EVK_ODIN_W2-GCC_ARM | UBLOX_EVK_ODIN_W2 | tests-api-spi | SPI - SD card exists | 0 | 1 | FAIL | 0.33 |
+---------------------------+-------------------+-----------------------+------------------------------------+--------+--------+--------+--------------------+
mbedgt: test case results: 9 FAIL / 19 OK / 3 ERROR
mbedgt: completed in 473.10 sec

Comments:

  • The tests-api-analogin won't pass because A0 and A1 are configured as either input or output by changing the jumpers J26.
  • The tests-api-digitalio won't pass since D2 is used as debug UART RX. If this pin can be omitted from the tests it would pass.
  • The tests-api-interruptin won't pass see tests-api-digitalio.
  • The tests-api-pwm won't pass since we don't support PWM on all pins. If some pins can be omitted from the test it would pass.
  • We have created an internal PR for tests-api-spi, TE_OM2-58

@0xc0170 Is it mandatory to pass those tests for mbed-os 5.5?

@0xc0170
Copy link
Contributor

0xc0170 commented May 30, 2017

@0xc0170 Is it mandatory to pass those tests for mbed-os 5.5?

Not yet. The ci test shield repo will go through some updates to address some of the comments above regarding not all pins are available for all peripherals.

Do we need to update https://github.com/ARMmbed/ci-test-shield/blob/master/mbed_app.json to reflect any of these failures (update pins) ?

@andreaslarssonublox
Copy link

Ok.
I don't think we can fix anything by updating the mbed_app.json since it will only replace pins I guess.

@ciarmcom
Copy link
Member

ciarmcom commented Jun 1, 2018

ARM Internal Ref: MBOTRIAGE-385

@0xc0170
Copy link
Contributor

0xc0170 commented Jun 5, 2018

@andreaslarssonublox Is this as won't fix or already resolved? It's been some time since the last update.

@andreaslarssonublox
Copy link

@0xc0170 I don't think we will fix it unless mandatory. @asifrizwanubx

@deepikabhavnani
Copy link

Mandatory ?

Not yet. The ci test shield repo will go through some updates to address some of the comments above regarding not all pins are available for all peripherals.

I don't think we will fix it unless mandatory

Closing it, please reopen later

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
devices: ublox
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@sg- @0xc0170 @bcostm @screamerbg @andreaslarssonublox @ciarmcom @ramtin-r @deepikabhavnani