Skip to content

CM3DS 'EMAC unicast long' Timeout #8200

@kapi90

Description

@kapi90
Contributor

When I run EMAC related Greentea tests on my CM3DS target (MPS2+ Rev. C) it seems that the 600s Timeout that is set by default is not enough for the EMAC unicast long testcase, in which the board sends, receives and validates 50,000 packets. When I ran the same test without using the python environment (Connect to it with DS-5 and Serial Terminal (Putty), do a software reset and send {{__sync;1}} to start) it didn't have the 600s timeout limit and so all test cases passed with no problem.

Target: CM3DS
Toolchain: GCC_ARM 7 2017-q4-major
Mbed OS SHA: 62f8b92

[ ] Question
[x ] Enhancement
[ ] Bug

@ashok-rao @SeppoTakalo

Activity

ashok-rao

ashok-rao commented on Sep 27, 2018

@ashok-rao
Contributor

@SeppoTakalo ..what do you think for the above issue?

SeppoTakalo

SeppoTakalo commented on Sep 27, 2018

@SeppoTakalo
Contributor

How long did it then take on this platform?

@mikaleppanen What do you think, is 600 seconds not enough?

SeppoTakalo

SeppoTakalo commented on Sep 27, 2018

@SeppoTakalo
Contributor

I'm okay with the idea of rising the timeout if its not way too long.
We are generally not expecting any defined speed or performance from the devices.

So if somebody sends a PR with test report that shows that this device was able to pass, I'm happy to accept.

mikaleppanen

mikaleppanen commented on Sep 27, 2018

@mikaleppanen

For K64F ethernet it takes 84.17 seconds. I'm also ok with raising the timeout if the device ethernet speed is such that 600 seconds is not enough.

SeppoTakalo

SeppoTakalo commented on Sep 27, 2018

@SeppoTakalo
Contributor

@kapi90 Can you share the Ethernet driver with us?
Perhaps send a PR.

Within the 5.9 timeframe all ethernet drivers have been refactored and outdated dropped. By that time, nobody was working with the CM3DS, so it got dropped.

If you have ported the driver to new EMAC API we are happy to review and test it.

deleted a comment from ciarmcom on Oct 1, 2018
adbridge

adbridge commented on Oct 4, 2018

@adbridge
Contributor

Internal Jira reference: https://jira.arm.com/browse/ONME-3908

kapi90

kapi90 commented on Oct 9, 2018

@kapi90
ContributorAuthor

Hi @SeppoTakalo, sorry for the late reply, I just got back from vacation. I'll need to push my code through our internal code and IP reviews first, once that is done I'm gonna share the EMAC driver, so you can take a look at it and test it however you like. How does that sound ?

kapi90

kapi90 commented on Oct 16, 2018

@kapi90
ContributorAuthor

There's been a PR created for the EMAC driver, that's available here: #8444

The issue seems to have changed, now the timeout happens at the end of the last test case, look like 1200s is a little bit short to get to the end of all test cases.

TuomoHautamaki

TuomoHautamaki commented on Nov 6, 2018

@TuomoHautamaki

Fix provided in #8604

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @0xc0170@SeppoTakalo@adbridge@mikaleppanen@ciarmcom

        Issue actions

          CM3DS 'EMAC unicast long' Timeout · Issue #8200 · ARMmbed/mbed-os