You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I'm working on a small camera with hi3518ev200 chip and a wifi module connected to SDIO1. Original stock firmware is a LiteOS clone. I've managed to flash openipc on it, and after investigating both stock firmware and ipctool readouts it seems there are discrepancies in your SDIO1 mappings in EV20Xregs array.
According to "ipctool reginfo" almost all SDIO1_ pins correspond to pinmux register value "0x3", except SDIO1_CARD_POWER_EN which is 0x4. This seems wrong, my stock firmware sets all those values to 0x4. I've replicated that and after some more shenanigans with onboard MCU (which is connected to UART1 and controls PWR and RST pins for wifi) I've finally managed to make wifi card at least present itself on MMC bus (as SDIO_ID 0296:5347 which seems to be in kernel already as Wilc1000 but is NOT actually that card or very much compatible at all :-/).
Anyway, this is pinmux configuration which makes SDIO1_* pins work correctly (at least those used on my board, I'm not sure about SDIO1_CARD_DETECT, SDIO1_CWPR and SDIO1_CARD_POWER_EN but have no reason to doubt the stock firmware setting them right):
Some of these pins I've tested manually in GPIO mode and that seemed to work fine with pinmux reg 0x0, and the default power-on values are 0x1 which would point to RMII/EPHY also being correct, but I have no idea what exactly should be mapped to 0x2/0x3 values.
Is it possible perhaps to insert "UNKNOWN" as 0x3 in there so the SDIO1 pins are in correct position? It's cost me quite some time and frustration wondering why nothing works with original 0x3 values...
If it helps, this is basic "ipctool" output for my board:
Hello,
I'm working on a small camera with hi3518ev200 chip and a wifi module connected to SDIO1. Original stock firmware is a LiteOS clone. I've managed to flash openipc on it, and after investigating both stock firmware and ipctool readouts it seems there are discrepancies in your SDIO1 mappings in EV20Xregs array.
According to "ipctool reginfo" almost all SDIO1_ pins correspond to pinmux register value "0x3", except SDIO1_CARD_POWER_EN which is 0x4. This seems wrong, my stock firmware sets all those values to 0x4. I've replicated that and after some more shenanigans with onboard MCU (which is connected to UART1 and controls PWR and RST pins for wifi) I've finally managed to make wifi card at least present itself on MMC bus (as SDIO_ID 0296:5347 which seems to be in kernel already as Wilc1000 but is NOT actually that card or very much compatible at all :-/).
Anyway, this is pinmux configuration which makes SDIO1_* pins work correctly (at least those used on my board, I'm not sure about SDIO1_CARD_DETECT, SDIO1_CWPR and SDIO1_CARD_POWER_EN but have no reason to doubt the stock firmware setting them right):
Some of these pins I've tested manually in GPIO mode and that seemed to work fine with pinmux reg 0x0, and the default power-on values are 0x1 which would point to RMII/EPHY also being correct, but I have no idea what exactly should be mapped to 0x2/0x3 values.
Is it possible perhaps to insert "UNKNOWN" as 0x3 in there so the SDIO1 pins are in correct position? It's cost me quite some time and frustration wondering why nothing works with original 0x3 values...
If it helps, this is basic "ipctool" output for my board:
Thanks a lot!
BR,
relghuar
The text was updated successfully, but these errors were encountered: