Support for Botic Linux driver

[ichiban]

#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.
/var/www/command/player_wdog.sh startup & > /dev/null 2>&1
echo 9 > /sys/module/snd_soc_botic/parameters/ext_masterclk
exit 0

did not change the config.What am I doing wrong?

What editor are you using.

 

[kinku]

Another thing ... if you have NTFS filesystem on the flash drive .. then you need to install also following package:

apt-get install [B]ntfs-3g[/B]

 

[kinku]

What editor are you using.

Pspad ichi

 

[ichiban]

Pspad ichi

Can you connect with putty and use nano instead?

 

[miero]

oh, my fault... I'm sorry

the ext_masterclk cannot be changed via command line, only from kernel option

so you need to update another file ... and with different content

mount /dev/mmcblk0p1 /boot/uboot
nano /boot/uboot/uEnv.txt
umount /boot/uboot

and (just guessing) you need to change there line starting with optargs to

optargs=fixrtc soc_botic.ext_masterclk=9

 

[miero]

Hey guys, please also edit and clarify the HOWTO document if anything there is missing or unclear... thanks.

https://docs.google.com/document/d/1XQ8PNl3o7iERYWH1Wt_YRdkAPoOSF2fu3Sz4zzmaURM/edit

 

[ichiban]

BBB problwm

Meiro,
I'm trying to get the BBB running again. If you can look at the attachment.
I'm trying to flash back to the start with a Debian version and redo the Botics.
Because something went awry after I attempted the Botic v5 update.

I'm trying various suggestions I find on Linux sites, go luck so far.

I know this thread is for Botic problems, so if you'd rather I try finding a solution else where I will and I understand.

If I can't find a fix, it'll be a new BBB ordered. Lesson learned.

 

[miero]

ichiban:

You do not boot from SD card... you boot from eMMC, because the Botic kernel is still being loaded (and it is only in eMMC assuming you are flashing Debian)

[ 0.000000] Linux version 4.0.0-botic5 (root@lilek) (gcc version 4.9.3 20141031 (prerelease) (Linaro GCC 2014.11) ) #1 PREEMPT Tue Apr 28 23:42:17 CEST 2015

Please check the BBB_SRM.pdf manual for exact instructions how to boot from SD card...
https://github.com/CircuitCo/BeagleBone-Black/blob/master/BBB_SRM.pdf?raw=true

 

[miero]

Or there might be a problem, that you have incorrectly flashed the image on the SD card.

Did you extract the .xz file before flashing? It should be more than 1GB file if extracted.

I think that this is very probable because of following output of bootloader:

mmc0 is current device
gpio: pin 54 (gpio 54) value is 1
** No partition table - mmc 0 **
Checking for: /uEnv.txt ...
** No partition table - mmc 0 **
Checking for: /boot.scr ...
** No partition table - mmc 0 **
Checking for: /boot/boot.scr ...
** No partition table - mmc 0 **
Checking for: /boot/uEnv.txt ...
** No partition table - mmc 0 **
** No partition table - mmc 0 **
** No partition table - mmc 0 **
** No partition table - mmc 0 **
** No partition table - mmc 0 **
** No partition table - mmc 0 **
** No partition table - mmc 0 **
gpio: pin 56 (gpio 56) value is 0
gpio: pin 55 (gpio 55) value is 0
gpio: pin 54 (gpio 54) value is 0

 

[kinku]

oh, my fault... I'm sorry

the ext_masterclk cannot be changed via command line, only from kernel option

so you need to update another file ... and with different content

mount /dev/mmcblk0p1 /boot/uboot
nano /boot/uboot/uEnv.txt
umount /boot/uboot

and (just guessing) you need to change there line starting with optargs to

optargs=fixrtc soc_botic.ext_masterclk=9

That did not work. This is the address of file if that was what you were guessing

/sys/module/snd_soc_botic/parameters/ext_masterclk

I was able to edit uEnv file before using pspad in WinScp,now I can not see it in /boot/uboot folder

 

[ichiban]

Or there might be a problem, that you have incorrectly flashed the image on the SD card.

Did you extract the .xz file before flashing? It should be more than 1GB file if extracted.

I think that this is very probable because of following output of bootloader:

