On Tue, Sep 21, 2021 at 4:54 PM Suman Anna <s-anna@xxxxxx> wrote: > > On 9/21/21 3:29 PM, Drew Fustini wrote: > > On Tue, Sep 21, 2021 at 9:09 AM Suman Anna <s-anna@xxxxxx> wrote: > >> > >> Hi Matti, Tony, > >> > >> On 9/21/21 2:47 AM, Tony Lindgren wrote: > >>> * Matti Vaittinen <mazziesaccount@xxxxxxxxx> [210920 08:23]: > >>>> Finally, adding the udelay(100); (as Tony suggested) at the end of the > >>>> omap_reset_deassert() did make the oops go away even when pruss_tm was > >>>> enabled. I don't know what would be a proper fix though. > >> > >> I have been able to boot v5.15-rc1 just fine on my BBB without any additional > >> changes [1]. > >> > >> May I ask what is your BBB board version? My board is rev.A5C. > > > > That rev is quite old [1]. Would you be able to try a Rev C? It has > > been in production since around 2014 with the move from 2GB to 4GB > > eMMC. > > I don't have any rev.C boards handy to try. > > I am curious to see if there is some correlation between failures and board > versions. I see that there is a minor processor change to AM3358 from rev.B > onwards compared to the AM3359 that I would have on my board. PRU-ICSS IP would > be present and supported on both though. Rev B vs Rev C shouldn't matter.. I don't think I even have a Rev "B".. A6A, B, to C* was done very quickly at CIrcuitCo at that time.. https://elinux.org/Beagleboard:BeagleBoneBlack#Revision_B "This version moves to the AM3358BZCZ100 processor as we are no longer able to get the limited production version of the AM3359AZCZ100." I'm assuming the AM3358 had the pru enabled.. Regards, -- Robert Nelson https://rcn-ee.com/
