glued building question

[hughhugh]

Hi,
I have trying to Building the Glued linux system for beaglebone black industrial board under Ubuntu 18.04, but many errors occurs like alloca or other issue. Since the glued project has existed for a long time. Which gcc or laptop system version is more suitable? Thanks.

[pmfg]

Hi Nathan,
To compile OS GLUED it is necessary to use the docker. The OS compilation is done inside the docker, this docker contains the necessary requirements for the compilation of the system.
Steps to compile OS GLUED

[gslkr]

Hi,
I have trying to Building the Glued linux system for beaglebone black. And I have populate uSD successfully, but after I power BBB, it will not work as wiki writing.
It shows that

And it cannot mount SD card with the right file like this:
.

I do not know it is right. Am I missing some necessary steps? Thanks

[mariacosta]

Dear Nathan, Beaglebone by default boots from the eMMC instead of the SD card. You'll need to configure it to boot from the SD card instead. Instructions on how to do it below: *Instructions on How to run GLUED on BBB - First Time* 1) Populate uSD with glued's ./mkdisk 2) Insert uSD on BBB (do not power it up) 3) Get a 5V power transformer + a USB <-> TTL cable 4) Open a terminal emulator with 115200, 8n1 5) Connect everything except the power transformer 6) Press a black button in BBB near USB connector, and keep pressing it while powering BBB 7) Release black button when you read "Uncompressing Kernel" or similar 8) After arriving to the shell you will mount the boot partition of the internal flash. Here's how: 8.1) /dev/mmc* You should see something like: /dev/mmcblk0 /dev/mmcblk0p3 /dev/mmcblk1boot1 /dev/mmcblk0p1 /dev/mmcblk1 /dev/mmcblk1p1 /dev/mmcblk0p2 /dev/mmcblk1boot0 /dev/mmcblk1p2 8.2) mount /dev/mmcblk1p1 /mnt 8.3) ls /mnt You should see something like: App Drivers LICENSE.txt README.md autorun.inf uEnv.txt Docs ID.txt MLO START.htm u-boot.img 8.4) Delete everything: rm -rf /mnt/* 8.5) cp /boot/MLO /boot/u-boot.img /mnt 8.6) umount /mnt 8.7) sync 8.8) sync 8.9) halt 9) Power off Now you should be able to use it normally. Start it without pressing the button and ssh to it for remote access. Best Regards, Maria Costa gslkr ***@***.***> escreveu no dia segunda, 28/06/2021 à(s) 09:15:

…

Hi, I have trying to Building the Glued linux system for beaglebone black. And I have populate uSD successfully, but after I power BBB, it will not work as wiki writing. It shows that [image: 1] <https://user-images.githubusercontent.com/74852726/123601855-c0cfc500-d82a-11eb-8c05-61f2aa101220.png> [image: 2] <https://user-images.githubusercontent.com/74852726/123601869-c4634c00-d82a-11eb-8dba-1a77633254cd.png> And it cannot mount SD card with the right file like this: [image: 3] <https://user-images.githubusercontent.com/74852726/123602456-55d2be00-d82b-11eb-9098-392e97d37d29.png> . I do not know it is right. Am I missing some necessary steps? Thanks — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#43 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABQJNOPSCGFRSFRLUNSCWHDTVAVRHANCNFSM47LPYD6Q> .

[gslkr]

Hi,
after I Populate uSD with glued,when I mount SD on the beaglebone black ,it will show that:
"spl_load_image_fat_os: error reading image args, err - -1 ".
And in addition, when I do "mount /dev/mmcblk1p1 /mnt" , there are no necessary files shown in the wiki. Do you have any ideas？ Thanks.

[pmfg]

Hi,
Ok, we're going to generate the same OS scenario for BBB on this side, to see if we can detect the same issue.
I'll put the test results here.

[krisgry]

Hi! Not sure if you know this, but there is a difference in setting up the BBB and the BBB Industrial. The above steps, from @mariacosta , are for the non-industrial version. We've had some issues with this, and have found that partitioning the eMMC works.

See the below lines, chopped from our guide on the matter:

 If the above steps do not work, it might be due to the eMMC being partitioned in a wrong way. To fix this, boot from the SD card and connect the BBB to the PC as described above.

    Check how the disk is partitioned: fdisk -l

This should give the following output:

Disk /dev/mmcblk1: 3867 MB, 3867148288 bytes
4 heads, 16 sectors/track, 118016 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

        Device Boot      Start         End      Blocks  Id System
/dev/mmcblk1p1   *          33        3104       98304   e Win95 FAT16 (LBA)
/dev/mmcblk1p2            3105      118016     3677184  83 Linux

Disk /dev/mmcblk1boot1: 16 MB, 16777216 bytes
4 heads, 16 sectors/track, 512 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Disk /dev/mmcblk1boot1 doesn't contain a valid partition table

Disk /dev/mmcblk1boot0: 16 MB, 16777216 bytes
4 heads, 16 sectors/track, 512 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Disk /dev/mmcblk1boot0 doesn't contain a valid partition table

If the partitions are not exactly of this size and type they must be made so. This is done by running the following commands:

    fdisk /dev/mmcblk1
    o - this clears the existing partitions
    p - this lists all partition tables on the card (there should be none)
    n - create a new partition
    p - primary partition
    1 - partition number
    33 - value for the first sector
    3104 - last sector / partition size
    t - change the partition type (select partition 1)
    e - change the partition type to “W95 FAT16 (LBA)”
    a - set the bootable flag for the selected partition (select partition 1)
    n - create a new partition
    p - primary partition
    2 - partition number
    3105 - value for the first sector
    hit Enter to choose the default (last) value for the last sector
    p - this lists all partition tables on the card (there should be two)
    w - write all the above changes to disk
    umount /dev/mmcblk1p1 - if mounted
    mkfs.vfat -F 16 /dev/mmcblk1p1 - format the first partition
    umount /dev/mmcblk1p2 - if mounted
    mkfs.ext4 /dev/mmcblk1p2 - format the second partition

If the system on the SD-card does not have mkfs.vfat, it can be included by adding dosfstools to the cfg_packages line in the system configuration file (found in glued/systems/ntnu-b2xx/) and then downloading the system to the SD-card again following the procedure in http://github.com/LSTS/glued. You will not need to co through the fdisk steps again, but may start directly from mkfs.vfat….