Hi Geert, Wolfram > > Magnus has my previous Lager board, so I can't try it today. > > I think my current board and previous board have different type of chip. > > Magnus will bring me my previous board tomorrow, so I will check it, > > and try your solution. > > The revision doesn't seem to be printed on the chip package, but it is > identified by the da9063 driver (CONFIG_REGULATOR_DA9063=y). > > My Koelsch has: > > da9063 6-0058: Device detected (chip-ID: 0x61, var-ID: 0x30) > > which corresponds to PMIC_DA9063_AD. > Magnus' Lager (remote access) has the same version. > > (after adding the missing pieces to DT) Magnus's Gose has: > > da9063 6-0058: Device detected (chip-ID: 0x61, var-ID: 0x50) > > which corresponds to PMIC_DA9063_BB. > > Which revision do you have? Thank you for your help. I found the hot-spot. The issue was not ES2.0 vs ES3.0, not DA9063 Type, not Hot/Cold boot, and not uboot version on my desk. It was dipswitch. I can reproduce this on Lager board now. If I OFF:ed on SW8 : 4bit (= MD21), kernel boot will be failed. It happened on both board ES2.0 : da9063 11-0058: Device detected (chip-ID: 0x61, var-ID: 0x50) ES3.0 : da9063 11-0058: Device detected (chip-ID: 0x61, var-ID: 0x30)
