raspberrypi cm3 v2019.07 not working
Hi,
I'm trying to run 2019.07 u-boot on raspberrypi cm3 module but I got no feedback on console. When used 2018.01 it boots fine. Probably I need to do git bisect but maybe someone have some idea or experience what can cause that. Thanks.
BR,
marek
On Tue, May 5, 2020 at 10:18 PM Belisko Marek marek.belisko@gmail.com wrote:
Hi,
I'm trying to run 2019.07 u-boot on raspberrypi cm3 module but I got no feedback on console. When used 2018.01 it boots fine. Probably I need to do git bisect but maybe someone have some idea or experience what can cause that. Thanks.
I give a try 2020.01 and I got only this: U-Boot 2020.01 (May 06 2020 - 20:09:45 +0000)
DRAM: 948 MiB RPI Compute Module 3 (0xa020a0)
I'll try to debug it and let you know.
BR,
marek
On Wed, May 6, 2020 at 11:02 PM Belisko Marek marek.belisko@gmail.com wrote:
On Tue, May 5, 2020 at 10:18 PM Belisko Marek marek.belisko@gmail.com wrote:
Hi,
I'm trying to run 2019.07 u-boot on raspberrypi cm3 module but I got no feedback on console. When used 2018.01 it boots fine. Probably I need to do git bisect but maybe someone have some idea or experience what can cause that. Thanks.
I give a try 2020.01 and I got only this: U-Boot 2020.01 (May 06 2020 - 20:09:45 +0000)
DRAM: 948 MiB RPI Compute Module 3 (0xa020a0)
I'll try to debug it and let you know.
Debug messages shows this: https://pastebin.com/2SwNzrb1
I tried to debug but I have no clue what is going one there.
Also u-boot 2019.07 is not working at all on cm3 due to this commit (after bisect when reverted u-boot start working again): 143256b353c4d2ad1cf5e5e63b38410188b35e49 - fdt: update bcm283x device tree sources to Linux 5.1-rc6 state
Any ideas hint how to resolve this issue? Thanks.
BR,
marek
-- as simple and primitive as possible
Marek Belisko - OPEN-NANDRA Freelance Developer
Ruska Nova Ves 219 | Presov, 08005 Slovak Republic Tel: +421 915 052 184 skype: marekwhite twitter: #opennandra web: http://open-nandra.com
BR,
marek
Hi Marek,
On 08/05/2020 21:52, Belisko Marek wrote:
On Wed, May 6, 2020 at 11:02 PM Belisko Marek marek.belisko@gmail.com wrote:
On Tue, May 5, 2020 at 10:18 PM Belisko Marek marek.belisko@gmail.com wrote:
Hi,
I'm trying to run 2019.07 u-boot on raspberrypi cm3 module but I got no feedback on console. When used 2018.01 it boots fine. Probably I need to do git bisect but maybe someone have some idea or experience what can cause that. Thanks.
I give a try 2020.01 and I got only this: U-Boot 2020.01 (May 06 2020 - 20:09:45 +0000)
DRAM: 948 MiB RPI Compute Module 3 (0xa020a0)
I'll try to debug it and let you know.
Debug messages shows this: https://pastebin.com/2SwNzrb1
I tried to debug but I have no clue what is going one there.
Also u-boot 2019.07 is not working at all on cm3 due to this commit (after bisect when reverted u-boot start working again): 143256b353c4d2ad1cf5e5e63b38410188b35e49 - fdt: update bcm283x device tree sources to Linux 5.1-rc6 state
Any ideas hint how to resolve this issue? Thanks.
Can you try to cherry-pick the following two patches to your tree: 5051377a0b ("arm: dts: bcm283x: Rename U-Boot file") 89e47e8eb6 ("fdt: fix bcm283x dm-pre-reloc definitions")
Regards, Matthias
Hi Matthias,
On Fri, May 8, 2020 at 11:28 PM Matthias Brugger mbrugger@suse.com wrote:
Hi Marek,
On 08/05/2020 21:52, Belisko Marek wrote:
On Wed, May 6, 2020 at 11:02 PM Belisko Marek marek.belisko@gmail.com wrote:
On Tue, May 5, 2020 at 10:18 PM Belisko Marek marek.belisko@gmail.com wrote:
Hi,
I'm trying to run 2019.07 u-boot on raspberrypi cm3 module but I got no feedback on console. When used 2018.01 it boots fine. Probably I need to do git bisect but maybe someone have some idea or experience what can cause that. Thanks.
I give a try 2020.01 and I got only this: U-Boot 2020.01 (May 06 2020 - 20:09:45 +0000)
DRAM: 948 MiB RPI Compute Module 3 (0xa020a0)
I'll try to debug it and let you know.
Debug messages shows this: https://pastebin.com/2SwNzrb1
I tried to debug but I have no clue what is going one there.
Also u-boot 2019.07 is not working at all on cm3 due to this commit (after bisect when reverted u-boot start working again): 143256b353c4d2ad1cf5e5e63b38410188b35e49 - fdt: update bcm283x device tree sources to Linux 5.1-rc6 state
Any ideas hint how to resolve this issue? Thanks.
Can you try to cherry-pick the following two patches to your tree: 5051377a0b ("arm: dts: bcm283x: Rename U-Boot file") 89e47e8eb6 ("fdt: fix bcm283x dm-pre-reloc definitions")
But those are present in 2020.01 and this version at least print something to console but stuck somewhere (pls see pastebin log with debug enabled) I prefer to run 2020.01 ;). Thanks.
Regards, Matthias
BR,
marek
On Fri, May 8, 2020 at 11:39 PM Belisko Marek marek.belisko@gmail.com wrote:
Hi Matthias,
On Fri, May 8, 2020 at 11:28 PM Matthias Brugger mbrugger@suse.com wrote:
Hi Marek,
On 08/05/2020 21:52, Belisko Marek wrote:
On Wed, May 6, 2020 at 11:02 PM Belisko Marek marek.belisko@gmail.com wrote:
On Tue, May 5, 2020 at 10:18 PM Belisko Marek marek.belisko@gmail.com wrote:
Hi,
I'm trying to run 2019.07 u-boot on raspberrypi cm3 module but I got no feedback on console. When used 2018.01 it boots fine. Probably I need to do git bisect but maybe someone have some idea or experience what can cause that. Thanks.
I give a try 2020.01 and I got only this: U-Boot 2020.01 (May 06 2020 - 20:09:45 +0000)
DRAM: 948 MiB RPI Compute Module 3 (0xa020a0)
I'll try to debug it and let you know.
Debug messages shows this: https://pastebin.com/2SwNzrb1
I tried to debug but I have no clue what is going one there.
Also u-boot 2019.07 is not working at all on cm3 due to this commit (after bisect when reverted u-boot start working again): 143256b353c4d2ad1cf5e5e63b38410188b35e49 - fdt: update bcm283x device tree sources to Linux 5.1-rc6 state
Any ideas hint how to resolve this issue? Thanks.
Can you try to cherry-pick the following two patches to your tree: 5051377a0b ("arm: dts: bcm283x: Rename U-Boot file") 89e47e8eb6 ("fdt: fix bcm283x dm-pre-reloc definitions")
But those are present in 2020.01 and this version at least print something to console but stuck somewhere (pls see pastebin log with debug enabled) I prefer to run 2020.01 ;). Thanks.
Any other stuff I can try to make it working in 2020.01? Could that be firmware issue somehow? Thanks.
Regards, Matthias
BR,
marek
BR,
marek
On 12/05/2020 11:15, Belisko Marek wrote:
On Fri, May 8, 2020 at 11:39 PM Belisko Marek marek.belisko@gmail.com wrote:
Hi Matthias,
On Fri, May 8, 2020 at 11:28 PM Matthias Brugger mbrugger@suse.com wrote:
Hi Marek,
On 08/05/2020 21:52, Belisko Marek wrote:
On Wed, May 6, 2020 at 11:02 PM Belisko Marek marek.belisko@gmail.com wrote:
On Tue, May 5, 2020 at 10:18 PM Belisko Marek marek.belisko@gmail.com wrote:
Hi,
I'm trying to run 2019.07 u-boot on raspberrypi cm3 module but I got no feedback on console. When used 2018.01 it boots fine. Probably I need to do git bisect but maybe someone have some idea or experience what can cause that. Thanks.
I give a try 2020.01 and I got only this: U-Boot 2020.01 (May 06 2020 - 20:09:45 +0000)
DRAM: 948 MiB RPI Compute Module 3 (0xa020a0)
I'll try to debug it and let you know.
Debug messages shows this: https://pastebin.com/2SwNzrb1
I tried to debug but I have no clue what is going one there.
Also u-boot 2019.07 is not working at all on cm3 due to this commit (after bisect when reverted u-boot start working again): 143256b353c4d2ad1cf5e5e63b38410188b35e49 - fdt: update bcm283x device tree sources to Linux 5.1-rc6 state
Any ideas hint how to resolve this issue? Thanks.
Can you try to cherry-pick the following two patches to your tree: 5051377a0b ("arm: dts: bcm283x: Rename U-Boot file") 89e47e8eb6 ("fdt: fix bcm283x dm-pre-reloc definitions")
But those are present in 2020.01 and this version at least print something to console but stuck somewhere (pls see pastebin log with debug enabled) I prefer to run 2020.01 ;). Thanks.
Any other stuff I can try to make it working in 2020.01? Could that be firmware issue somehow? Thanks.
Sorry I didn't realized that your first try was with 2020.01. I just confirmed that it acutually does not boot. As a shortcut, do you know which is the last working version of U-Boot?
Regards, Matthias
On Tue, May 12, 2020 at 12:51 PM Matthias Brugger mbrugger@suse.com wrote:
On 12/05/2020 11:15, Belisko Marek wrote:
On Fri, May 8, 2020 at 11:39 PM Belisko Marek marek.belisko@gmail.com wrote:
Hi Matthias,
On Fri, May 8, 2020 at 11:28 PM Matthias Brugger mbrugger@suse.com wrote:
Hi Marek,
On 08/05/2020 21:52, Belisko Marek wrote:
On Wed, May 6, 2020 at 11:02 PM Belisko Marek marek.belisko@gmail.com wrote:
On Tue, May 5, 2020 at 10:18 PM Belisko Marek marek.belisko@gmail.com wrote: > > Hi, > > I'm trying to run 2019.07 u-boot on raspberrypi cm3 module but I got > no feedback on console. When used 2018.01 it boots fine. Probably I > need to do git bisect but maybe someone have some idea or experience > what can cause that. Thanks. I give a try 2020.01 and I got only this: U-Boot 2020.01 (May 06 2020 - 20:09:45 +0000)
DRAM: 948 MiB RPI Compute Module 3 (0xa020a0)
I'll try to debug it and let you know.
Debug messages shows this: https://pastebin.com/2SwNzrb1
I tried to debug but I have no clue what is going one there.
Also u-boot 2019.07 is not working at all on cm3 due to this commit (after bisect when reverted u-boot start working again): 143256b353c4d2ad1cf5e5e63b38410188b35e49 - fdt: update bcm283x device tree sources to Linux 5.1-rc6 state
Any ideas hint how to resolve this issue? Thanks.
Can you try to cherry-pick the following two patches to your tree: 5051377a0b ("arm: dts: bcm283x: Rename U-Boot file") 89e47e8eb6 ("fdt: fix bcm283x dm-pre-reloc definitions")
But those are present in 2020.01 and this version at least print something to console but stuck somewhere (pls see pastebin log with debug enabled) I prefer to run 2020.01 ;). Thanks.
Any other stuff I can try to make it working in 2020.01? Could that be firmware issue somehow? Thanks.
Sorry I didn't realized that your first try was with 2020.01. I just confirmed that it acutually does not boot. As a shortcut, do you know which is the last working version of U-Boot?
v2019.07 with reverted commit : 143256b353c4d2ad1cf5e5e63b38410188b35e49 - fdt: update bcm283x device tree sources to Linux 5.1-rc6 state work fine. Without revert it shows anything on console. So something between 2019.07..2020.01 mus fix it partially ;)
Regards, Matthias
BR,
marek
On 12/05/2020 13:00, Belisko Marek wrote:
On Tue, May 12, 2020 at 12:51 PM Matthias Brugger mbrugger@suse.com wrote:
On 12/05/2020 11:15, Belisko Marek wrote:
On Fri, May 8, 2020 at 11:39 PM Belisko Marek marek.belisko@gmail.com wrote:
Hi Matthias,
On Fri, May 8, 2020 at 11:28 PM Matthias Brugger mbrugger@suse.com wrote:
Hi Marek,
On 08/05/2020 21:52, Belisko Marek wrote:
On Wed, May 6, 2020 at 11:02 PM Belisko Marek marek.belisko@gmail.com wrote: > > On Tue, May 5, 2020 at 10:18 PM Belisko Marek marek.belisko@gmail.com wrote: >> >> Hi, >> >> I'm trying to run 2019.07 u-boot on raspberrypi cm3 module but I got >> no feedback on console. When used 2018.01 it boots fine. Probably I >> need to do git bisect but maybe someone have some idea or experience >> what can cause that. Thanks. > I give a try 2020.01 and I got only this: > U-Boot 2020.01 (May 06 2020 - 20:09:45 +0000) > > DRAM: 948 MiB > RPI Compute Module 3 (0xa020a0) > > I'll try to debug it and let you know. Debug messages shows this: https://pastebin.com/2SwNzrb1
I tried to debug but I have no clue what is going one there.
Also u-boot 2019.07 is not working at all on cm3 due to this commit (after bisect when reverted u-boot start working again): 143256b353c4d2ad1cf5e5e63b38410188b35e49 - fdt: update bcm283x device tree sources to Linux 5.1-rc6 state
Any ideas hint how to resolve this issue? Thanks.
Can you try to cherry-pick the following two patches to your tree: 5051377a0b ("arm: dts: bcm283x: Rename U-Boot file") 89e47e8eb6 ("fdt: fix bcm283x dm-pre-reloc definitions")
But those are present in 2020.01 and this version at least print something to console but stuck somewhere (pls see pastebin log with debug enabled) I prefer to run 2020.01 ;). Thanks.
Any other stuff I can try to make it working in 2020.01? Could that be firmware issue somehow? Thanks.
Sorry I didn't realized that your first try was with 2020.01. I just confirmed that it acutually does not boot. As a shortcut, do you know which is the last working version of U-Boot?
v2019.07 with reverted commit : 143256b353c4d2ad1cf5e5e63b38410188b35e49 - fdt: update bcm283x device tree sources to Linux 5.1-rc6 state work fine. Without revert it shows anything on console. So something between 2019.07..2020.01 mus fix it partially ;)
I just tired v2020.04 and it works for me. Would you mind testing that on your end?
Do you have a hard dependency on v2020.01?
Regards, Matthias
On Tue, May 12, 2020 at 1:16 PM Matthias Brugger matthias.bgg@gmail.com wrote:
On 12/05/2020 13:00, Belisko Marek wrote:
On Tue, May 12, 2020 at 12:51 PM Matthias Brugger mbrugger@suse.com wrote:
On 12/05/2020 11:15, Belisko Marek wrote:
On Fri, May 8, 2020 at 11:39 PM Belisko Marek marek.belisko@gmail.com wrote:
Hi Matthias,
On Fri, May 8, 2020 at 11:28 PM Matthias Brugger mbrugger@suse.com wrote:
Hi Marek,
On 08/05/2020 21:52, Belisko Marek wrote: > On Wed, May 6, 2020 at 11:02 PM Belisko Marek marek.belisko@gmail.com wrote: >> >> On Tue, May 5, 2020 at 10:18 PM Belisko Marek marek.belisko@gmail.com wrote: >>> >>> Hi, >>> >>> I'm trying to run 2019.07 u-boot on raspberrypi cm3 module but I got >>> no feedback on console. When used 2018.01 it boots fine. Probably I >>> need to do git bisect but maybe someone have some idea or experience >>> what can cause that. Thanks. >> I give a try 2020.01 and I got only this: >> U-Boot 2020.01 (May 06 2020 - 20:09:45 +0000) >> >> DRAM: 948 MiB >> RPI Compute Module 3 (0xa020a0) >> >> I'll try to debug it and let you know. > Debug messages shows this: > https://pastebin.com/2SwNzrb1 > > I tried to debug but I have no clue what is going one there. > > Also u-boot 2019.07 is not working at all on cm3 due to this commit > (after bisect when reverted u-boot start working again): > 143256b353c4d2ad1cf5e5e63b38410188b35e49 - fdt: update bcm283x device > tree sources to Linux 5.1-rc6 state > > Any ideas hint how to resolve this issue? Thanks. >
Can you try to cherry-pick the following two patches to your tree: 5051377a0b ("arm: dts: bcm283x: Rename U-Boot file") 89e47e8eb6 ("fdt: fix bcm283x dm-pre-reloc definitions")
But those are present in 2020.01 and this version at least print something to console but stuck somewhere (pls see pastebin log with debug enabled) I prefer to run 2020.01 ;). Thanks.
Any other stuff I can try to make it working in 2020.01? Could that be firmware issue somehow? Thanks.
Sorry I didn't realized that your first try was with 2020.01. I just confirmed that it acutually does not boot. As a shortcut, do you know which is the last working version of U-Boot?
v2019.07 with reverted commit : 143256b353c4d2ad1cf5e5e63b38410188b35e49 - fdt: update bcm283x device tree sources to Linux 5.1-rc6 state work fine. Without revert it shows anything on console. So something between 2019.07..2020.01 mus fix it partially ;)
I just tired v2020.04 and it works for me. Would you mind testing that on your end?
OK I'll give a try and try to bisect between 2020.01 and 2020.04. I have dependency on 2020.01 as I integrate mender and then use this version.
Do you have a hard dependency on v2020.01?
Regards, Matthias
Thanks.
BR,
marek
On 12/05/2020 13:36, Belisko Marek wrote:
On Tue, May 12, 2020 at 1:16 PM Matthias Brugger matthias.bgg@gmail.com wrote:
On 12/05/2020 13:00, Belisko Marek wrote:
On Tue, May 12, 2020 at 12:51 PM Matthias Brugger mbrugger@suse.com wrote:
On 12/05/2020 11:15, Belisko Marek wrote:
On Fri, May 8, 2020 at 11:39 PM Belisko Marek marek.belisko@gmail.com wrote:
Hi Matthias,
On Fri, May 8, 2020 at 11:28 PM Matthias Brugger mbrugger@suse.com wrote: > > Hi Marek, > > On 08/05/2020 21:52, Belisko Marek wrote: >> On Wed, May 6, 2020 at 11:02 PM Belisko Marek marek.belisko@gmail.com wrote: >>> >>> On Tue, May 5, 2020 at 10:18 PM Belisko Marek marek.belisko@gmail.com wrote: >>>> >>>> Hi, >>>> >>>> I'm trying to run 2019.07 u-boot on raspberrypi cm3 module but I got >>>> no feedback on console. When used 2018.01 it boots fine. Probably I >>>> need to do git bisect but maybe someone have some idea or experience >>>> what can cause that. Thanks. >>> I give a try 2020.01 and I got only this: >>> U-Boot 2020.01 (May 06 2020 - 20:09:45 +0000) >>> >>> DRAM: 948 MiB >>> RPI Compute Module 3 (0xa020a0) >>> >>> I'll try to debug it and let you know. >> Debug messages shows this: >> https://pastebin.com/2SwNzrb1 >> >> I tried to debug but I have no clue what is going one there. >> >> Also u-boot 2019.07 is not working at all on cm3 due to this commit >> (after bisect when reverted u-boot start working again): >> 143256b353c4d2ad1cf5e5e63b38410188b35e49 - fdt: update bcm283x device >> tree sources to Linux 5.1-rc6 state >> >> Any ideas hint how to resolve this issue? Thanks. >> > > Can you try to cherry-pick the following two patches to your tree: > 5051377a0b ("arm: dts: bcm283x: Rename U-Boot file") > 89e47e8eb6 ("fdt: fix bcm283x dm-pre-reloc definitions") But those are present in 2020.01 and this version at least print something to console but stuck somewhere (pls see pastebin log with debug enabled) I prefer to run 2020.01 ;). Thanks.
Any other stuff I can try to make it working in 2020.01? Could that be firmware issue somehow? Thanks.
Sorry I didn't realized that your first try was with 2020.01. I just confirmed that it acutually does not boot. As a shortcut, do you know which is the last working version of U-Boot?
v2019.07 with reverted commit : 143256b353c4d2ad1cf5e5e63b38410188b35e49 - fdt: update bcm283x device tree sources to Linux 5.1-rc6 state work fine. Without revert it shows anything on console. So something between 2019.07..2020.01 mus fix it partially ;)
I just tired v2020.04 and it works for me. Would you mind testing that on your end?
OK I'll give a try and try to bisect between 2020.01 and 2020.04. I have dependency on 2020.01 as I integrate mender and then use this version.
I'm on that no need for you to do it.
Regards, Matthias
On 12/05/2020 13:39, Matthias Brugger wrote:
On 12/05/2020 13:36, Belisko Marek wrote:
On Tue, May 12, 2020 at 1:16 PM Matthias Brugger matthias.bgg@gmail.com wrote:
On 12/05/2020 13:00, Belisko Marek wrote:
On Tue, May 12, 2020 at 12:51 PM Matthias Brugger mbrugger@suse.com wrote:
On 12/05/2020 11:15, Belisko Marek wrote:
On Fri, May 8, 2020 at 11:39 PM Belisko Marek marek.belisko@gmail.com wrote: > > Hi Matthias, > > On Fri, May 8, 2020 at 11:28 PM Matthias Brugger mbrugger@suse.com wrote: >> >> Hi Marek, >> >> On 08/05/2020 21:52, Belisko Marek wrote: >>> On Wed, May 6, 2020 at 11:02 PM Belisko Marek marek.belisko@gmail.com wrote: >>>> >>>> On Tue, May 5, 2020 at 10:18 PM Belisko Marek marek.belisko@gmail.com wrote: >>>>> >>>>> Hi, >>>>> >>>>> I'm trying to run 2019.07 u-boot on raspberrypi cm3 module but I got >>>>> no feedback on console. When used 2018.01 it boots fine. Probably I >>>>> need to do git bisect but maybe someone have some idea or experience >>>>> what can cause that. Thanks. >>>> I give a try 2020.01 and I got only this: >>>> U-Boot 2020.01 (May 06 2020 - 20:09:45 +0000) >>>> >>>> DRAM: 948 MiB >>>> RPI Compute Module 3 (0xa020a0) >>>> >>>> I'll try to debug it and let you know. >>> Debug messages shows this: >>> https://pastebin.com/2SwNzrb1 >>> >>> I tried to debug but I have no clue what is going one there. >>> >>> Also u-boot 2019.07 is not working at all on cm3 due to this commit >>> (after bisect when reverted u-boot start working again): >>> 143256b353c4d2ad1cf5e5e63b38410188b35e49 - fdt: update bcm283x device >>> tree sources to Linux 5.1-rc6 state >>> >>> Any ideas hint how to resolve this issue? Thanks. >>> >> >> Can you try to cherry-pick the following two patches to your tree: >> 5051377a0b ("arm: dts: bcm283x: Rename U-Boot file") >> 89e47e8eb6 ("fdt: fix bcm283x dm-pre-reloc definitions") > But those are present in 2020.01 and this version at least print > something to console but stuck somewhere (pls see pastebin log with > debug enabled) > I prefer to run 2020.01 ;). Thanks. Any other stuff I can try to make it working in 2020.01? Could that be firmware issue somehow? Thanks.
Sorry I didn't realized that your first try was with 2020.01. I just confirmed that it acutually does not boot. As a shortcut, do you know which is the last working version of U-Boot?
v2019.07 with reverted commit : 143256b353c4d2ad1cf5e5e63b38410188b35e49 - fdt: update bcm283x device tree sources to Linux 5.1-rc6 state work fine. Without revert it shows anything on console. So something between 2019.07..2020.01 mus fix it partially ;)
I just tired v2020.04 and it works for me. Would you mind testing that on your end?
OK I'll give a try and try to bisect between 2020.01 and 2020.04. I have dependency on 2020.01 as I integrate mender and then use this version.
I'm on that no need for you to do it.
The result for me is: 7099d71d87 ("common: Drop mdm_init()")
which kind of makes no sense. Can you retry, I think I made a mistake somewhere in the process.
For reference here is my log:
$ git bisect log git bisect start # bad: [36fec02b1f90b92cf51ec531564f9284eae27ab4] Prepare v2020.04 git bisect bad 36fec02b1f90b92cf51ec531564f9284eae27ab4 # good: [0b0c6af38738f2c132cfd41a240889acaa031c8f] Prepare v2020.01 git bisect good 0b0c6af38738f2c132cfd41a240889acaa031c8f # good: [2f39ab1649caddf748ef1eff60c40fede5995ced] clock_imx8mq: Make frac_pll_init() static git bisect good 2f39ab1649caddf748ef1eff60c40fede5995ced # bad: [e6da32f243b3846e5c18183b8604b71ccb535a89] Merge tag 'ti-v2020.04-rc3' of https://gitlab.denx.de/u-boot/custodians/u-boot-ti git bisect bad e6da32f243b3846e5c18183b8604b71ccb535a89 # bad: [c95215a6ca1cc7bb53cc634159e222abc06fddff] Merge tag 'rpi-next-2020.04' of https://gitlab.denx.de/u-boot/custodians/u-boot-raspberrypi git bisect bad c95215a6ca1cc7bb53cc634159e222abc06fddff # bad: [d7b433e40b037733f47b83b8e2f385f91035924b] env: kconfig: Restrict rockchip env for MMC git bisect bad d7b433e40b037733f47b83b8e2f385f91035924b # bad: [6db7943b92f7a4b5858b6a68f137462ed0293e09] i2c: designware_i2c: Rename 'max' speed to 'high' speed git bisect bad 6db7943b92f7a4b5858b6a68f137462ed0293e09 # bad: [f32934916c65d3c26c5436b393d886fce8b9ab9f] common: Rename and move source() git bisect bad f32934916c65d3c26c5436b393d886fce8b9ab9f # bad: [ef20e5359bde42ad7e1aae8f0bf893dbca2ef2d0] common: Drop CONFIG_POST_STD/ALT_LIST git bisect bad ef20e5359bde42ad7e1aae8f0bf893dbca2ef2d0 # bad: [34971eec84e25773e29acfeeeae5ccb88f197ab4] common: Move do_tftpb() to net.h git bisect bad 34971eec84e25773e29acfeeeae5ccb88f197ab4 # bad: [9dfbc24459ccb0623c76f33b359e8fedb0e6d0a7] common: Move flash_perror() to flash.h git bisect bad 9dfbc24459ccb0623c76f33b359e8fedb0e6d0a7 # bad: [930c57ed9654f9fd53fe9bb0fc7d46d2e0317bbd] common: Move main_loop() to init.h git bisect bad 930c57ed9654f9fd53fe9bb0fc7d46d2e0317bbd # bad: [7099d71d87813f997b58a3d8107c3a615fd37669] common: Drop mdm_init() git bisect bad 7099d71d87813f997b58a3d8107c3a615fd37669 # first bad commit: [7099d71d87813f997b58a3d8107c3a615fd37669] common: Drop mdm_init()
Regards, Matthias
On Tue, May 12, 2020 at 1:51 PM Matthias Brugger mbrugger@suse.com wrote:
On 12/05/2020 13:39, Matthias Brugger wrote:
On 12/05/2020 13:36, Belisko Marek wrote:
On Tue, May 12, 2020 at 1:16 PM Matthias Brugger matthias.bgg@gmail.com wrote:
On 12/05/2020 13:00, Belisko Marek wrote:
On Tue, May 12, 2020 at 12:51 PM Matthias Brugger mbrugger@suse.com wrote:
On 12/05/2020 11:15, Belisko Marek wrote: > On Fri, May 8, 2020 at 11:39 PM Belisko Marek marek.belisko@gmail.com wrote: >> >> Hi Matthias, >> >> On Fri, May 8, 2020 at 11:28 PM Matthias Brugger mbrugger@suse.com wrote: >>> >>> Hi Marek, >>> >>> On 08/05/2020 21:52, Belisko Marek wrote: >>>> On Wed, May 6, 2020 at 11:02 PM Belisko Marek marek.belisko@gmail.com wrote: >>>>> >>>>> On Tue, May 5, 2020 at 10:18 PM Belisko Marek marek.belisko@gmail.com wrote: >>>>>> >>>>>> Hi, >>>>>> >>>>>> I'm trying to run 2019.07 u-boot on raspberrypi cm3 module but I got >>>>>> no feedback on console. When used 2018.01 it boots fine. Probably I >>>>>> need to do git bisect but maybe someone have some idea or experience >>>>>> what can cause that. Thanks. >>>>> I give a try 2020.01 and I got only this: >>>>> U-Boot 2020.01 (May 06 2020 - 20:09:45 +0000) >>>>> >>>>> DRAM: 948 MiB >>>>> RPI Compute Module 3 (0xa020a0) >>>>> >>>>> I'll try to debug it and let you know. >>>> Debug messages shows this: >>>> https://pastebin.com/2SwNzrb1 >>>> >>>> I tried to debug but I have no clue what is going one there. >>>> >>>> Also u-boot 2019.07 is not working at all on cm3 due to this commit >>>> (after bisect when reverted u-boot start working again): >>>> 143256b353c4d2ad1cf5e5e63b38410188b35e49 - fdt: update bcm283x device >>>> tree sources to Linux 5.1-rc6 state >>>> >>>> Any ideas hint how to resolve this issue? Thanks. >>>> >>> >>> Can you try to cherry-pick the following two patches to your tree: >>> 5051377a0b ("arm: dts: bcm283x: Rename U-Boot file") >>> 89e47e8eb6 ("fdt: fix bcm283x dm-pre-reloc definitions") >> But those are present in 2020.01 and this version at least print >> something to console but stuck somewhere (pls see pastebin log with >> debug enabled) >> I prefer to run 2020.01 ;). Thanks. > Any other stuff I can try to make it working in 2020.01? Could that be > firmware issue somehow? Thanks.
Sorry I didn't realized that your first try was with 2020.01. I just confirmed that it acutually does not boot. As a shortcut, do you know which is the last working version of U-Boot?
v2019.07 with reverted commit : 143256b353c4d2ad1cf5e5e63b38410188b35e49 - fdt: update bcm283x device tree sources to Linux 5.1-rc6 state work fine. Without revert it shows anything on console. So something between 2019.07..2020.01 mus fix it partially ;)
I just tired v2020.04 and it works for me. Would you mind testing that on your end?
OK I'll give a try and try to bisect between 2020.01 and 2020.04. I have dependency on 2020.01 as I integrate mender and then use this version.
I'm on that no need for you to do it.
The result for me is: 7099d71d87 ("common: Drop mdm_init()")
which kind of makes no sense. Can you retry, I think I made a mistake somewhere in the process.
For reference here is my log:
$ git bisect log git bisect start # bad: [36fec02b1f90b92cf51ec531564f9284eae27ab4] Prepare v2020.04 git bisect bad 36fec02b1f90b92cf51ec531564f9284eae27ab4 # good: [0b0c6af38738f2c132cfd41a240889acaa031c8f] Prepare v2020.01 git bisect good 0b0c6af38738f2c132cfd41a240889acaa031c8f # good: [2f39ab1649caddf748ef1eff60c40fede5995ced] clock_imx8mq: Make frac_pll_init() static git bisect good 2f39ab1649caddf748ef1eff60c40fede5995ced # bad: [e6da32f243b3846e5c18183b8604b71ccb535a89] Merge tag 'ti-v2020.04-rc3' of https://gitlab.denx.de/u-boot/custodians/u-boot-ti git bisect bad e6da32f243b3846e5c18183b8604b71ccb535a89 # bad: [c95215a6ca1cc7bb53cc634159e222abc06fddff] Merge tag 'rpi-next-2020.04' of https://gitlab.denx.de/u-boot/custodians/u-boot-raspberrypi git bisect bad c95215a6ca1cc7bb53cc634159e222abc06fddff # bad: [d7b433e40b037733f47b83b8e2f385f91035924b] env: kconfig: Restrict rockchip env for MMC git bisect bad d7b433e40b037733f47b83b8e2f385f91035924b # bad: [6db7943b92f7a4b5858b6a68f137462ed0293e09] i2c: designware_i2c: Rename 'max' speed to 'high' speed git bisect bad 6db7943b92f7a4b5858b6a68f137462ed0293e09 # bad: [f32934916c65d3c26c5436b393d886fce8b9ab9f] common: Rename and move source() git bisect bad f32934916c65d3c26c5436b393d886fce8b9ab9f # bad: [ef20e5359bde42ad7e1aae8f0bf893dbca2ef2d0] common: Drop CONFIG_POST_STD/ALT_LIST git bisect bad ef20e5359bde42ad7e1aae8f0bf893dbca2ef2d0 # bad: [34971eec84e25773e29acfeeeae5ccb88f197ab4] common: Move do_tftpb() to net.h git bisect bad 34971eec84e25773e29acfeeeae5ccb88f197ab4 # bad: [9dfbc24459ccb0623c76f33b359e8fedb0e6d0a7] common: Move flash_perror() to flash.h git bisect bad 9dfbc24459ccb0623c76f33b359e8fedb0e6d0a7 # bad: [930c57ed9654f9fd53fe9bb0fc7d46d2e0317bbd] common: Move main_loop() to init.h git bisect bad 930c57ed9654f9fd53fe9bb0fc7d46d2e0317bbd # bad: [7099d71d87813f997b58a3d8107c3a615fd37669] common: Drop mdm_init() git bisect bad 7099d71d87813f997b58a3d8107c3a615fd37669 # first bad commit: [7099d71d87813f997b58a3d8107c3a615fd37669] common: Drop mdm_init()
Found it. When apply : [29f7d05a347ab7a42577c67fdfb787ef91537302] dm: core: Move ofdata_to_platdata() call earlier on top of 2020.01 board boots fine. Thanks for any help ;).
Regards, Matthias
BR,
marek
participants (3)
-
Belisko Marek -
Matthias Brugger -
Matthias Brugger