mmc0 is current device
gpio: pin 54 (gpio 54) value is 1
** No partition table - mmc 0 **
Checking for: /uEnv.txt ...
** No partition table - mmc 0 **
Checking for: /boot.scr ...
** No partition table - mmc 0 **
Checking for: /boot/boot.scr ...
** No partition table - mmc 0 **
Checking for: /boot/uEnv.txt ...
** No partition table - mmc 0 **
** No partition table - mmc 0 **
** No partition table - mmc 0 **
** No partition table - mmc 0 **
** No partition table - mmc 0 **
** No partition table - mmc 0 **
** No partition table - mmc 0 **
gpio: pin 56 (gpio 56) value is 0
gpio: pin 55 (gpio 55) value is 0
gpio: pin 54 (gpio 54) value is 0

Yes, it was from xz file and 3.61 GB (3,879,731,200 bytes).
I've used this extraction to re flash many times the past two weeks with no problem.


BBB-eMMC-flasher-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb_1.img

 

[miero]

kinku, in that case you need to find where is uEnv.txt and write it there... no other way

nano /uEnv.txt
nano /boot/uEnv.txt

if any of these works please check also output of command "blkid"

if there are 2 /dev/mmcblk0... lines, then the uBoot.txt is probably on the first one ... and you need to mount it and find the file there

 

[miero]

ichiban: then you can also try different microSD card ... the one you are using seems not to be recognized by BBB

the partition table on the SD card must be found, otherwise it is not correctly written

you can try also another card with some data to check if the BBB can still read SD cards

 

[kinku]

ok what did is this ,in winscp I made a file in boot/uboot folder with name uEnv.txt when I opened it I found all the strings there.

optargs=fixrtc

loadfdt=ext4load mmc ${mmcdev}:2 ${fdtaddr} /boot/dtbs/${fdtfile}
loaduimage=mw.l 4804c134 fe1fffff; if ext4load mmc 0:2 ${loadaddr} /boot/zImage; then mw.l 4804c194 01200000; echo Booting from external microSD...; setenv mmcdev 0; else setenv mmcdev 1; if test $mmc0 = 1; then setenv mmcroot /dev/mmcblk1p2 rw; fi; ext4load mmc 1:2 ${loadaddr} /boot/zImage && mw.l 4804c194 00c00000; echo Booting from internal eMMC...; fi
mmcboot=run mmcargs; bootz ${loadaddr} - ${fdtaddr}
uenvcmd=i2c mw 0x24 1 0x3e; run findfdt; if test $board_name = A335BNLT; then setenv mmcdev 1; mmc dev ${mmcdev}; if mmc rescan; then setenv mmc1 1; else setenv mmc1 0; fi; fi; setenv mmcdev 0; mmc dev ${mmcdev}; if mmc rescan; then setenv mmc0 1; else setenv mmc0 0; fi; run loaduimage && run loadfdt && run mmcboot

it is gone with reboot.I am booting from SD,does it have anything to do with this

 

[miero]

optargs=fixrtc snd_soc_botic.ext_masterclk=9

 

[miero]

And I see now that in #855 I've forgotten to add soc_ prefix to kernel option.

 

[ichiban]

ichiban: then you can also try different microSD card ... the one you are using seems not to be recognized by BBB

the partition table on the SD card must be found, otherwise it is not correctly written

you can try also another card with some data to check if the BBB can still read SD cards

I may have missed mentioning a salient point.
There is also a problem with a standard boot.
Serial output attached......

 

[miero]

it is gone with reboot.I am booting from SD,does it have anything to do with this

it should not be... otherwise it has not been written correctly... save, close, unmount....

what is your "blkid" output?

 

[kinku]

/dev/mmcblk0p1: SEC_TYPE="msdos" LABEL="boot" UUID="BC22-2319" TYPE="vfat"
/dev/mmcblk0p2: LABEL="rootfs" UUID="31c7703c-ab54-436f-9017-2a9a0e3ac2bb" TYPE="ext4"
/dev/mmcblk1p1: SEC_TYPE="msdos" LABEL="BEAGLEBONE" UUID="3AEA-1E68" TYPE="vfat"
/dev/mmcblk1p2: LABEL="rootfs" UUID="fbc0dc84-8c3d-43c4-8bcd-b23b8d67b086" TYPE="ext4"

 

[miero]

ichiban: that is not standard bootl that boot is executing eMMC flasher command automagicaly... you have used incorrect flashing script before.