Skip to first unread message
Rodrigo Such
Nov 8, 2015, 5:25:38 PM11/8/15
to BeagleBoard
Hello everybody!
I'm just starting to learn embedded linux on my beagleboard-XM rev C.
I'm trying to do everything from scratch. So I downloaded the latest versions of U-boot and Linux kernel and compiled them. I'm using the following versions:
U-boot, release 2015-10
Kernel 4.2.5
I've compiled the u-boot using these commands:
$ make omap3_beagle_defconfig
$ make CROSS_COMPILE=arm-linux-gnueabi-
I've compiled the linux kernel and device tree using these commands:
make ARCH=arm omap2plus_defconfig
make -j4 ARCH=arm CROSS_COMPILE=arm-linux-gnueabi-
Everything has compiled normally, with no errors.
Here is the uEnv.txt file that I'm using:
kernel_file=zImage
loadzimage=load mmc ${mmcdev}:${mmcpart} ${loadaddr} ${kernel_file}
loadfdt=load mmc ${mmcdev}:${mmcpart} ${fdtaddr} ${fdtfile}
console=ttyO2,115200n8
optargs="debug init=/etc/preinit"
mmcroot=/dev/mmcblk0p2 rw
mmcrootfstype=ext2 rootwait
rootfstype=${mmcrootfstype} ${optargs}
mmcargs=setenv bootargs console=${console} root=${mmcroot} ${mmcrootfstype} verbose debug
uenvcmd=run loadzimage; run loadfdt; run mmcargs; bootz ${loadaddr} - ${fdtaddr}
At the end, I've put it all together, in my boot partition of SdCard and tried to boot my beagle. (I know I'm missing the filesystem. I'm trying to boot the kernel at first)
Here is the message I got:
U-Boot SPL 2015.10 (Nov 08 2015 - 16:49:19)
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 2015.10 (Nov 08 2015 - 16:49:19 -0200)
OMAP36XX/37XX-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
Die ID #29e000029ff80000016842c91601001a
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
gpio: pin 173 (gpio 173) value is 0
gpio: pin 4 (gpio 4) value is 0
SD/MMC found on device 0
reading uEnv.txt
472 bytes read in 3 ms (153.3 KiB/s)
Loaded environment from uEnv.txt
Importing environment from mmc ...
Running uenvcmd ...
reading zImage
3464752 bytes read in 222 ms (14.9 MiB/s)
reading omap3-beagle-xm.dtb
63200 bytes read in 11 ms (5.5 MiB/s)
Kernel image @ 0x80200000 [ 0x000000 - 0x34de30 ]
data abort
pc : [<9ff6ea24>] lr : [<9ff6ea75>]
reloc pc : [<80111a24>] lr : [<80111a75>]
sp : 9ef3ca50 ip : 8054de30 fp : 00000003
r10: 00000002 r9 : 9ef3ced0 r8 : 9ffa3604
r7 : 9ffa3600 r6 : 00000000 r5 : 9ffa359c r4 : 9ef4450c
r3 : 00000002 r2 : 9ffa359c r1 : 9ef4450c r0 : 00000000
Flags: nZcv IRQs off FIQs off Mode SVC_32
Resetting CPU ...
resetting ...
And this boot process repeats over and over...
Im I doing something wrong? Everywhere I looked for information about how to create a system from scratch, uses an older version from kernel, and normally uses uImage instead zImage... Is this the problem?
It would be great to get some help... I'm trying to do this from myself from 2 weeks but had no success...
Ps: I have attached the files I wrote in the SdCard and the log messages.
Tks in advance!
Rodrigo Such
I'm just starting to learn embedded linux on my beagleboard-XM rev C.
I'm trying to do everything from scratch. So I downloaded the latest versions of U-boot and Linux kernel and compiled them. I'm using the following versions:
U-boot, release 2015-10
Kernel 4.2.5
I've compiled the u-boot using these commands:
$ make omap3_beagle_defconfig
$ make CROSS_COMPILE=arm-linux-gnueabi-
I've compiled the linux kernel and device tree using these commands:
make ARCH=arm omap2plus_defconfig
make -j4 ARCH=arm CROSS_COMPILE=arm-linux-gnueabi-
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- dtbs
Here is the uEnv.txt file that I'm using:
kernel_file=zImage
loadzimage=load mmc ${mmcdev}:${mmcpart} ${loadaddr} ${kernel_file}
loadfdt=load mmc ${mmcdev}:${mmcpart} ${fdtaddr} ${fdtfile}
console=ttyO2,115200n8
optargs="debug init=/etc/preinit"
mmcroot=/dev/mmcblk0p2 rw
mmcrootfstype=ext2 rootwait
rootfstype=${mmcrootfstype} ${optargs}
mmcargs=setenv bootargs console=${console} root=${mmcroot} ${mmcrootfstype} verbose debug
uenvcmd=run loadzimage; run loadfdt; run mmcargs; bootz ${loadaddr} - ${fdtaddr}
At the end, I've put it all together, in my boot partition of SdCard and tried to boot my beagle. (I know I'm missing the filesystem. I'm trying to boot the kernel at first)
Here is the message I got:
U-Boot SPL 2015.10 (Nov 08 2015 - 16:49:19)
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 2015.10 (Nov 08 2015 - 16:49:19 -0200)
OMAP36XX/37XX-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
Die ID #29e000029ff80000016842c91601001a
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
gpio: pin 173 (gpio 173) value is 0
gpio: pin 4 (gpio 4) value is 0
SD/MMC found on device 0
reading uEnv.txt
472 bytes read in 3 ms (153.3 KiB/s)
Loaded environment from uEnv.txt
Importing environment from mmc ...
Running uenvcmd ...
reading zImage
3464752 bytes read in 222 ms (14.9 MiB/s)
reading omap3-beagle-xm.dtb
63200 bytes read in 11 ms (5.5 MiB/s)
Kernel image @ 0x80200000 [ 0x000000 - 0x34de30 ]
data abort
pc : [<9ff6ea24>] lr : [<9ff6ea75>]
reloc pc : [<80111a24>] lr : [<80111a75>]
sp : 9ef3ca50 ip : 8054de30 fp : 00000003
r10: 00000002 r9 : 9ef3ced0 r8 : 9ffa3604
r7 : 9ffa3600 r6 : 00000000 r5 : 9ffa359c r4 : 9ef4450c
r3 : 00000002 r2 : 9ffa359c r1 : 9ef4450c r0 : 00000000
Flags: nZcv IRQs off FIQs off Mode SVC_32
Resetting CPU ...
resetting ...
And this boot process repeats over and over...
Im I doing something wrong? Everywhere I looked for information about how to create a system from scratch, uses an older version from kernel, and normally uses uImage instead zImage... Is this the problem?
It would be great to get some help... I'm trying to do this from myself from 2 weeks but had no success...
Ps: I have attached the files I wrote in the SdCard and the log messages.
Tks in advance!
Rodrigo Such
Robert Nelson
Nov 8, 2015, 5:43:21 PM11/8/15
to Beagle Board
http://git.denx.de/?p=u-boot.git;a=commit;h=c139b5ff0999ec3d44a02ebdb623a92e5782e53e
Regards,
--
Robert Nelson
https://rcn-ee.com/
Rodrigo Such
Nov 8, 2015, 6:00:55 PM11/8/15
to BeagleBoard
Hi Robert!
I've just applied this commit but it is still not working. The problem has changed. The boot starts, the message "Starting the kernel ..." is printed, but then it stops.
Here is the log:
U-Boot SPL 2015.10 (Nov 08 2015 - 20:52:16)
I've just applied this commit but it is still not working. The problem has changed. The boot starts, the message "Starting the kernel ..." is printed, but then it stops.
Here is the log:
U-Boot SPL 2015.10 (Nov 08 2015 - 20:52:16)
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 2015.10 (Nov 08 2015 - 20:52:16 -0200)
OMAP36XX/37XX-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
Die ID #29e000029ff80000016842c91601001a
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
gpio: pin 173 (gpio 173) value is 0
gpio: pin 4 (gpio 4) value is 0
SD/MMC found on device 0
reading uEnv.txt
472 bytes read in 3 ms (153.3 KiB/s)
Loaded environment from uEnv.txt
Importing environment from mmc ...
Running uenvcmd ...
reading zImage
3464752 bytes read in 223 ms (14.8 MiB/s)
reading omap3-beagle-xm.dtb
63200 bytes read in 11 ms (5.5 MiB/s)
Kernel image @ 0x80200000 [ 0x000000 - 0x34de30 ]
## Flattened Device Tree blob at 80f80000
Booting using the fdt blob at 0x80f80000
Using Device Tree in place at 80f80000, end 80f926df
Starting kernel ...
Anything else?
Tks
Rodrigo Such
Booting using the fdt blob at 0x80f80000
Using Device Tree in place at 80f80000, end 80f926df
Starting kernel ...
Anything else?
Tks
Rodrigo Such
Robert Nelson
Nov 8, 2015, 6:05:18 PM11/8/15
to Beagle Board
relatively new kernel.. Your dtb is too fat, thus overwritting your
kernel in memory..
Use:
loadaddr=0x82000000
fdtaddr=0x88000000
rdaddr=0x88080000
Rodrigo Such
Nov 8, 2015, 6:22:12 PM11/8/15
to beagl...@googlegroups.com
Nice Robert!
It worked!! Thank you so much!!
Sorry, could you please help me once more? What does these parameters
did? I'm not sure if I understood....
Rodrigo Such
> --
> 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/Ejg4zgVkWWU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
It worked!! Thank you so much!!
Sorry, could you please help me once more? What does these parameters
did? I'm not sure if I understood....
Rodrigo Such
> 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/Ejg4zgVkWWU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
Robert Nelson
Nov 8, 2015, 6:38:45 PM11/8/15
to Beagle Board
On Sun, Nov 8, 2015 at 5:21 PM, Rodrigo Such <rodri...@gmail.com> wrote:
> Nice Robert!
>
> It worked!! Thank you so much!!
> Sorry, could you please help me once more? What does these parameters
> did? I'm not sure if I understood....
http://git.denx.de/?p=u-boot.git;a=blob;f=include/configs/ti_armv7_common.h;hb=HEAD#l40
> Nice Robert!
>
> It worked!! Thank you so much!!
> Sorry, could you please help me once more? What does these parameters
> did? I'm not sure if I understood....
Rodrigo Such
Nov 8, 2015, 7:03:01 PM11/8/15
to BeagleBoard
Thanks!!
Rodrigo Such
Rodrigo Such
Reply all
Reply to author
Forward
0 new messages