We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In the MAX32690 FTHR board.c file, we have:
const mxc_gpio_cfg_t pb_pin[] = { { MXC_GPIO1, MXC_GPIO_PIN_14, MXC_GPIO_FUNC_IN, MXC_GPIO_PAD_PULL_UP, MXC_GPIO_VSSEL_VDDIOH, MXC_GPIO_DRVSTR_0 }, { MXC_GPIO1, MXC_GPIO_PIN_15, MXC_GPIO_FUNC_IN, MXC_GPIO_PAD_PULL_UP, MXC_GPIO_VSSEL_VDDIOH, MXC_GPIO_DRVSTR_0 }, };
Notice that P1.14 and P1.15 are set to VDDIOH.
But the data sheet says these pins can only be VDDIO:
"GPIO that support HyperBus as an alternate function are tied to the VDDIO supply and do not support VDDIOH supply selection."
The text was updated successfully, but these errors were encountered:
No branches or pull requests
In the MAX32690 FTHR board.c file, we have:
const mxc_gpio_cfg_t pb_pin[] = {
{ MXC_GPIO1, MXC_GPIO_PIN_14, MXC_GPIO_FUNC_IN, MXC_GPIO_PAD_PULL_UP, MXC_GPIO_VSSEL_VDDIOH, MXC_GPIO_DRVSTR_0 },
{ MXC_GPIO1, MXC_GPIO_PIN_15, MXC_GPIO_FUNC_IN, MXC_GPIO_PAD_PULL_UP, MXC_GPIO_VSSEL_VDDIOH, MXC_GPIO_DRVSTR_0 },
};
Notice that P1.14 and P1.15 are set to VDDIOH.
But the data sheet says these pins can only be VDDIO:
"GPIO that support HyperBus as an alternate function are tied to the VDDIO supply and do not support VDDIOH supply selection."
The text was updated successfully, but these errors were encountered: