Last debian Image for XM

Hi,

Anyone can share the latest image for beagole board xM rec C1 ?

I want to setup it to download media into external hard disk

Monthy snapshots with directions here:

http://elinux.org/BeagleBoardDebian#Debian_.28jessie.29

Sorry, i don't really test the xM anymore, other then basic boot tests..

Regards,

Hi,

Anyone can share the latest image for beagole board xM rec C1 ?

I want to setup it to download media into external hard disk

Monthy snapshots with directions here:

http://elinux.org/BeagleBoardDebian#Debian_.28jessie.29

Sorry, i don’t really test the xM anymore, other then basic boot tests…

I created a simple console disk image at http://debian.beagleboard.org/images/beaglexm-debian-8.3-console-2016-02-11-2gb.img.xz.

If I get positive feedback, I will link from BeagleBoard.org/latest-images. I have not tested it myself yet.

Looks good, except i flashed it to a broken microsd card:

xzcat beaglexm-debian-8.3-console-2016-02-11-2gb.img.xz | sudo dd of=/dev/sde

U-Boot SPL 2016.01-00001-gc0bfce8 (Jan 25 2016 - 20:14:03)
Trying to boot from MMC
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 2016.01-00001-gc0bfce8 (Jan 25 2016 - 20:14:03 -0600), Build:
jenkins-github_Bootloader-Builder-325

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
No EEPROM on expansion board
OMAP die ID: 1701000e016830c49ff8000034680022Net: usb_ether
Error: usb_ether address not set.

Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
Checking for: /uEnv.txt ...
Checking for: /boot/uEnv.txt ...
260 bytes read in 46 ms (4.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.4.1-armv7-x5 ...
5793392 bytes read in 555 ms (10 MiB/s)
loading /boot/dtbs/4.4.1-armv7-x5/omap3-beagle-xm.dtb ...
108305 bytes read in 243 ms (434.6 KiB/s)
loading /boot/initrd.img-4.4.1-armv7-x5 ...
9777413 bytes read in 896 ms (10.4 MiB/s)
debug: [console=ttyO2,115200n8 root=/dev/mmcblk0p2 ro rootfstype=ext4
rootwait coherent_pool=1M quiet] ...
debug: [bootz 0x82000000 0x88080000:953105 0x88000000] ...
Kernel image @ 0x82000000 [ 0x000000 - 0x586670 ]
## Flattened Device Tree blob at 88000000
   Booting using the fdt blob at 0x88000000
   Loading Ramdisk to 8f6ac000, end 8ffff105 ... OK
   Loading Device Tree to 8f68e000, end 8f6ab710 ... OK

Starting kernel ...

[ 0.851165] platform 48058000.ssi-controller: Cannot lookup hwmod 'ssi'
[ 0.855285] of_amba_device_create(): amba_device_add() failed (-19)
for /etb@5401b000
[ 0.855438] of_amba_device_create(): amba_device_add() failed (-19)
for /etm@54010000
[ 4.842193] tfp410 encoder@0: failed to parse PD gpio
[ 4.842742] connector-dvi connector@0: failed to find video source
[ 4.897338] Error: Driver 'tfp410' is already registered, aborting...
[ 5.025207] ehci-omap 48064800.ehci: Can't get PHY device for port 1: -517
[ 5.148040] omap2_set_init_voltage: unable to find boot up OPP for
vdd_mpu_iva
[ 5.155700] omap2_set_init_voltage: unable to set vdd_mpu_iva
[ 5.161834] omap2_set_init_voltage: unable to find boot up OPP for vdd_core
[ 5.169128] omap2_set_init_voltage: unable to set vdd_core
Loading, please wait...
[ 7.181335] mmc0: card never left busy state
[ 7.185821] mmc0: error -110 whilst initialising SD card
Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
   - Check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/mmcblk0p2 does not exist. Dropping to a shell!
(initramfs)

"mmc0: error -110 whilst initialising SD card" this a bad microSD card.. :wink:

Regards,

This time with a good microsd card:

monitor alive via edid:

debian@arm:~$ cat /sys/class/drm/card0-DVI-D-1/edid | parse-edid
Checksum Correct

Section "Monitor"
Identifier "DELL 1707FP"
ModelName "DELL 1707FP"
VendorName "DEL"
# Monitor Manufactured week 48 of 2006
# EDID version 1.3
# Digital Display
DisplaySize 340 270
Gamma 2.20
Option "DPMS" "true"
Horizsync 30-81
VertRefresh 56-76
# Maximum pixel clock is 140MHz
#Not giving standard mode: 1152x864, 75Hz
#Not giving standard mode: 1280x1024, 60Hz
Modeline "Mode 0" +hsync +vsync
EndSection

usb:

debian@arm:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 005: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 002 Device 004: ID 0424:2504 Standard Microsystems Corp. USB 2.0 Hub
Bus 002 Device 003: ID 0424:ec00 Standard Microsystems Corp.
SMSC9512/9514 Fast Ethernet Adapter
Bus 002 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

ethernet:

debian@arm:~$ sudo ifconfig -a
eth0 Link encap:Ethernet HWaddr 3a:76:00:fb:79:d2
          inet addr:192.168.0.142 Bcast:192.168.0.255 Mask:255.255.255.0
          inet6 addr: fe80::3876:ff:fefb:79d2/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST DYNAMIC MTU:1500 Metric:1
          RX packets:29 errors:0 dropped:0 overruns:0 frame:0
          TX packets:61 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:3164 (3.0 KiB) TX bytes:10140 (9.9 KiB)

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:65536 Metric:1
          RX packets:160 errors:0 dropped:0 overruns:0 frame:0
          TX packets:160 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:12960 (12.6 KiB) TX bytes:12960 (12.6 KiB)

usb0 Link encap:Ethernet HWaddr 9a:b9:4c:c7:09:ef
          BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

debian@arm:~$ cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
  driver: cpufreq-dt
  CPUs which run at the same hardware frequency: 0
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 300 us.
  hardware limits: 300 MHz - 800 MHz
  available frequency steps: 300 MHz, 600 MHz, 800 MHz
  available cpufreq governors: conservative, ondemand, userspace,
powersave, performance
  current policy: frequency should be within 300 MHz and 800 MHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 300 MHz.
  cpufreq stats: 300 MHz:82.59%, 600 MHz:2.69%, 800 MHz:14.72% (41)

Sorry no 1Ghz, no one is really working on opp stuff for omap3's
anymore on mainline... (and our local hack doesn't work anymore..)

Regards,

Hi,

Anyone can share the latest image for beagole board xM rec C1 ?

I want to setup it to download media into external hard disk

Monthy snapshots with directions here:

http://elinux.org/BeagleBoardDebian#Debian_.28jessie.29

Sorry, i don't really test the xM anymore, other then basic boot tests..

I created a simple console disk image at
http://debian.beagleboard.org/images/beaglexm-debian-8.3-console-2016-02-11-2gb.img.xz.

If I get positive feedback, I will link from BeagleBoard.org - latest-images.
I have not tested it myself yet.

This time with a good microsd card:

This is good. It was built without a microSD card (script only). There is a bmap for it in the same path. I will push to latest-images and look at additions as requested.

I think the bmap will fail...

When last i tried bmap vs dd for pre-omap4 bootrom's, they were
failing to boot u-boot..

I'm tempted to dd /dev/random into the first MB before craeting the
first fat partition.. (just haven't tried this yet)..

As i think the bootrom get's stuck on something the bmap ignored..

Regards,