Skip to content

Renesas : Add USB Device feature #9165

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.

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

Merged
merged 1 commit into from
Jan 9, 2019

Conversation

TomoYamanaka
Copy link
Contributor

@TomoYamanaka TomoYamanaka commented Dec 20, 2018

Description

I implemented USB Device feature for Renesas mbed boards(GR-PEACH and GR-LYCHEE).
The Greentea test of USB Device(Basic / Serial) results are here.
Test_PEACH_GCC.txt
Test_LYCHEE_GCC.txt

Pull request type

[ ] Fix
[ ] Refactor
[x] Target update
[ ] Functionality change
[ ] Docs update
[ ] Test update
[ ] Breaking change

@cmonr
Copy link
Contributor

cmonr commented Dec 20, 2018

@TomoYamanaka Would you be able to provide greentea test results for the USB tests?

@TomoYamanaka
Copy link
Contributor Author

@cmonr

I attached two text files in the above description section. Please you let me know if you can't watch them.

@cmonr
Copy link
Contributor

cmonr commented Dec 20, 2018

@TomoYamanaka Whoops, I did in fact miss those.

Would you happen to also have ARM and IAR results?

@TomoYamanaka
Copy link
Contributor Author

@cmonr Sure. Please wait a bit.

@TomoYamanaka
Copy link
Contributor Author

@cmonr
ARMCC and IAR test results are here.

[ARMCC]
Test_PEACH_ARM.txt
Test_LYCHEE_ARM.txt

[IAR]
Test_PEACH_IAR.txt
Test_LYCHEE_IAR.txt

* NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
* DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
* OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
*/
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the license looks almost OK but as this is a new file, can you add apache 2.0 here, update the copyright and also fix the name, add SPDX identifier as well

Copy link
Contributor Author

@TomoYamanaka TomoYamanaka Dec 21, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I modified this file's header by commit 4c47084.

@@ -0,0 +1,681 @@

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

missing license header

Copy link
Contributor Author

@TomoYamanaka TomoYamanaka Dec 21, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I modified this file's header by commit 4c47084.

