Skip to content
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

mimxrt1011, 400mhz support #286

Closed
ccrome opened this issue Feb 18, 2023 · 7 comments
Closed

mimxrt1011, 400mhz support #286

ccrome opened this issue Feb 18, 2023 · 7 comments
Labels
bug Something isn't working

Comments

@ccrome
Copy link
Contributor

ccrome commented Feb 18, 2023

Operating System

Linux

INFO_UF2.TXT

If i'm not mistaken, I believe that the default mimxrt1011 tinyuf2 starts at 500MHz. It should probably start at 400Mhz or lower to ensure that it's compatible with all chip revisions.

I might be mistaken -- I used the mcu config tools to read the clock_config.c file, so it's quite possible that process didn't work right.

What happened ?

I think the system is starting at 500Mhz, which is well outside the specs for the 400mhz part.

How to reproduce ?

just putting something here because i have to.

Debug Log

No response

Screenshots

No response

@ccrome ccrome added the bug Something isn't working label Feb 18, 2023
@tannewt
Copy link
Member

tannewt commented Mar 1, 2023

The only version I see here is 500mhz capable. Where is a 400mhz part documented?

@ccrome
Copy link
Contributor Author

ccrome commented Mar 1, 2023

in the "Buy/Paramettrics" tab.

image

@hathach
Copy link
Member

hathach commented Mar 2, 2023

each board has its own clock_config.c/h and can be configured individually, yes ?

@ccrome
Copy link
Contributor Author

ccrome commented Mar 2, 2023

each board has its own clock_config.c/h and can be configured individually, yes ?

Yes. Now that I think about it, this really isn't a bug for the imxrt1010_evk. It's that I was using the imxrt1010_evk as a placeholder for 'all i.mx RT 1011 based boards'.

I guess it's just a policy choice: do you want the clock speed set to the maximum clock speed available for that particular board, or the maximum clock speed supported by all members of the CPU family? The former means when transitioning from an evk to a custom board, it's easy to miss the fact that the clock speed of the chip is different (exactly what happened to me), vs. the bootloader running at lower clock speed.

Actually, now that I think about it, does the bootloader need to run at such high speeds at all? Perhaps it should just leave the PLL disabled and run everything at 24 MHz?

@gsteiert any opinion here? I was wondering if we should do the minimum amount of clock setup necessary to make things go, so it's left for the app in as close to reset state as possible. Rather than doing the full auto-generated BOARD_BootClockRUN call.

@hathach
Copy link
Member

hathach commented Mar 3, 2023

Each board should configure its preferred clock individually with clock_config. I don't think we need to set any minimum or maximum clock at all. They should run with their optimum design (crystal/power etc...). If you accept this answer, we can close this issue.

@gsteiert
Copy link
Collaborator

gsteiert commented Mar 3, 2023 via email

@ccrome
Copy link
Contributor Author

ccrome commented Mar 3, 2023

Yep, makes sense to me, closing...

@ccrome ccrome closed this as not planned Won't fix, can't repro, duplicate, stale Mar 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants