element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      • Japan
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Vietnam
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
BeagleBoard
  • Products
  • Dev Tools
  • Single-Board Computers
  • BeagleBoard
  • More
  • Cancel
BeagleBoard
Forum Do I have a bad BB-AI? Suggestions Welcome
  • Blog
  • Forum
  • Documents
  • Quiz
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join BeagleBoard to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • Replies 9 replies
  • Subscribers 102 subscribers
  • Views 2100 views
  • Users 0 members are here
  • bb-ai
  • bbb
Related

Do I have a bad BB-AI? Suggestions Welcome

mp2100
mp2100 over 5 years ago

I've had my BB-AI a couple weeks, and I'm running from the on board eMMC with debian 9.9 just fine, The tidl examples work.  But I wanted to flash the newer 'buster' image.  It does not work.  I read all the good advice from here:

BeagleBone AI SD card boot

 

I tried 3 different images downloaded.  I tried 4 different SD cards, one 8 GB (no name brand), one 16 GB (PNY brand), two 32 GB (both Kingston brand).  Used balena etcher, linux dd, win32 flasher.  All said they were successful but nothing would boot on my BB-AI.  OK I said, the good people on e14 will ask me a bunch of questions, what do I need to do to be ready?  OK, I should read the boot messages on the serial debug UART. . . . 

Read  sjmill01 informative guide to the BB-AI

Read shabaz getting started guide,

BeagleBone AI (BB-AI) - Getting Started

Great but I don't have a JST-ZH cable, and it'll take a while to get one.  So I pulled apart what I had, an old CD-ROM to sound card cable, hot glued the loose sockets together at something close to the required 1.5mm pitch and plug it into my FTDI board.  Amazingly it worked.

 

Now for my question, do I have a bad board?  I see voltage errors in the debug messages.  I did switch power supplies.  I was using a generic USB-C 3 amp power supply, so I tried my raspberry Pi 4 official 3 amp power supply, same errors on boot up.  Do I have a damaged SD slot?

 

Here's boot up dump:

 

[  255.631173] reboot: Restarting system

 

U-Boot 2019.07-rc4-00001-g607b5b738b (Jul 06 2019 - 21:01:15 -0500), Build: jenkins-github_Bootloader-Builder-127

 

CPU  : DRA752-GP ES2.0

Model: BeagleBoard.org BeagleBone AI

Board: BeagleBone AI REV A

DRAM:  1 GiB

MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1

CTRL_CORE_PAD_I2C1_SDA:    0x00060000

CTRL_CORE_PAD_I2C1_SCL:    0x00060000

CTRL_CORE_PAD_GPMC_A0:     0x00060007

CTRL_CORE_PAD_GPMC_A1:     0x00060007

CTRL_CORE_PAD_VIN2A_D4:    0x0005000f

CTRL_CORE_PAD_VIN2A_D5:    0x0005000f

CM_L4PER_GPIO7_CLKCTRL:    0x00000001

CM_L4PER_I2C1_CLKCTRL:     0x00000002

CM_L4PER_I2C4_CLKCTRL:     0x00000002

CM_L4PER_L4_PER1_CLKCTRL   0x00000001

PM_L4PER_I2C1_WKDEP        0x0000b000

RM_L4PER_I2C1_CONTEXT      0x00000002

PM_L4PER_I2C4_WKDEP        0x0000b000

RM_L4PER_I2C4_CONTEXT      0x00000001

BeagleBone: cape eeprom: i2c_probe: 0x54

Checking (ret 1 bus works) I2C1 bus. ret 1

Checking (ret 1 bus works) I2C4 bus. ret 1

BeagleBone: cape eeprom: i2c_probe: 0x55

Checking (ret 1 bus works) I2C1 bus. ret 1

Checking (ret 1 bus works) I2C4 bus. ret 1

BeagleBone: cape eeprom: i2c_probe: 0x56

Checking (ret 1 bus works) I2C1 bus. ret 1

Checking (ret 1 bus works) I2C4 bus. ret 1

BeagleBone: cape eeprom: i2c_probe: 0x57

Checking (ret 1 bus works) I2C1 bus. ret 1

Checking (ret 1 bus works) I2C4 bus. ret 1

Net:

Warning: ethernet@48484000 using MAC address from ROM

eth0: ethernet@48484000

Press SPACE to abort autoboot in 1 seconds

usb_boot is currently disabled

scsi_boot is currently disabled

Card did not respond to voltage select!

Card did not respond to voltage select!

Card did not respond to voltage select!

switch to partitions #0, OK

mmc1(part 0) is current device

 

Partition Map for MMC device 1  --   Partition Type: DOS

 

Part    Start Sector    Num Sectors     UUID            Type

  1     8192            30613504        d27d9455-01     83 Boot

Scanning mmc device 1

Checking for: /uEnv.txt ...

Checking for: /boot/uEnv.txt ...

603 bytes read in 1 ms (588.9 KiB/s)

Loaded environment from /boot/uEnv.txt

Checking if uname_r is set in /boot/uEnv.txt ...

debug: [uname_r=4.14.108-ti-r134] ...

loading /boot/vmlinuz-4.14.108-ti-r134 ...

9717736 bytes read in 219 ms (42.3 MiB/s)

loading /boot/dtbs/4.14.108-ti-r134/am5729-beagleboneai.dtb ...

150333 bytes read in 4 ms (35.8 MiB/s)

uboot_overlays: add [enable_uboot_overlays=1] to /boot/uEnv.txt to enable...

loading /boot/initrd.img-4.14.108-ti-r134 ...

4905353 bytes read in 111 ms (42.1 MiB/s)

debug: [console=ttyS0,115200n8 root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 rng_core.default_quality=100 quiet] ...

debug: [bootz 0x82000000 0x88080000:4ad989 0x88000000] ...

## Flattened Device Tree blob at 88000000

   Booting using the fdt blob at 0x88000000

   Loading Ramdisk to 8fb52000, end 8ffff989 ... OK

   Loading Device Tree to 8fb2a000, end 8fb51b3c ... OK

 

Starting kernel ...

 

[    0.002593] /cpus/cpu@0 missing clock-frequency property

[    0.002616] /cpus/cpu@1 missing clock-frequency property

[    0.409209] omap-mailbox 4a0f4000.mailbox: no available mbox devices found

[    0.409279] omap-mailbox 4883a000.mailbox: no available mbox devices found

[    0.409343] omap-mailbox 4883c000.mailbox: no available mbox devices found

[    0.409406] omap-mailbox 4883e000.mailbox: no available mbox devices found

[    0.410067] omap-mailbox 48844000.mailbox: no available mbox devices found

[    0.410133] omap-mailbox 48846000.mailbox: no available mbox devices found

[    0.410196] omap-mailbox 4885e000.mailbox: no available mbox devices found

[    0.410258] omap-mailbox 48860000.mailbox: no available mbox devices found

[    0.410320] omap-mailbox 48862000.mailbox: no available mbox devices found

[    0.410382] omap-mailbox 48864000.mailbox: no available mbox devices found

[    0.410444] omap-mailbox 48802000.mailbox: no available mbox devices found

[    0.864339] sdhci-omap 4809c000.mmc: failed to set system capabilities

[    0.871583] sdhci-omap 480b4000.mmc: failed to set system capabilities

[    0.881628] tpd12s015 encoder@0: failed to find video source

[    0.887626] connector-hdmi connector@0: failed to find video source

[    1.014288] dwc3 488d0000.usb: failed to initialize core

[    1.048839] omap_voltage_late_init: Voltage driver support not added

[    1.170035] sdhci-omap 4809c000.mmc: no pinctrl state for ddr_1_8v mode

[    1.176755] sdhci-omap 4809c000.mmc: no pinctrl state for hs200_1_8v mode

rootfs: clean, 134076/958464 files, 1041142/3826688 blocks

[    9.826748] cpu cpu0: _get_optimal_vdd_voltage: Failed optimized voltage match for 860000

         Starting Authorization Manager...

[  OK  ] Started Authorization Manager.

         Starting Disk Manager...

[  OK  ] Started Disk Manager.

