As I said earlier, nautibuoy posted a link to an image file of Botic with Roonbridge. I've been using it for months.
Of corse i did, i'm following the guide at page 248 point-per-point exactly. But after installing botic driver, when i reboot all 4 leds remain on and bbb doesn't boot from sd. I cannot even reach flashing eMMC.
I tried debian 9.3 and 9.5, but nothing.
1) What exactly do you mean by "install the new system into an SD card via USB"... Do you mean connecting to terminal via usb ssh? Why not via ethernet? How should this installation be done?
2) And how should we then install botic driver on this sd card debian? By booting from it?
Sorry, my description might have been a bit misleading. I usually use a USB SD card reader to set up a bootable SD card. This procedure is always done on a linux system (Ubuntu 16.04) which is running on My MacBook Pro (using Parallels Desktop). So the SD card above can be always visible via the USB port as a /dev/sdX device. Once the debian image is installed to the card, I move it into the microSD slot of the BBB for booting.
After confirmation of this bootable SD is working, I usually download the .deb files of Botic system for installation. Actually, the files are always kept in my Ubuntu system. So I just run sftp command on the BBB to get the remote files.
Having a working linux system on a PC will be quite convenient for this kind of work.
Ok.
I do the following:
- Put a working 9.3 debian console image on eMMC and i ensure it works and boots
- Flash a prebuilt bone 9.5 image on the SD via Etcher in my W10 PC
- Insert the SD on BBB and it boots regularly
- Install botic driver V7 on SD as explained at page 248 - first post
- Modify /boot/uEnv.txt by adding the line "dtb=am335x-boneblack-botic.dtb"
- Reboot
And the BBB does not boot, all 4 leds are on at the same time.
The same if i try using a 9.3 image instead of 9.5.
The same if i perform botic installation on eMMC directly
I made maybe 20/30 tries in all manners i could think of...
What am i doing wrong?
Last edited:
First of all, if you are using an image file from debian.beagleboard.org as suggested by the first post of page 248 (actually #2471), it will not work for botic system. You are on the wrong track, though I don't know why because I'm not interested in their debian image file.
You need another image file from here as I wrote in other posts before. The current debian stretch image appears debian-9.5-console-armhf-2018-07-14.
Both 9.3 (old) and 9.5 images are from the site you link, but i tried the one from page 248 too.
My 9.5 image is exactly the one you report and i downloaded it from that site (raw microSD section)
Last edited:
Sorry my memory is not so good. A search of this thread helped refreshed my memory. See post #1803 for the image from Nautibuoy. Pretty sure I installed Roon on his image. It is an older Linux distribution but it works great for me. I had a few issues with the Roon install which are documented in this thread.
I finally managed to get a 8.7 image + botic 7 to boot.
The problem is Squeezelite R2 needs debian 9 at least...
I tried 9.1 too, but no way to get Stretch to boot after botic installation. Maybe there some more change to do in uEnv.txt?
Last edited:
I've just checked the feasibility of the latest debian image for botic system (2018-07-14/elinux/debian-9.5-console-armhf-2018-07-14.tar.xz).
After making a bootable debian SD and subsequent installation of the Botic system, I confirmed the Botic kernel was running fine as usual.
/etc/dogtag after successful botic installation shows the trace of original debian image: rcn-ee.net console Debian Image 2018-07-14.
BTW I don't use Windows when dealing with critically important linux things...
So please why don't you make a prebuilt working image of that booting SD card? So we can flash it and have a working BBB with debian 9.5 and botic running.
Anyway, i find it strange that just flashing an SD on a W10 PC (this is all i do using it) can lead to such a difference in results. Considering that even eLinux site says etcher on Windows can be used to burn their images on SD...
In windows systems all these compatibility problems are unimaginable: i normally use drivers written 5, 6 or 10 years ago and they still work ok on last windows versions without sacrifying any functionalities...
But i just bought a cronus/hermes hardware system, not a Linux PC. I didn't think all of this painful struggle was needed on the software side to make it work. I was used to ready-to-go Linux-based software like Volumio before, i thought something similar was available for BBB, but i was wrong.
My mistake.
Last edited:
I think I can understand your frustration but such a task might be well assigned to the author of this botic system...
To the point of preparing a working SD card of debian image, etcher on Windows will be okay, though I have no experience with this software.
Based on your previous comment that the booting process is stalled with all LEDs lit after installation of the botic system, there is a possibility of incomplete writing into the SD card during installation of the botic system. You might check if the sync command after installation of .deb files will work, though this is usually not required if reboot or shutdown follows after installation.
I have always used the sync command after modifying uEnv.txt, as doing this is among the instructions on page 248.
But i really cannot understand how can this same process work on some machines and fail on others: we all have the same platforms (BBB) and the same software (same debian images), so what could the difference be?
Something that maybe could make a (very little) sense could be that my BBB is Rev. C, so eMMC is 4Gb. You have Rev. C too or an earlier one?
Could this make a significant difference?
Surely it would be nice towards us Linux noobs, by Miero...
But i think anyone can do it, with his permission.
Or another solution would be to release a new botic version that fixes all compatibility issues with Stretch overlays
Another clue i noticed right now: the quoted message from Vit123 has an uBoot log file attached, that shows problems with the MMC card and invalid partitions.
So maybe the way the SD card is flashed could effectively have an influence on the issue?
I tried to flash an image in BBB directly, following the instruction on Elinux site for Debian Testing image, but it failed for the lack of "parted" package, that i couldn't download even doing what the image itself asked: i had a "not found" error using wget from the suggested address.
I can not recall the programs I used to flash the SDCard. --edit: it was
Win32 Disk Imager
Seem to recall I had problems if the SDCard was not
completely erased before doing the copy to it.
I think I had the same problem of all leds lit after
trying to install the SDCard to the eMMC.
Also, there was a program that was specifically
specified to use for flashing in Windows.
Win32 Disk Imager
Seem to recall I had problems if the SDCard was not
completely erased before doing the copy to it.
I think I had the same problem of all leds lit after
trying to install the SDCard to the eMMC.
Also, there was a program that was specifically
specified to use for flashing in Windows.
Last edited:
That should be reformat the SDCard not erase.
Must be done every time before doing a flash!
Using SD Formatter Tool to restore full capacity on SDHC/SDXC cards
Must be done every time before doing a flash!
Using SD Formatter Tool to restore full capacity on SDHC/SDXC cards
Last edited:
Personally, i always used SD Formatter to (quick) format the SD cards before flashing: i noticed in previous cases it lowers the chance of bad flashes.
For flashing i used Etcher and in a pair of cases Win32 disk imager.
I noticed fs was always fat32...
In some cases i tried expanding the partition before installing botic, but not to 100% of available space. My SD is 8Gb.
Last edited: