Testing BBBW

Has something changed with bone-debian-8.7-lxqt-4gb-armhf-2017-02-12-4gb.img ?

root@kgDebian:/home/kevin# fdisk /dev/sdc1

Welcome to fdisk (util-linux 2.25.2).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

/dev/sdc1: device contains a valid 'ext4' signature, it's strongly recommended to wipe the device by command wipefs(8) if this setup is unexpected to avoid possible collisions.

Device does not contain a recognized partition table.
Created a new DOS disklabel with disk identifier 0x10b30ea5.

Command (m for help): q

root@kgDebian:/home/kevin# umount -v /dev/sdc1
umount: /media/kevin/rootfs (/dev/sdc1) unmounted

I have not seen this message before: Device does not contain a recognized partition table.

What is the best way to increase the partition size?

Many thanks,

Kevin.

bootup once and use the built-in script:

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Expanding_File_System_Partition_On_A_microSD

Regards,

Many thanks Robert. In the past I have used and to make my sdcards. Your script finds errors in their result.

Using linux how do you suggest I should make my sdcards compatiable with your script?

Regards,

Kevin.

Hi Robert,

The error I struck using grow_partition.sh was:

Re-reading the partition table ...
sfdisk: BLKRRPART: Device or resource busy
sfdisk: The command to re-read the partition table failed.
Run partprobe(8), kpartx(8) or reboot your system now,
before using mkfs
sfdisk: If you created or changed a DOS partition, /dev/foo7, say, then use dd(1)
to zero the first 512 bytes: dd if=/dev/zero of=/dev/foo7 bs=512 count=1
(See fdisk(8).)

I rebooted and ran:

root@beaglebone:/opt/scripts/tools# ./version.sh
git:/opt/scripts/:[e066cb50c5eda24ce09227b1a155da823d56225a]
eeprom:[A335BNLTBWA51646BBWG0358]
dogtag:[BeagleBoard.org Debian Image 2017-02-12]
bootloader:[/dev/mmcblk0]:[U-Boot 2017.03-rc1-00003-ga09f2d]
bootloader:[/dev/mmcblk1]:[U-Boot 2016.11-rc3-00002-g73df7f]
kernel:[4.4.48-ti-r88]
nodejs:[v4.7.3]
root@beaglebone:/opt/scripts/tools# df
Filesystem 1K-blocks Used Available Use% Mounted on
udev 10240 0 10240 0% /dev
tmpfs 99956 3036 96920 4% /run
/dev/mmcblk0p1 7376168 2934944 4090164 42% /
tmpfs 249884 4 249880 1% /dev/shm
tmpfs 5120 4 5116 1% /run/lock
tmpfs 249884 0 249884 0% /sys/fs/cgroup
tmpfs 49980 0 49980 0% /run/user/1000

root@beaglebone:/opt/scripts/tools# fdisk -l /dev/mmcblk0

Disk /dev/mmcblk0: 7.2 GiB, 7744782336 bytes, 15126528 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xc9171f1a

Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 * 8192 15126527 15118336 7.2G 83 Linux

I HAVE NOT RUN mkfs.

So there is only one partition BUT it starts at 8192 sectors. Is there absolutely nothing pior to 8192 sectors? Is there a MRB in the first 512 bytes? If I used dd in linux must I allow for that? Why so many sectors (8192)?

The version is: bootloader:[/dev/mmcblk0]:[U-Boot 2017.03-rc1-00003-ga09f2d] Is U-Boot 2017.03-rc1-00003 sufficiently up to date?

This is how my slots are at present:

0: P---L- 0 4D 7.0 LCD CAPE- 4DCAPE-70T ,00A3,4D SYSTEMS ,BB-BONE-LCD7-01

1: PF---- -1

2: PF---- -1

3: PF---- -1

In /boot/uEnv.txt I uncommented: enable_uboot_overlays=1 and disable_uboot_overlay_video=1

Moved /uEnv.txt to /uEnv.txt.old

I shutdown the BBBW and it actually shutdown not rebooted??? After so long faulty?

After restart checked slots which was the same as above.

In /boot/uEnv.txt I uncommented:disable_uboot_overlay_audio=1

In /boot/uEnv.txtadded cape_enable=bone_capemgr.enable_partno=BB-UART1,BB-I2C1,BB-UART4

I shutdown the BBBW but it rebooted.

New slots:

0: P---L- 0 4D 7.0 LCD CAPE- 4DCAPE-70T ,00A3,4D SYSTEMS ,BB-BONE-LCD7-01

1: PF---- -1

2: PF---- -1

3: PF---- -1

4: P-O-L- 1 Override Board Name,00A0,Override Manuf,BB-UART1

5: P-O-L- 2 Override Board Name,00A0,Override Manuf,BB-I2C1

6: P-O-L- 3 Override Board Name,00A0,Override Manuf,BB-UART4

I tried adding BB-ADC with no effect. BB-BONE-LCD7-01 uses some of AIN pins. AIN0 to AIN3? Not sure.

root@beaglebone:/home/debian# cd /sys/bus/iio/devices/iio:device0
root@beaglebone:/sys/bus/iio/devices/iio:device0# ls -al
total 0
drwxr-xr-x 5 root root 0 Feb 20 23:41 .
drwxr-xr-x 4 root root 0 Feb 20 23:41 ..
drwxr-xr-x 2 root root 0 Feb 21 03:49 buffer
-r--r--r-- 1 root root 4096 Feb 21 03:49 dev
-rw-r--r-- 1 root root 4096 Feb 21 03:49 in_voltage4_raw
-rw-r--r-- 1 root root 4096 Feb 21 03:49 in_voltage5_raw
-rw-r--r-- 1 root root 4096 Feb 21 03:49 in_voltage6_raw
-rw-r--r-- 1 root root 4096 Feb 21 03:49 in_voltage7_raw
-r--r--r-- 1 root root 4096 Feb 21 03:49 name
lrwxrwxrwx 1 root root 0 Feb 21 03:49 of_node -> ../../../../../../firmware/devicetree/base/ocp/tscadc@44e0d000/adc
drwxr-xr-x 2 root root 0 Feb 21 03:49 power
drwxr-xr-x 2 root root 0 Feb 21 03:49 scan_elements
lrwxrwxrwx 1 root root 0 Feb 21 03:49 subsystem -> ../../../../../../bus/iio
-rw-r--r-- 1 root root 4096 Feb 20 23:41 uevent
root@beaglebone:/sys/bus/iio/devices/iio:device0#

I guess from the above I can use AIN3 to AIN6?

The important result is that using uboot overlays does NOT impact on wireless.

Regards,

Kevin.