debian: 2014-12-19 beta image for a beta board....

Hello!

Just in case Santa happened to deliver a few more x15 beta board's,
you guys might want to something to boot.. Right?

wget https://rcn-ee.net/rootfs/bb.org/testing/2014-12-19/lxqt/bbx15-debian-jessie-lxqt-armhf-2014-12-19-2gb.img.xz

(yes i made a mistake with the bootloader in the 2014-12-19 *.img..)

wget https://rcn-ee.net/deb/tools/beagle_x15/MLO-beagle_x15-v2015.01-rc4-r5
wget https://rcn-ee.net/deb/tools/beagle_x15/u-boot-beagle_x15-v2015.01-rc4-r5.img

(a "fixed" image will follow in a day or two..)

Assuming:

export DISK=/dev/sdf

unxz bbx15-debian-jessie-lxqt-armhf-2014-12-19-2gb.img.xz

sudo dd if=./bbx15-debian-jessie-lxqt-armhf-2014-12-19-2gb.img of=${DISK}
sync
sudo dd if=MLO-beagle_x15-v2015.01-rc4-r5 of=${DISK} count=1 seek=1
conv=notrunc bs=128k
sudo dd if=u-boot-beagle_x15-v2015.01-rc4-r5.img of=${DISK} count=2
seek=1 conv=notrunc bs=384k
sync

2GB [x]
HDMI video [x]
HDMI audio [ ]
USB [x]

By default it's running a branch based off of ti's 3.14.x, but you
test mainline to via:

sudo apt-get update
sudo apt-get install linux-image-3.19.0-rc2-armv7-lpae-x0
sudo reboot

Regards,

Here's a fixed image just for new-years..

https://rcn-ee.net/rootfs/bb.org/testing/2014-12-31/lxqt/bbx15-debian-jessie-lxqt-armhf-2014-12-31-2gb.img.xz

Regards,

Cool, the fixed memory on the beta board fixed the issue i was seeing
on the alpha with loading.. "dra7-ipu2-fw.xem4" (Android video
acceleration codec's).. On the alpha, it would just hardlock...

debian@beaglebone:~$ dmesg | grep ipu2
[ 0.000000] Reserved memory: initialized node ipu2_cma@95800000,
compatible id shared-dma-pool
[ 0.751792] platform 55020000.ipu: assigned reserved memory node
ipu2_cma@95800000
[ 5.003312] remoteproc5: Booting fw image dra7-ipu2-fw.xem4, size 3365836

sudo tar xf /opt/source/x15/ducati_full_jacinto6evm.tgz -C /lib/firmware/

Regards,

Shell is "root@beaglebone" :wink: maybe BeagleBoard-X15?

Works: Alpha board
2GB [x]
Line Audio out/in [x] [1]
HDMI video [x]
HDMI audio [x][2]
USB[x]
RTC[x][3]
SATA[x][4]
Palmas power button[x][5]
emmc[x][6]

[1]
Setup:
- Connect LINEOUT of your PC to LINEIN of X15 and LINEOUT of
X15 to a speaker.

amixer -c1 sset 'PCM' 119
amixer -c1 sset 'Line DAC' 108
amixer -c1 sset 'Left PGA Mixer Mic3L' unmute
amixer -c1 sset 'Right PGA Mixer Mic3R' unmute
amixer -c1 sset 'PGA' 10

Record:
arecord -Dplughw:1,0 -fcd -d10 -c2 > /tmp/music.wav

Playback:
aplay -Dplughw:1,0 /tmp/music.wav

[2] aplay -Dplughw:0,0 test.wav
[3] http://slexy.org/view/s2bc1bt6AN (uses rtctest)
[4] basic dd tests to /dev/sda1 (for the esata drive)
[5] evtest /dev/input/event0
[6] basic dd tests to /dev/mmcblk1p1 (for emmc)

ofcourse, sgx acceleration might be good to integrate later on.. :wink:

2014-12-31-171924_1920x1080_scrot.png

yep - we had noticed this before on Alphas :frowning: Betas are good.

^^ correction: this is a newer beta board.. :frowning:

Hello!

Just in case Santa happened to deliver a few more x15 beta board's,
you guys might want to something to boot.. Right?

wget https://rcn-ee.net/rootfs/bb.org/testing/2014-12-19/lxqt/bbx15-debian-jessie-lxqt-armhf-2014-12-19-2gb.img.xz

(yes i made a mistake with the bootloader in the 2014-12-19 *.img..)

wget https://rcn-ee.net/deb/tools/beagle_x15/MLO-beagle_x15-v2015.01-rc4-r5
wget https://rcn-ee.net/deb/tools/beagle_x15/u-boot-beagle_x15-v2015.01-rc4-r5.img

(a "fixed" image will follow in a day or two..)

Assuming:

export DISK=/dev/sdf

unxz bbx15-debian-jessie-lxqt-armhf-2014-12-19-2gb.img.xz

sudo dd if=./bbx15-debian-jessie-lxqt-armhf-2014-12-19-2gb.img of=${DISK}
sync
sudo dd if=MLO-beagle_x15-v2015.01-rc4-r5 of=${DISK} count=1 seek=1
conv=notrunc bs=128k
sudo dd if=u-boot-beagle_x15-v2015.01-rc4-r5.img of=${DISK} count=2
seek=1 conv=notrunc bs=384k
sync

2GB [x]
HDMI video [x]
HDMI audio [ ]
USB [x]

Shell is "root@beaglebone" :wink: maybe BeagleBoard-X15?

Yeap! I need to change that. The image shares the same base rootfs
that we use for the beaglebone's. I need to tweak the /etc/hosts when
i make it for a specific board..

Works: Alpha board
2GB [x]
Line Audio out/in [x] [1]
HDMI video [x]
HDMI audio [x][2]
USB[x]
RTC[x][3]
SATA[x][4]
Palmas power button[x][5]
emmc[x][6]

Sweet! Thanks for testing all those!

It looks like either i messed up a config, or reset might be broken:

debian@beaglebone:~$ uname -r
3.14.26-ti-r43

debian@beaglebone:~$ sudo reboot

         Starting Reboot...
[ 35.335196] reboot: Restarting system

(2 led's lit)

Kernel:
http://git.ti.com/gitweb/?p=ti-linux-kernel/ti-linux-kernel.git;a=shortlog;h=refs/heads/ti-linux-3.14.y

synced with: bdea111134d82dc225f16f69652284f684985aee (top of the branch)

With this config:

https://github.com/beagleboard/linux/blob/1d0defeba9685e616b05f7340111ab84c47ad762/arch/arm/configs/bb.org_defconfig

Regards,

Any chance of using /proc/device-tree/model for that?

Actually an easy fix:

https://github.com/RobertCNelson/omap-image-builder/commit/c51385269432c8f45257bf8b9ae263ad65ab64f4

I've had a few users bug me about it before, just never added the
--hostname switch...

Regards,

hmmm... I see the same on my board now as well..

First i thought PRM_RSTTIME(0x4AE07D08) was not properly configured.
so i forced it to max value.. did not help..

I then realized looking at code that voltage rails were being powered off.

mmc_runtime_suspend->_mmc_sd_suspend->https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/mmc/host/omap_hsmmc.c#n354

So i hacked it with http://slexy.org/view/s21OqF9TWE (ldo1,
pbias_mmc_reg, vdd_3v3 always on).

With that I was able to reboot some 5 times. that makes me
wonder...two things:
a) On the current X15, ES1.1, warm reset is supposed to be routed to
PORz sequence for Palmas -> should'nt it setup everything properly by
Palmas? maybe we ought to monitor the rails and figure that out.

b) ES1.2 will have warm reset fixed, so we'd go back to hitting the
same issue all over again :(...

maybe we need something like a boot-device dt property to not reset
pins..

I see that similar attempt like
https://patchwork.kernel.org/patch/5480691/ was tried as well.. which
kinda results in the same problem but the solution for gpio expander
obviously wont for for x15 (as it has no gpio expander).

So, CCying kishon, sekhar et.al..

+Roger.

Since this might even be valid for SATA boot (powering off SATA might
result in SATA not detected by ROM code since ROM code does not talk
to PMIC anymore and depends on boot configuration).

we might want to restore something like boot-configuration for a
shutdown handler and depend on PMIC powering everything off for
poweroff. uggh... sounds like a wider forum question here.. will let
someone(kishon/roger?) take the ball to linux-kernel lists with a
proposal perhaps?

I am curious: is there a supply toggle for switching for HS200 mode? and
what do you suggest might be a potential proposal here?