@@ -0,0 +1,1506 @@
/* mbed Microcontroller Library
* Copyright (c) 2018-2018 ARM Limited
*
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add SPDX identifier

Copy link
Contributor Author

@TomoYamanaka TomoYamanaka Dec 21, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I modified this file's header by commit 4c47084.

@@ -0,0 +1,85 @@
/* Copyright (c) 2010-2011 mbed.org, MIT License
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@TomoYamanaka I'd br curious to hear about the history of this file since this header makes me think it's beein around for a while.

Copy link
Contributor Author

@TomoYamanaka TomoYamanaka Dec 21, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, this is new file. It seems that the information of the reference file has remained. I modified this file's header by commit 4c47084.

I implemented USB Device feature for Renesas mbed boards.
The code referenced the following code as a starting point and is implemented it by inheritting USBPhy same as other boards.
(mbed-os\features\unsupported\USBDevice\targets\TARGET_RENESAS)
@cmonr cmonr dismissed 0xc0170’s stale review December 21, 2018 03:24

Comments addressed. Please re-review.

@cmonr
Copy link
Contributor

cmonr commented Dec 21, 2018

@0xc0170 Please re-review. Should be alright now.

@cmonr
Copy link
Contributor

cmonr commented Dec 21, 2018

CI started

@mbed-ci
Copy link

mbed-ci commented Dec 21, 2018

Test run: FAILED

Summary: 1 of 11 test jobs failed
Build number : 1
Build artifacts

Failed test jobs:

  • jenkins-ci/mbed-os-ci_greentea-test

@NirSonnenschein
Copy link
Contributor

NirSonnenschein commented Dec 24, 2018

@TomoYamanaka
strange failures in tests, which may not be unrelated:
http://mbed-os-ci.s3-website-eu-west-1.amazonaws.com/?prefix=jenkins-ci/artifacts/9165/1/greentea-test/647/

tests which failed:
ARCH_PRO iar_arm / ARCH_PRO-IAR.tests-usb_device-serial.CDC USB reconnectARCH_PRO arm-none-eabi-gcc / ARCH_PRO-GCC_ARM.tests-usb_device-serial.CDC USB reconnectARCH_PRO armcc / ARCH_PRO-ARM.tests-usb_device-serial.CDC USB reconnectNUCLEO_F207ZG iar_arm / NUCLEO_F207ZG-IAR.tests-usb_device-serial.CDC USB reconnectNUCLEO_F207ZG armcc / NUCLEO_F207ZG-ARM.tests-usb_device-serial.CDC USB reconnectNUCLEO_F207ZG arm-none-eabi-gcc / NUCLEO_F207ZG-GCC_ARM.tests-usb_device-serial.CDC USB reconnectNUCLEO_F429ZI iar_arm / NUCLEO_F429ZI-IAR.tests-usb_device-serial.CDC USB reconnectNUCLEO_F429ZI armcc / NUCLEO_F429ZI-ARM.tests-usb_device-serial.CDC USB reconnectNUCLEO_F429ZI arm-none-eabi-gcc / NUCLEO_F429ZI-GCC_ARM.tests-usb_device-serial.CDC USB reconnectK64F iar_arm / K64F-IAR.tests-usb_device-serial.CDC USB reconnectK64F armcc / K64F-ARM.tests-usb_device-serial.CDC USB reconnectK64F arm-none-eabi-gcc / K64F-GCC_ARM.tests-usb_device-serial.CDC USB reconnect

@cmonr
Copy link
Contributor

cmonr commented Dec 24, 2018

@c1728p9 Is it possible something came into this branch that's causing issues?

@cmonr
Copy link
Contributor

cmonr commented Dec 28, 2018

Running CI on the feature branch. Will report bcak in the morning.

@cmonr
Copy link
Contributor

cmonr commented Dec 28, 2018

Interesting. It looks like the base branch failed.

@cmonr
Copy link
Contributor

cmonr commented Dec 28, 2018

Ooooh. Crap. It looks like the PR that added the tests was run on the old CI.

@studavekar @OPpuolitaival Do you know/remember what test runner differences exist between the old CI and the new one? Looking at this PR's failures (they're the same as the base branch), there's a bunch of socketio activity, but the test simply times out.

@TomoYamanaka On the plus side, this means that once we get this test issue sorted out, this PR should be easy to bring through since it seems to be fine.

@studavekar
Copy link
Contributor

@0xc0170
Copy link
Contributor

0xc0170 commented Jan 2, 2019

@cmonr none of us test should be running as defined in https://github.com/ARMmbed/mbed-os-ci/blob/master/mbed-os-jenkins/mbed-os-ci-greentea-test/Jenkinsfile.groovy#L54

@OPpuolitaival Can you review? Looks to me that this covers only some usb tests not serial one? Not certain what has changed on the feature branch but looks like this is CI config issue?

@cmonr cmonr added parked and removed parked labels Jan 2, 2019
@0xc0170
Copy link
Contributor

0xc0170 commented Jan 3, 2019

Set as "needs: work", until we fix the config in the CI

@OPpuolitaival
Copy link
Contributor

@cmonr @0xc0170 This is bigger issue in CI and it takes time to figure out how to make this testing happening in CI setup. Need to test manually for now

@OPpuolitaival
Copy link
Contributor

I mean that this PR change need to be tested manually, CI is not testing it. The CI error root cause is most probably CI misconfiguration during the development. I did restart the test

@cmonr
Copy link
Contributor

cmonr commented Jan 3, 2019

@OPpuolitaival For the time being, is there anything we can do from the GitHub side of things to progress this PR, or is this stuck waiting on a CI change?

@OPpuolitaival
Copy link
Contributor

feature-hal-spec-usb-device branch do not pass the CI. That is the root cause. The results are visible in https://mbed-os.mbedcloudtesting.com/job/mbed-os-ci/job/feature-hal-spec-usb-device/ I need to find someone to discuss what is the best solution for that

@OPpuolitaival
Copy link
Contributor

Started email thread with @studavekar and @c1728p9

@cmonr cmonr added the parked label Jan 4, 2019
@OPpuolitaival
Copy link
Contributor

Fixed usb tests skip command:
"tests-usb_device-basic" => "tests-usb_device-*"
Commit in internal repository: https://github.com/ARMmbed/mbed-os-ci/commit/65b8762973a2fefa792f9f5a2b1faffb60d7f82c

Restarted tests also

@0xc0170 0xc0170 removed the parked label Jan 7, 2019
@cmonr cmonr merged commit 8b6fffb into ARMmbed:feature-hal-spec-usb-device Jan 9, 2019
@TomoYamanaka TomoYamanaka deleted the usb_device branch January 10, 2019 00:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants