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

imx7 and hobbit board, second uart. #1

Open
mhanuel26 opened this issue Mar 15, 2018 · 1 comment
Open

imx7 and hobbit board, second uart. #1

mhanuel26 opened this issue Mar 15, 2018 · 1 comment

Comments

@mhanuel26
Copy link

@richard-hu @ray-chang
Hello,

I have a doubt about the step in the instruction, the M4 debug UART is defined as UART6, is that the second serial port you mention where the hello_world.bin example should print?

I am using iMX7 with hobbit carrier board, as my best understanding UART6 is the debug port, the same I use to see the console log and access u-boot. I have ran the demo but it did no show any console output from M4, it might be that A7 core is using UART6 resource too?

In this case I would like to know how can I use my own .dtsi file to disable UART6 for A7, but I cannot find the way this might be integrated in yocto.

Will appreciate your advice,

@mhanuel26
Copy link
Author

@richard-hu @ray-chang
Hi,

For the pico hobbit board I found after running the demo that the second uart is located in the Mikrobus expansion header under UART3, thou I still don't understand how things get defined, for the pico imx7 I understand the UART6 debug output is defined in yocto as
SERIAL_CONSOLE = "115200 ttymxc4"
under pico-imx7.conf.

In freertos-tn the hello_world example for pico imx7 (imx7d_pioc_m4) defines a debug uart in board.h as
#define BOARD_DEBUG_UART_BASEADDR UART6

So how is the ttymxc# related to UART port on imx7? And how come UART3 is working for M4 demo?

I will appreciate your comments,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant