The latter, install botic. What I've tried yesterday...and was going to post but decided not to.....but here it is--->
After many tries, redownloads of bbb-demo-botic-v3-2gb.img.gz unpack with 7-ZIP, earse/reformat SSD, loading the .img usinf Win32DiskImager, the best I can say is I haven't gotten back to square zero again.
1st try
- SSD card inserted in powered down BBB
- press & hold user-boot-button, power on
- no leds lit, nothing happening, power down
2nd try
- SSD card inserted in powered down BBB
- NO user-boot-button press, power on
- leds 1&2 on, nothing else happening, power down
3rd try
- BBB unpowered
- SSD not inserted, no boot-button-press, powered on
- Insert SSD
- copy & paste /opt/scripts/tools/eMMC/beaglebone-black-make-microSD-flasher-from-eMMC.sh
- led 1 on (solid)
- after 15-20 minutes? ,a guess' message displays "Network error: Software caused connection abort"
Ichiban, you do not need to re-download many times image ... there is also .md5sum file which contains "proof number" that you have the correct file
for example: after the unpacking the bbb-demo-botic-v3-2gb.img file should have md5sum checksum equal to b221aa53ae6387fd14aa5fd2b46221de
the "Win32 Disk Imager" is able to compute this number during copy operation
To your tries:
- 1st one should boot from internal eMMC memory (if its content is still valid)
- 3rd one is strange, because you need to have booted Botic to be able flash eMMC,
also it is not cleare where you pasted that command and what was its output
- nevertheless, your 2nd try should succeed.
I'm not able to tell what could be wrong in your case. It would be cool if you could connect serial port to BBB and copy out messages which are printed. But you would need serial cable (TTL 3.3V levels only!). For example, this one could work well... errr that one would NOT!
for example: after the unpacking the bbb-demo-botic-v3-2gb.img file should have md5sum checksum equal to b221aa53ae6387fd14aa5fd2b46221de
the "Win32 Disk Imager" is able to compute this number during copy operation
To your tries:
- 1st one should boot from internal eMMC memory (if its content is still valid)
- 3rd one is strange, because you need to have booted Botic to be able flash eMMC,
also it is not cleare where you pasted that command and what was its output
- nevertheless, your 2nd try should succeed.
I'm not able to tell what could be wrong in your case. It would be cool if you could connect serial port to BBB and copy out messages which are printed. But you would need serial cable (TTL 3.3V levels only!). For example, this one could work well... errr that one would NOT!
Last edited:
This USB serial cable should work well (with CP2102 chip):
- CP2102 Module USB to Usart UART 3 3V TTL USB to com Free Cables | eBay
You'd need to connect GND, RXD, TXD pins to 1, 4 and 5 pins on the J1 connector on BBB. And use some serial terminal application.
- CP2102 Module USB to Usart UART 3 3V TTL USB to com Free Cables | eBay
You'd need to connect GND, RXD, TXD pins to 1, 4 and 5 pins on the J1 connector on BBB. And use some serial terminal application.
Last edited:
My guess : your SD card from Botic image appears OK but the file system necessary for booting linux may be corrupted and is needed to be repaired.
For this, you have to run a unix command called fsck on a particular linux system with the SD card inserted. After that, I think you can boot up the Botic BBB with this card. The problem is that you can not run fsck on your Win PC.
I don't know if there is any Windows application equivalent to fsck. The best way is to have a linux system like ubuntu on a small USB drive which can be booted from your Windows machine. If you want to have a long relationship with Botic system, this small effort to set up your own linux environment will be of great help in the future.
I found this and will give it a shot. Thanks for your help.
Ext2Fsd is an ext* file system driver for Windows , gpl2 license and FREE, support a lot of features that you can find in fsck , here is the link to check Ext2Fsd Project
Maybe I'm not getting this right. The APP fsck is going to check the "file system necessary for booting linux" that is on the SD card?
Yes, fsck checks the file systems on the SD card, located in different partitions: one with FAT12 and the other with Linux in this particular case.
Or also "official" cable: TTL-232R-3V3 FTDI | Mouser
This one will have faster shipment, than the one from China.
This one will have faster shipment, than the one from China.
Well, I'm glad I decided to check for posts here this morning before digging around in the garage for parts to set up a linux box. I have a Cinnamon music server set up but being an old PC I garbage picked off the street it doesn't have a SD card reader.
Yes, I was thinking how could the downloaded botic be corrupted, but at this point I'll try anything.
So, I'll put together a Mouser order. I've been putting off a parts order for two years now, and I have multiple Salas BiB regs, and Pass amps to build.
Miero, do you think BBB has enough processing power to incorporate DRC. Was reading on BruteFIR and DIgital room correction
nwfiir audio tools
BruteFIR
DRC: Digital Room Correction
nwfiir audio tools
BruteFIR
DRC: Digital Room Correction
This reference states that the program draws 15% CPU load on an 800MHz Celeron with 44.1KHz stereo material. So my guess is it could run. I played with the program 'Room EQ Wizard' some years ago. With Opus DACs back then, critical fidelity was never maintained. Best results came from merely de-emphasizing low frequency peaks. Better results were obtained the old fashioned way - critical speaker placement. Not to discourage you - newer DRC implementations might be much improved. The question is - what is the highest frequency that is feasible (and can one adapt between 44.1 and 48 KHz families with integer up sampling)? My TPA boards should arrive this week and I will try to get Ecasound running on a BBB - but I'm looking at a steep learning curve! No hurry... I will be interested in others' experiences. Cheers!
Franco, I tried room correction through a professional level parametric EQ from Rane with the help of Room EQ wizard two years ago. The problems were these
You cannot correct for all room issues with an equalizer ,because it will introduce phase distortion.
Rane had a noisy power supply that injected noise into my entire signal chain
So I went back to room correction the old style. So correction for low frequency issue is better done with absorbers and traps and high frequency room modes can be dealt with to an extent with DRC.
You cannot correct for all room issues with an equalizer ,because it will introduce phase distortion.
Rane had a noisy power supply that injected noise into my entire signal chain
So I went back to room correction the old style. So correction for low frequency issue is better done with absorbers and traps and high frequency room modes can be dealt with to an extent with DRC.
Perhaps for fixed frequency output, newer DRC schemes using FIR will be better.
I will also relate this somewhat OT experience relative to room EQ. A while after trying Room EQ Wizard I dabbled in the black art of driver cone/dome modifications. With my particular drivers the mods had a remarkable impact in removing distracting room effects! (search my old posts if you want a ref to my experiences) Overall, the apparent speaker locations lost definition. With this stuff, though, every driver and situation is unique. Now I'm starting with a new room, new player hardware/software, and new (much higher WAF) driver enclosures. So, a lot of fun to be had!
Appreciation to Meiro and all the contributors to this revolutionary advance in DIY sound!
