Re: [beagleboard] Re: Invalid partition message during boot

[Jim Bell]

For posterity, I'm past this "** Invalid partition 2** ..." issue, though 
I'm not exactly sure how. I was using "make O=... install" instead of "make 
O=... zinstall"; also, I did another build on the kernel ("make O=..."). 

On Saturday, January 13, 2018 at 12:23:54 AM UTC-6, acheesehead wrote:
>
> Sorry Jim, forgot how I fixed this.
>
> On Sat, Jan 13, 2018 at 12:02 AM, Jim Bell  > wrote:
>
>> Please let us know what changes you made to your uEnv.txt file. I'm 
>> seeing the same symptom as above:
>> ** Invalid partition 2 **
>> ** Invalid partition 3 **
>> ** Invalid partition 4 **
>> ** Invalid partition 5 **
>> ** Invalid partition 6 **
>> ** Invalid partition 7 **
>>
>>
>> On Wednesday, February 8, 2017 at 2:21:40 PM UTC-6, acheesehead wrote:
>>>
>>> Got around that problem. My uEnv.txt file was wrong.
>>>
>>> On Wednesday, February 8, 2017 at 1:10:20 PM UTC-7, acheesehead wrote:

 I built Linux RT for a custom board based upon Beagleboard xM exactly 
 as in Robert C. Nelson's page 
 https://eewiki.net/display/linuxonarm/BeagleBoard.


 -- 
>> For more options, visit http://beagleboard.org/discuss
>> --- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "BeagleBoard" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/beagleboard/9gbDy70lnKw/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> beagleboard...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beagleboard/7ab8b604-aa6d-4138-9383-f462ce7aad37%40googlegroups.com
>>  
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> John 3:16
> IN GOD WE TRUST!!!
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/47187487-cb85-4632-be66-9b82b85295fa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Invalid partition message during boot

[Todd Peterson]

Sorry Jim, forgot how I fixed this.

On Sat, Jan 13, 2018 at 12:02 AM, Jim Bell  wrote:

> Please let us know what changes you made to your uEnv.txt file. I'm seeing
> the same symptom as above:
> ** Invalid partition 2 **
> ** Invalid partition 3 **
> ** Invalid partition 4 **
> ** Invalid partition 5 **
> ** Invalid partition 6 **
> ** Invalid partition 7 **
>
>
> On Wednesday, February 8, 2017 at 2:21:40 PM UTC-6, acheesehead wrote:
>>
>> Got around that problem. My uEnv.txt file was wrong.
>>
>> On Wednesday, February 8, 2017 at 1:10:20 PM UTC-7, acheesehead wrote:
>>>
>>> I built Linux RT for a custom board based upon Beagleboard xM exactly as
>>> in Robert C. Nelson's page https://eewiki.net/displa
>>> y/linuxonarm/BeagleBoard.
>>>
>>>
>>> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/beagleboard/9gbDy70lnKw/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/beagleboard/7ab8b604-aa6d-4138-9383-f462ce7aad37%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
John 3:16
IN GOD WE TRUST!!!

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAMSLvQyPn%3D0uBREw-4kW2%3DgXRudj%3DGR30f3p490h9_O0fP1wPg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Invalid partition message during boot

[Jim Bell]

Please let us know what changes you made to your uEnv.txt file. I'm seeing 
the same symptom as above:
** Invalid partition 2 **
** Invalid partition 3 **
** Invalid partition 4 **
** Invalid partition 5 **
** Invalid partition 6 **
** Invalid partition 7 **


On Wednesday, February 8, 2017 at 2:21:40 PM UTC-6, acheesehead wrote:
>
> Got around that problem. My uEnv.txt file was wrong.
>
> On Wednesday, February 8, 2017 at 1:10:20 PM UTC-7, acheesehead wrote:
>>
>> I built Linux RT for a custom board based upon Beagleboard xM exactly as 
>> in Robert C. Nelson's page 
>> https://eewiki.net/display/linuxonarm/BeagleBoard.
>>
>>
>>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/7ab8b604-aa6d-4138-9383-f462ce7aad37%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Invalid partition message during boot

[acheesehead]

Robert,

My u-boot mod somehow got wiped. Put it back in and recompiled. I'm still 
having a problem with the device tree (which I don't know enough about):

U-Boot 2017.03-rc1-dirty (Feb 08 2017 - 15:00:15 -0700)

OMAP3630/3730-GP ES1.2, CPU-OPP2, L3-200MHz, Max CPU Clock 1 GHz
OMAP3 Beagle board + LPDDR/NAND
I2C:   ready
DRAM:  256 MiB
NAND:  0 MiB
MMC:   OMAP SD/MMC: 0
*** Warning - readenv() failed, using default environment

Beagle xM Rev C
No EEPROM on expansion board
No EEPROM on expansion board
OMAP die ID: 715e00029ff80156083e0501c01d
Net:   usb_ether
Error: usb_ether address not set.

Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
Checking for: /uEnv.txt ...
Checking for: /boot/uEnv.txt ...
53 bytes read in 7 ms (6.8 KiB/s)
Loaded environment from /boot/uEnv.txt
Checking if uname_r is set in /boot/uEnv.txt...
Running uname_boot ...
loading /boot/vmlinuz-4.9.7-armv7-rt-x4 ...
6435000 bytes read in 499 ms (12.3 MiB/s)
loading /boot/dtbs/4.9.7-armv7-rt-x4/omap3-beagle-xm.dtb ...
100032 bytes read in 233 ms (418.9 KiB/s)
debug: [console=ttyO2,115200n8 root=/dev/mmcblk0p2 ro rootfstype=ext4 
rootwait] ...
debug: [bootz 0x8200 - 0x8800] ...
## Flattened Device Tree blob at 8800
   Booting using the fdt blob at 0x8800
   Loading Device Tree to 8ffe4000, end 86bf ... OK
fdt_find_or_add_subnode: memory: FDT_ERR_BADSTRUCTURE
ERROR: arch-specific fdt fixup failed
 - must RESET the board to recover.

FDT creation failed! hanging...### ERROR ### Please RESET the board ###


On Wednesday, February 8, 2017 at 1:39:01 PM UTC-7, RobertCNelson wrote:
>
> On Wed, Feb 8, 2017 at 2:33 PM, acheesehead  > wrote: 
> > Boots ok on Beagleboard xM, but hangs on our custom board. 
> > 
> > U-Boot SPL 2017.03-rc1-dirty (Feb 04 2017 - 12:10:18) 
> > Trying to boot from MMC1 
> > SPL: Please implement spl_start_uboot() for your board 
> > SPL: Direct Linux boot not active! 
> > reading u-boot.img 
> > reading u-boot.img 
> > 
> > 
> > U-Boot 2017.03-rc1-dirty (Feb 04 2017 - 12:10:18 -0700) 
> > 
> > OMAP3630/3730-GP ES1.2, CPU-OPP2, L3-200MHz, Max CPU Clock 1 GHz 
> > OMAP3 Beagle board + LPDDR/NAND 
>
> > Beagle Rev Ax/Bx 
>
> > loading /boot/dtbs/4.9.7-armv7-rt-x4/omap3-beagle.dtb ... 
>
> Why is your board going down the Beagle classic route? 
>
> Take a look at the gpio's used for id on the xM C, you messed those up 
> when you built your custom board.. 
>
> Regards, 
>
> -- 
> Robert Nelson 
> https://rcn-ee.com/ 
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/cefbf17e-aea8-4eff-b8fd-48aca613d1f2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Invalid partition message during boot

[Robert Nelson]

On Wed, Feb 8, 2017 at 2:33 PM, acheesehead  wrote:
> Boots ok on Beagleboard xM, but hangs on our custom board.
>
> U-Boot SPL 2017.03-rc1-dirty (Feb 04 2017 - 12:10:18)
> Trying to boot from MMC1
> SPL: Please implement spl_start_uboot() for your board
> SPL: Direct Linux boot not active!
> reading u-boot.img
> reading u-boot.img
>
>
> U-Boot 2017.03-rc1-dirty (Feb 04 2017 - 12:10:18 -0700)
>
> OMAP3630/3730-GP ES1.2, CPU-OPP2, L3-200MHz, Max CPU Clock 1 GHz
> OMAP3 Beagle board + LPDDR/NAND

> Beagle Rev Ax/Bx

> loading /boot/dtbs/4.9.7-armv7-rt-x4/omap3-beagle.dtb ...

Why is your board going down the Beagle classic route?

Take a look at the gpio's used for id on the xM C, you messed those up
when you built your custom board..

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYhBOBZ8Rk4ZH%2Bj3NPwQLuqvZTCy3JvzyLJTk90GiQx25w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Invalid partition message during boot

[acheesehead]

Boots ok on Beagleboard xM, but hangs on our custom board.

U-Boot SPL 2017.03-rc1-dirty (Feb 04 2017 - 12:10:18)
Trying to boot from MMC1
SPL: Please implement spl_start_uboot() for your board
SPL: Direct Linux boot not active!
reading u-boot.img
reading u-boot.img


U-Boot 2017.03-rc1-dirty (Feb 04 2017 - 12:10:18 -0700)

OMAP3630/3730-GP ES1.2, CPU-OPP2, L3-200MHz, Max CPU Clock 1 GHz
OMAP3 Beagle board + LPDDR/NAND
I2C:   ready
DRAM:  256 MiB
NAND:  0 MiB
MMC:   OMAP SD/MMC: 0
*** Warning - readenv() failed, using default environment

Beagle Rev Ax/Bx
No EEPROM on expansion board
No EEPROM on expansion board
OMAP die ID: 715e00029ff80156083e0501c01d
Net:   usb_ether
Error: usb_ether address not set.

Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
Checking for: /uEnv.txt ...
Checking for: /boot/uEnv.txt ...
26 bytes read in 7 ms (2.9 KiB/s)
Loaded environment from /boot/uEnv.txt
Checking if uname_r is set in /boot/uEnv.txt...
Running uname_boot ...
loading /boot/vmlinuz-4.9.7-armv7-rt-x4 ...
6435000 bytes read in 499 ms (12.3 MiB/s)
loading /boot/dtbs/4.9.7-armv7-rt-x4/omap3-beagle.dtb ...
98676 bytes read in 210 ms (458 KiB/s)
debug: [console=ttyO2,115200n8 root=/dev/mmcblk0p2 ro rootfstype=ext4 
rootwait musb_hdrc.fifo_mode=5] ...
debug: [bootz 0x8200 - 0x8800] ...
## Flattened Device Tree blob at 8800
   Booting using the fdt blob at 0x8800
   Loading Device Tree to 8ffe4000, end 8173 ... OK
fdt_find_or_add_subnode: memory: FDT_ERR_BADSTRUCTURE
ERROR: arch-specific fdt fixup failed
 - must RESET the board to recover.

FDT creation failed! hanging...### ERROR ### Please RESET the board ###


On Wednesday, February 8, 2017 at 1:10:20 PM UTC-7, acheesehead wrote:
>
> I built Linux RT for a custom board based upon Beagleboard xM exactly as 
> in Robert C. Nelson's page 
> https://eewiki.net/display/linuxonarm/BeagleBoard.
>
> Here is what I get during boot, tried on a real Beagleboard xM and get the 
> same behavior. The booting stops at a u-boot prompt.
>
> U-Boot SPL 2017.03-rc1-dirty (Feb 04 2017 - 12:10:18)
> Trying to boot from MMC1
> SPL: Please implement spl_start_uboot() for your board
> SPL: Direct Linux boot not active!
> reading u-boot.img
> reading u-boot.img
>
>
> U-Boot 2017.03-rc1-dirty (Feb 04 2017 - 12:10:18 -0700)
>
> OMAP3630/3730-GP ES1.2, CPU-OPP2, L3-200MHz, Max CPU Clock 1 GHz
> OMAP3 Beagle board + LPDDR/NAND
> I2C:   ready
> DRAM:  512 MiB
> NAND:  0 MiB
> MMC:   OMAP SD/MMC: 0
> *** Warning - readenv() failed, using default environment
>
> Beagle xM Rev C
> No EEPROM on expansion board
> No EEPROM on expansion board
> OMAP die ID: 101000229ff8016830c319017022
> Net:   usb_ether
> Error: usb_ether address not set.
>
> Hit any key to stop autoboot:  0
> switch to partitions #0, OK
> mmc0 is current device
> Scanning mmc 0:1...
> switch to partitions #0, OK
> mmc0 is current device
> SD/MMC found on device 0
> Checking for: /uEnv.txt ...
> Checking for: /boot/uEnv.txt ...
> 26 bytes read in 7 ms (2.9 KiB/s)
> Loaded environment from /boot/uEnv.txt
> Checking if uname_r is set in /boot/uEnv.txt...
> Running uname_boot ...
> ** Invalid partition 3 **
> ** Invalid partition 4 **
> ** Invalid partition 5 **
> ** Invalid partition 6 **
> ** Invalid partition 7 **
> =>
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/b03e465d-a7b4-4016-a8db-a3480f160973%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Invalid partition message during boot

[acheesehead]

Got around that problem. My uEnv.txt file was wrong.

On Wednesday, February 8, 2017 at 1:10:20 PM UTC-7, acheesehead wrote:
>
> I built Linux RT for a custom board based upon Beagleboard xM exactly as 
> in Robert C. Nelson's page 
> https://eewiki.net/display/linuxonarm/BeagleBoard.
>
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/640d76a5-d182-46e2-808a-6f9aca1dc86d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.