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

TX - RX mismatch on mt7988 ? #8

Open
Ansuel opened this issue Jun 12, 2024 · 3 comments
Open

TX - RX mismatch on mt7988 ? #8

Ansuel opened this issue Jun 12, 2024 · 3 comments

Comments

@Ansuel
Copy link

Ansuel commented Jun 12, 2024

Hi, in messing with a bananapi r4 and trying to use this tool, I found an interesting interaction between the board and the my serial.

For some reason using the default baudrate values for brom cause a TX -RX mismatch error but using the lowest one makes it work correctly.

Any idea of the cause and how we can bisect this? I notice there were some workaround for some fake serial that required more time...

Problem is that (in theory) my serial is not fake and is even one of the more modern one. It's a CH347. I have verified that the tool works correctly with mt7981 and mt7986.

FIP load is not affected by this problem.

The thing crash at:
https://github.com/981213/mtk_uartboot/blob/main/src/bootrom.rs#L47

TX 215 RX 5
@981213
Copy link
Owner

981213 commented Jul 4, 2024

Is this issue CH347 specific? Also, have you tried a higher baud rate of 921600 for bootrom?
It's possible that the clock setup in bootrom doesn't allow an accurate 460800 baud rate for UART. If that's the case, we could add a list of default baud rates for every SoCs in the utility.

@romanovj
Copy link

romanovj commented Jul 14, 2024

you can try out of tree drivers for ch347 https://github.com/WCHSoftGroup/ch343ser_linux

I had no problem with ch341(with oot driver) and baud rate 921600 (for BL2 and fip) on mt7981 device

@Ansuel
Copy link
Author

Ansuel commented Sep 17, 2024

@981213 btw i feel so stupid an not saying the important thing...

With baudrate of 115200 it does correctly load...

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

3 participants