devSCK and devSDA are GPIO device IDs. They can be either the GPIOs of the SoC itself, or of any of a number of RTL8231 GPIO expanders. But in principle the API is so abstracted that it could also be the GPIOs of an RTL8231 expander chip connected to a secondary SoC slaved via SPI to the primary SoC.
Some of this functionality (anything that does not involve a secondary SoC) is available through using the right &gpio reference. This can be &gpio0, which is the SoC itself, or &gpio1, which should be the RTL8231 expander chip.
This sounds as if the checksum in the header of the image for the actual image data is not what u-boot on your device expects. It could be that a different algorithm is used or that a seed is used with the normal crc algorithm. The first thing you should do is compare the header of the original image or a firmware update image with the one produced by you in openwrt. You can use the mkimage tool to check the checksums. The u-boot sources under tools contain the header description.
You will probably then need to analyzer how the u- boot on you router calculates the checksum. Load the flash image of u-boot into ghidra load address is b4000000 which is the same as 84000000. Find the reference in the code to the error string. Figure out how the algorithm works or at least disable the checksum check. @obi is a magician with ghidra, maybe he can help.
Hi Alfa, i have a similar switch (dgs-1210-24p)... i assume you run the switch 24/7? did you ever encounter any heat problems? i assume the cooling fans are also off?
mine are all-time off when booted by openwrt, and i try to get them running because i have the concern that the swithc eventually will overheat
Well, thats the issue I also have.
You can use a multimer or logic analyzer and you will see that one of the I2C pins on the LM63 package itself is floating, like its missing a pull-up.
But if you just use it as a GPIO then it can be toggled just fine.
Hi, i have used dgs-1210-28p F2 revision (realtek ic) for a long time with all ports default vlan conf.
It has passive cooling.There were no cooler fan on it and it has normal heat during switching process.
Did you try to enable fan controller if there is a way..
Looks like it, no idea what the stock FW does about it because the whole LM63 configuration is missing from GPL.
Even in the stock FW, it sometimes fails finding the LM63 and only after a reboot it will succeed configuring it for the fans to work
The datasheet actually claims that there should be internal pull-ups available. At least on certain pins but dependent on resp. mode configured. Rather confusing really.
The pins that have internal pull-up/down resistors, are the bootstrapping pins. Basically to make sure the device will power on in a certain default state (MIIM/MDIO device with address 0x1f). These pull-ups do work, since I relied on them when testing my RTL8231 driver on a modified board (pull-down or floating address pin). 75kΩ is quite a weak pull-up though; any current draw over 17µA and you won't meet the high-level threshold anymore.