[  OK  ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.

[  OK  ] Found device /dev/ttyS0.

[  OK  ] Started Serial Getty on ttyS0.

 

Debian GNU/Linux 9 beaglebone ttyS0

 

BeagleBoard.org Debian Image 2019-08-03

Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian

default username:password is [debian:temppwd]

 

beaglebone login:

  • Sign in to reply
  • Cancel

Top Replies

  • shabaz
    shabaz over 5 years ago +1
    Hi Allen, I just powered up my BB-AI with a Pi 4 power supply (3A). this is the serial console output I see: U-Boot 2019.07-rc4-00001-g607b5b738b (Jul 06 2019 - 21:01:15 -0500), Build: jenkins-github_Bootloader…
Parents
  • mp2100
    mp2100 over 5 years ago

    I just noticed, I left the serial cable connected to putty, and this error is coming in regularly.  Doesn't look good.

     

     

    debian@beaglebone:~$ [82233.002673] cpu cpu0: _get_optimal_vdd_voltage: Failed optimized voltage match for 860000

    [82254.634889] cpu cpu0: _get_optimal_vdd_voltage: Failed optimized voltage match for 860000

    [82258.507341] cpu cpu0: _get_optimal_vdd_voltage: Failed optimized voltage match for 860000

    [82263.402884] cpu cpu0: _get_optimal_vdd_voltage: Failed optimized voltage match for 860000

    [82267.274752] cpu cpu0: _get_optimal_vdd_voltage: Failed optimized voltage match for 860000

    [82270.642746] cpu cpu0: _get_optimal_vdd_voltage: Failed optimized voltage match for 860000

    [82278.602738] cpu cpu0: _get_optimal_vdd_voltage: Failed optimized voltage match for 860000

    [82283.467002] cpu cpu0: _get_optimal_vdd_voltage: Failed optimized voltage match for 860000

    [82287.338765] cpu cpu0: _get_optimal_vdd_voltage: Failed optimized voltage match for 860000

    [82290.699019] cpu cpu0: _get_optimal_vdd_voltage: Failed optimized voltage match for 860000

    [82296.859068] cpu cpu0: _get_optimal_vdd_voltage: Failed optimized voltage match for 860000

    [82300.974901] cpu cpu0: _get_optimal_vdd_voltage: Failed optimized voltage match for 860000

    [82307.402982] cpu cpu0: _get_optimal_vdd_voltage: Failed optimized voltage match for 860000

    [82313.326939] cpu cpu0: _get_optimal_vdd_voltage: Failed optimized voltage match for 860000

    [82319.251009] cpu cpu0: _get_optimal_vdd_voltage: Failed optimized voltage match for 860000

    [82323.371188] cpu cpu0: _get_optimal_vdd_voltage: Failed optimized voltage match for 860000

    [

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • mp2100
    mp2100 over 5 years ago

    I just noticed, I left the serial cable connected to putty, and this error is coming in regularly.  Doesn't look good.

     

     

    debian@beaglebone:~$ [82233.002673] cpu cpu0: _get_optimal_vdd_voltage: Failed optimized voltage match for 860000

    [82254.634889] cpu cpu0: _get_optimal_vdd_voltage: Failed optimized voltage match for 860000

    [82258.507341] cpu cpu0: _get_optimal_vdd_voltage: Failed optimized voltage match for 860000

    [82263.402884] cpu cpu0: _get_optimal_vdd_voltage: Failed optimized voltage match for 860000

    [82267.274752] cpu cpu0: _get_optimal_vdd_voltage: Failed optimized voltage match for 860000

    [82270.642746] cpu cpu0: _get_optimal_vdd_voltage: Failed optimized voltage match for 860000

    [82278.602738] cpu cpu0: _get_optimal_vdd_voltage: Failed optimized voltage match for 860000

    [82283.467002] cpu cpu0: _get_optimal_vdd_voltage: Failed optimized voltage match for 860000

    [82287.338765] cpu cpu0: _get_optimal_vdd_voltage: Failed optimized voltage match for 860000

    [82290.699019] cpu cpu0: _get_optimal_vdd_voltage: Failed optimized voltage match for 860000

    [82296.859068] cpu cpu0: _get_optimal_vdd_voltage: Failed optimized voltage match for 860000

    [82300.974901] cpu cpu0: _get_optimal_vdd_voltage: Failed optimized voltage match for 860000

    [82307.402982] cpu cpu0: _get_optimal_vdd_voltage: Failed optimized voltage match for 860000

    [82313.326939] cpu cpu0: _get_optimal_vdd_voltage: Failed optimized voltage match for 860000

    [82319.251009] cpu cpu0: _get_optimal_vdd_voltage: Failed optimized voltage match for 860000

    [82323.371188] cpu cpu0: _get_optimal_vdd_voltage: Failed optimized voltage match for 860000

    [

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Children
No Data
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2026 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube