Custom Board doesnt run with Angström Image

83 views
Skip to first unread message

El Smiedro

unread,
Mar 7, 2018, 5:13:27 AM3/7/18
to BeagleBoard
Hello community,

I use the Angström Image v2012.12 - Kernel 3.8.13 with U-Boot SPL 2013.04-dirty (Jun 19 2013 - 09:57:14) and I can login on my BBB.

I also try to run a custom board similar to the BBB. I only removed the HDMI part and use a MT41K256M16TW-107 ITP DDR3. When I try to boot, it stops while running the kernel:

Code hier eingeben...
U
-Boot SPL 2013.04-dirty (Jun 19 2013 - 09:57:14)
musb
-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb
-hdrc: MHDRC RTL version 2.0
musb
-hdrc: setup fifo_mode 4
musb
-hdrc: 28/31 max ep, 16384/16384 memory
USB
Peripheral mode controller at 47401000 using PIO, IRQ 0
musb
-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb
-hdrc: MHDRC RTL version 2.0
musb
-hdrc: setup fifo_mode 4
musb
-hdrc: 28/31 max ep, 16384/16384 memory
USB
Host mode controller at 47401800 using PIO, IRQ 0
OMAP SD
/MMC: 0
reading u
-boot.img
reading u
-boot.img


U
-Boot 2013.04-dirty (Jun 19 2013 - 09:57:14)

I2C
:   ready
DRAM
:  512 MiB
WARNING
: Caches not enabled
NAND
:  No NAND device found!!!
0 MiB
MMC
:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
*** Warning - readenv() failed, using default environment

musb
-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb
-hdrc: MHDRC RTL version 2.0
musb
-hdrc: setup fifo_mode 4
musb
-hdrc: 28/31 max ep, 16384/16384 memory
USB
Peripheral mode controller at 47401000 using PIO, IRQ 0
musb
-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb
-hdrc: MHDRC RTL version 2.0
musb
-hdrc: setup fifo_mode 4
musb
-hdrc: 28/31 max ep, 16384/16384 memory
USB
Host mode controller at 47401800 using PIO, IRQ 0
Net:   <ethaddr> not set. Validating first E-fuse MAC
cpsw
, usb_ether
Hit any key to stop autoboot:  0
gpio
: pin 53 (gpio 53) value is 1
mmc0
is current device
micro SD card found
mmc0
is current device
gpio
: pin 54 (gpio 54) value is 1
SD
/MMC found on device 0
reading uEnv
.txt
33 bytes read in 3 ms (10.7 KiB/s)
Loaded environment from uEnv.txt
Importing environment from mmc ...
gpio
: pin 55 (gpio 55) value is 1
4270840 bytes read in 770 ms (5.3 MiB/s)
gpio
: pin 56 (gpio 56) value is 1
24129 bytes read in 49 ms (480.5 KiB/s)
Booting from mmc ...
## Booting kernel from Legacy Image at 80007fc0 ...
   
Image Name:   Angstrom/3.8.13/beaglebone
   
Image Type:   ARM Linux Kernel Image (uncompressed)
   
Data Size:    4270776 Bytes = 4.1 MiB
   
Load Address: 80008000
   
Entry Point:  80008000
   
Verifying Checksum ... OK
## Flattened Device Tree blob at 80f80000
   
Booting using the fdt blob at 0x80f80000
   XIP
Kernel Image ... OK
OK
   
Using Device Tree in place at 80f80000, end 80f88e40

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.194444] omap2_mbox_probe: platform not supported
[    0.204990] tps65217-bl tps65217-bl: no platform data provided
[    0.281512] bone-capemgr bone_capemgr.8: slot #0: No cape found
[    0.318618] bone-capemgr bone_capemgr.8: slot #1: No cape found
[    0.355726] bone-capemgr bone_capemgr.8: slot #2: No cape found
[    0.392836] bone-capemgr bone_capemgr.8: slot #3: No cape found
[    0.412862] bone-capemgr bone_capemgr.8: slot #6: BB-BONELT-HDMIN conflict P8                                   .45 (#5:BB-BONELT-HDMI)
[    0.422487] bone-capemgr bone_capemgr.8: slot #6: Failed verification
[    0.429266] bone-capemgr bone_capemgr.8: loader: failed to load slot-6 BB-BON                                   ELT-HDMIN:00A0 (prio 2)
[    0.451930] omap_hsmmc mmc.4: of_parse_phandle_with_args of 'reset' failed
[    0.516301] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by                                    44e10800.pinmux; cannot claim for gpio-leds.7
[    0.528016] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.7) status -22
[    0.535334] pinctrl-single 44e10800.pinmux: could not request pin 21 on devic                                   e pinctrl-single
[    0.568496] dummy 0-0034: Error -121 writing to cec:0xff
[    0.574309] tda998x 0-0070: Error -121 reading from 0xa
[    0.580038] tda998x 0-0070: Error -121 writing to 0xa
[    0.637061] tda998x 0-0070: Error -121 reading from 0xa
[    0.642639] tda998x 0-0070: Error -121 writing to 0xa
[    0.699595] tda998x 0-0070: Error -121 reading from 0x1
[    0.705172] tda998x 0-0070: Error -121 writing to 0x1
[    0.710564] tda998x 0-0070: Error -121 reading from 0x1
[    0.716136] tda998x 0-0070: Error -121 writing to 0x1
[    0.721524] tda998x 0-0070: Error -121 writing to REG_CURPAGE
[    0.727640] tda998x 0-0070: Error -121 writing to 0x200
[    0.733211] tda998x 0-0070: Error -121 writing to 0x201
[    0.738781] tda998x 0-0070: Error -121 writing to 0x202
[    0.744377] tda998x 0-0070: Error -121 writing to 0x203
[    0.749949] tda998x 0-0070: Error -121 writing to 0x204
[    0.755520] tda998x 0-0070: Error -121 writing to 0x205
[    0.761090] tda998x 0-0070: Error -121 writing to 0x20e
[    0.766661] tda998x 0-0070: Error -121 writing to 0x211
[    0.772233] tda998x 0-0070: Error -121 writing to 0x207
[    0.777803] tda998x 0-0070: Error -121 writing to 0x208
[    0.783372] tda998x 0-0070: Error -121 writing to 0x209
[    0.788942] tda998x 0-0070: Error -121 writing to 0x20a
[    0.794514] tda998x 0-0070: Error -121 writing to 0x206
[    0.800084] tda998x 0-0070: Error -121 writing to REG_CURPAGE
[    0.806199] tda998x 0-0070: Error -121 reading from 0x0
[    0.811770] tda998x 0-0070: Error -121 reading from 0x2
[    0.817608] tilcdc 4830e000.fb: no encoders/connectors found
[    0.823568] tilcdc 4830e000.fb: failed to initialize mode setting



Could the different RAM be the reason for this? Could anybody give an advice to get it run?
Thank you very much.

Best regards
Eric

Jeff Andich

unread,
Mar 7, 2018, 9:43:09 AM3/7/18
to BeagleBoard
I just did a 10 second google and it appears like tda998x is related to HDMI which you pulled from your board.

Just a couple of basic questions:

1) Did you remove the HDMI from either/both the u-boot pinmux and/or the cape manager?

2) If you start with a console image, does this yield the same result?  

I'm assuming that the console image doesn't access the HDMI port, but I DID see what appeared to be plain text appear on the HDMI port before X-windows started up on an LXQT image, so I could be mistaken..

El Smiedro

unread,
Mar 7, 2018, 10:59:47 AM3/7/18
to BeagleBoard


Am Mittwoch, 7. März 2018 15:43:09 UTC+1 schrieb Jeff Andich:
I just did a 10 second google and it appears like tda998x is related to HDMI which you pulled from your board.

Just a couple of basic questions:

1) Did you remove the HDMI from either/both the u-boot pinmux and/or the cape manager?

2) If you start with a console image, does this yield the same result?  

I'm assuming that the console image doesn't access the HDMI port, but I DID see what appeared to be plain text appear on the HDMI port before X-windows started up on an LXQT image, so I could be mistaken..



 Thank you for your fast reply.
I didnt remove anything. I only download this image: https://s3.amazonaws.com/angstrom/demo/beaglebone/Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.12-beaglebone-2013.06.20.img.xz from BeagleBoard.org and put it on my sd-card.
I'm new to this topic and tried to build an own uboot and linux kernel with the BBB configuration. But they stopped after the RAM-check. Then I noticed, that my NAND is not properly connected because of a hardware issue. I assume that it check for the NAND and stops, because it cant find it. Then I tried the angström image from beagleboard.org. But I cant edit it. Is there a way to edit it with the uEnv.txt or do you now where I can disable the NAND-check in a current uboot?
Thank you

evilwulfie

unread,
Mar 7, 2018, 11:05:01 AM3/7/18
to beagl...@googlegroups.com
Do yourself a favor dont use Angstrom It has no support
development has stopped

Use debian. We have Excellent support here when using a modern OS
--
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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/0809a984-8a20-49f7-bcdc-e67520a57165%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Robert Nelson

unread,
Mar 7, 2018, 11:10:23 AM3/7/18
to Beagle Board
> Thank you for your fast reply.
> I didnt remove anything. I only download this image:

"I also try to run a custom board similar to the BBB. I only removed
the HDMI part and use a MT41K256M16TW-107 ITP DDR3. When I try to
boot, it stops while running the kernel:"

YOU removed the HDMI..


> https://s3.amazonaws.com/angstrom/demo/beaglebone/Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.12-beaglebone-2013.06.20.img.xz
> from BeagleBoard.org and put it on my sd-card.
> I'm new to this topic and tried to build an own uboot and linux kernel with
> the BBB configuration. But they stopped after the RAM-check. Then I noticed,
> that my NAND is not properly connected because of a hardware issue. I assume
> that it check for the NAND and stops, because it cant find it. Then I tried
> the angström image from beagleboard.org. But I cant edit it. Is there a way
> to edit it with the uEnv.txt or do you now where I can disable the
> NAND-check in a current uboot?

What Nand?

Anywho, it's 2018, that 2012 image is EOL...

Regards,

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

El Smiedro

unread,
Mar 7, 2018, 11:40:52 AM3/7/18
to BeagleBoard


I use a custom board similar similar to the BBB but without the HDMI part, and a different RAM. with NAND I mean the eMMC on MMC1.
I tried the Debian Image9.3, but it stops after the RAM:

CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
U
-Boot SPL 2018.01-00002-g9aa111a004 (Jan 20 2018 - 12:45:29)
Trying to boot from MMC1


U
-Boot 2018.01-00002-g9aa111a004 (Jan 20 2018 - 12:45:29 -0600), Build: jenkins-github_Bootloader-Builder-32

CPU  
: AM335X-GP rev 2.1

I2C
:   ready
DRAM
:  512 MiB

I programmed the EEPROM like the one from the BBB. Is ist stop because of the missing eMMC on MMC1?

Thank you all for your advices.
 

Eric Schm.

unread,
Mar 9, 2018, 2:49:51 AM3/9/18
to BeagleBoard
I tried to build my own MLO and uboot.img with this commands:
- make CROSS_COMPILE=arm-linux-gnueabihf- distclean
- make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- am335x_boneblack_defconfig
- make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j4

I suppose that I have to build a custom MLO and uboot.img and put it on the boot partition. But after flashing the Debian Image9.3 I cant find a boot partition. And the only MLO and uboot.img I could find was under /opt/backup/uboot/
Could someone give an advise how I could boot the uboot?

Robert Nelson

unread,
Mar 9, 2018, 10:07:21 AM3/9/18
to Beagle Board

Eric Schm.

unread,
Mar 11, 2018, 1:42:53 PM3/11/18
to BeagleBoard

Thank you for the link.
I guess thats there is a check for the emmc in the uboot when I use:
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- am335x_boneblack_defconfig
Is that right? Do you know in which file I could disable it?
Thank you for your help

evilwulfie

unread,
Mar 11, 2018, 2:05:57 PM3/11/18
to beagl...@googlegroups.com
Do the current images load capes DTBO files automatically when a proper
eeprom is detected?

uname -r
4.14.20-ti-r36


OR do we have to just load them in /boot/Uenv.txt

Be nice to take some of the configuration and automate things.

Robert Nelson

unread,
Mar 11, 2018, 3:17:50 PM3/11/18
to Beagle Board, evilwulfie
It does as long as your version of u-boot in the eMMC isn't ancient..

https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays

Robert Nelson

unread,
Mar 11, 2018, 3:21:54 PM3/11/18
to Beagle Board, evilwulfie
Oh sorry, i forgot our previous conversation:

https://groups.google.com/d/msg/beagleboard/kpKoeZf_yJ4/tuD9lFw-DgAJ

you don't want to update the eMMC..

So my solution doesn't work for you.
Reply all
Reply to author
Forward
0 new messages