BeagleBone Black (Rev. C): GLUED won't boot from SD-card

[Elias Strandell Erstorp]

Hi,

I'm trying to boot GLUED 1.11.1 from a SD card, but as I hold in the boot-switch and power up nothing happens except for the power

LED to turn on.  I guess the partitions on the SD card looks fine (root0, data0, BOOT0). My eMMC is currently flashed with Debian 

and it works fine. I think the problem might have something to do with the GLUED boot files, but it's really difficult to tell. I tried

putting the boot-files inside a boot folder in BOOT0, as this seems to have solved a similar problem for others (using other Linux distributions though), 

but without success. I used the lctr-b2xx-testbed configuration file when configuring and compiling GLUED in a Virtual Machine running Debian under OSX,

and had no problems during the compilation or whatsoever. 

Do you have any clue of what this problem might be related to?

Best Regards,

Elias

[Ricardo Martins]

Hi Elias,

Which GLUED revision (git commit) are you using ? Can you try the following on debian and send me the output ?

sudo fdisk SDCARD_DEVICE

When you reach the prompt write:

p<ENTER>

Then

q<ENTER>

--
You received this message because you are subscribed to the Google Groups "LSTS Toolchain" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lsts-toolchai...@googlegroups.com.
Visit this group at http://groups.google.com/group/lsts-toolchain.
To view this discussion on the web visit https://groups.google.com/d/msgid/lsts-toolchain/fa4ca3ad-ad66-4bca-bddd-0376648cf2c5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Elias Strandell Erstorp]

Thank you for such a quick reply!
I downloaded the GLUED 1.11.1 release.
This is the output I get:

Disk /dev/sdb: 3965 MB, 3965190144 bytes
255 heads, 63 sectors/track, 482 cylinders, total 7744512 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
Disk identifier: 0x0002eb3c

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1       65535       32767+  83  Linux
/dev/sdb2           65536     1114111      524288   83  Linux
/dev/sdb3         1114112     7743329     3314609   83  Linux

[Ricardo Martins]

On Thu, Oct 16, 2014 at 12:57 PM, Elias Strandell Erstorp <moe...@gmail.com> wrote:

Thank you for such a quick reply!
I downloaded the GLUED 1.11.1 release.
This is the output I get:

Disk /dev/sdb: 3965 MB, 3965190144 bytes
255 heads, 63 sectors/track, 482 cylinders, total 7744512 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
Disk identifier: 0x0002eb3c

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1       65535       32767+  83  Linux
/dev/sdb2           65536     1114111      524288   83  Linux
/dev/sdb3         1114112     7743329     3314609   83  Linux

The problem is that parted, which we use to create partitions, sometimes forgets to set the right partition's system id type. Can you try flashing a microSD card using the branch 'master'. You can issue:

git checkout master

and then mkdisk.

 

On Thursday, October 16, 2014 5:56:03 AM UTC-5, Elias Strandell Erstorp wrote:

Hi,

I'm trying to boot GLUED 1.11.1 from a SD card, but as I hold in the boot-switch and power up nothing happens except for the power

LED to turn on.  I guess the partitions on the SD card looks fine (root0, data0, BOOT0). My eMMC is currently flashed with Debian 

and it works fine. I think the problem might have something to do with the GLUED boot files, but it's really difficult to tell. I tried

putting the boot-files inside a boot folder in BOOT0, as this seems to have solved a similar problem for others (using other Linux distributions though), 

but without success. I used the lctr-b2xx-testbed configuration file when configuring and compiling GLUED in a Virtual Machine running Debian under OSX,

and had no problems during the compilation or whatsoever. 

Do you have any clue of what this problem might be related to?

Best Regards,

Elias

--
You received this message because you are subscribed to the Google Groups "LSTS Toolchain" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lsts-toolchai...@googlegroups.com.
Visit this group at http://groups.google.com/group/lsts-toolchain.

To view this discussion on the web visit https://groups.google.com/d/msgid/lsts-toolchain/0ea91987-17e1-4fca-b67a-18bf2139b361%40googlegroups.com.

[Elias Strandell Erstorp]

Seems to have worked when I obtained the code using git. It doesn't automatically boot from the SD card, so I'm not sure everything is alright.

A couple of questions has araised:

- Should it support a HDMI monitor? I had assumed to be able to interact with it using keyboard and display, but I don't get any video output.

- The university network is kind of protected, and I won't get access to it by just connecting the BBB to the ethernet. Is there a chance to

  access the BBB through a direct USB connection? The Debian version had a static USB address, so it was really easy to connect to.

Thanks!

[Ricardo Martins]

On Thu, Oct 16, 2014 at 4:07 PM, Elias Strandell Erstorp <moe...@gmail.com> wrote:

Seems to have worked when I obtained the code using git. It doesn't automatically boot from the SD card, so I'm not sure everything is alright.

If you press the boot button (the one near to the microSD slot) for 5 seconds while powering the board it should boot from the microSD card and not the eMMC. Can you try it ?

 

A couple of questions has araised:

- Should it support a HDMI monitor? I had assumed to be able to interact with it using keyboard and display, but I don't get any video output.

GLUED is meant to be used in autonomous vehicles and deeply embedded systems. It's very rare to have one of those systems connected to a screen or keyboard. For the BBB you can use an FTDI TTL 3V3  to USB converter to connect to the console. With that cable you can see all stages of the boot process and at the end you will have a shell.

 

- The university network is kind of protected, and I won't get access to it by just connecting the BBB to the ethernet. Is there a chance to

  access the BBB through a direct USB connection? The Debian version had a static USB address, so it was really easy to connect to.

We could add that to the kernel configuration. Even though we have no use for it we could be persuaded to add it if you tell us what you intend to do with GLUED.

 

Thanks!

On Thursday, October 16, 2014 12:56:03 PM UTC+2, Elias Strandell Erstorp wrote:

Hi,

I'm trying to boot GLUED 1.11.1 from a SD card, but as I hold in the boot-switch and power up nothing happens except for the power

LED to turn on.  I guess the partitions on the SD card looks fine (root0, data0, BOOT0). My eMMC is currently flashed with Debian 

and it works fine. I think the problem might have something to do with the GLUED boot files, but it's really difficult to tell. I tried

putting the boot-files inside a boot folder in BOOT0, as this seems to have solved a similar problem for others (using other Linux distributions though), 

but without success. I used the lctr-b2xx-testbed configuration file when configuring and compiling GLUED in a Virtual Machine running Debian under OSX,

and had no problems during the compilation or whatsoever. 

Do you have any clue of what this problem might be related to?

Best Regards,

Elias

--
You received this message because you are subscribed to the Google Groups "LSTS Toolchain" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lsts-toolchai...@googlegroups.com.
Visit this group at http://groups.google.com/group/lsts-toolchain.

To view this discussion on the web visit https://groups.google.com/d/msgid/lsts-toolchain/e867e0d2-1b88-4230-bdbb-cc28e407715f%40googlegroups.com.

[Elias Strandell Erstorp]

It seems to work, one of the partitions is now a FAT16 file system and one of the user LEDs was blinking when I booted with the boot button pressed. 

If I understood it right, a static IP adress is set for eth0 and SSH is automatically installed, so I should be able to connect to the BBB through my home router

using that adress? Will try tomorrow.

I started getting a feeling I might need a FTDI cable, I'll see what I got. At this moment I'm just trying to understand the toolchain and

connect things. I first want to try a system constituting of BeagleBone and Ardupilot to control a road vehicle, as I know you have tested such a setup. 

If it's really necessary to use GLUED is not clear, there is probably some other "quite" lightweight Linux distribution that are targeted at BeagleBone that would

be adequate. The main benefit of GLUED is the speed right? It's also interesting as you are using it in your projects.

Thank you again!