8000 Portenta C33 USB regression. · Issue #15651 · micropython/micropython · GitHub
[go: up one dir, main page]
Skip to content

Portenta C33 USB regression. #15651

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
andrewleech opened this issue Aug 13, 2024 · 5 comments
Closed

Portenta C33 USB regression. #15651

andrewleech opened this issue Aug 13, 2024 · 5 comments

Comments

@andrewleech
Copy link
Contributor

Port, board and/or hardware

Renesas port, Portenta C33

MicroPython version

Micropython nightly builds after v1.23

Reproduction

Use DFU to load micropython firmware.

Expected behaviour

USB serial / repl should be available.

Observed behaviour

USB does not enumerate.

Additional Information

As reported in #14462 (comment)

Code of Conduct

Yes, I agree
@andrewleech
Copy link
Contributor Author
andrewleech commented Aug 13, 2024 •
edited
Loading

Hi @iabdalkader I wanted to capture this regression here in its own separate issue for tracking, I feel it really should be resolved one way or another before the next release.

I don't personally feel confident that just a crystal/clock issue could cause the fault in combination with 2d33071
I think it's more likely a bug I've introduced in the USB HS vs FS configuration.

One of the primary goals of my set of stdio consolidate commits was to enable the runtime USB / machine.USBDevice support on more ports, so I'm loath to suggest just reverting that commit as that blocks progressing this on the renesas port.

I don't have any renesas high speed devices to test & fix with however.

Did you get any feedback on whether the newer builds do work on production boards though?

@iabdalkader
Copy link
Contributor

I don't personally feel confident that just a crystal/clock issue could cause the fault in combination with 2d33071
I think it's more likely a bug I've introduced in the USB HS vs FS configuration.

I think it really might just be the bad crystal there, it also had something to do with USB maybe it derived some clock from it. I wouldn't revert anything until we can test it.

Did you get any feedback on whether the newer builds do work on production boards though?

Not yet, everyone is on vacation including me and I don't have a second C33 to test with, but will check again.

@iabdalkader
Copy link
Contributor

Everything is working on a production board, USB and WiFi:

WiFi Connected  ('192.168.86.244', '255.255.255.0', '192.168.86.1', '192.168.86.1')
Year:2024 Month:8 Day:13 Time: 9:19:38

@iabdalkader
Copy link
Contributor

I can test this when I get back in two weeks: #15550

@andrewleech
Copy link
Contributor Author

That all sounds great thanks! I still find it curious it worked before the change on your board but not after, but I'll take any positive test results!

Thanks for the feedback and enjoy the rest of your time off!

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

No branches or pull requests
2 participants
@andrewleech @iabdalkader
0