<mattb0ne>
ssh works the same in windows right cannot ssh to beaglebone.local in win11
<mattb0ne>
getting
<mattb0ne>
ssh: connect to host beaglebone.local port 22: Unknown error
mattb0ne has quit [Remote host closed the connection]
mattb0ne has joined #beagle
<hnv>
mattb0ne: can you reach the beagle with `telnet beaglebone.local 22` ?
thinkfat has joined #beagle
thinkfat_ has quit [Ping timeout: 250 seconds]
vagrantc has quit [Ping timeout: 250 seconds]
fakuivan has joined #beagle
<fakuivan>
Hello, I'm a noob with respect to the beaglebone boards. A university professor asigned me to look into how to get a beaglebone black running with a linux OS. What linux distros does that board support?
<fakuivan>
It'd be great if I could get something familiar to run like ubuntu or debian server
buzzmarshall has quit [Quit: Konversation terminated!]
<hnv>
The BeagleBone Black (and Green) are shipped with Debian pre-installed
<hnv>
(booting from the eMMC). You can also boot from a uSD with another distro (supporting that particular board). I never tried Ubuntu though
vagrantc has joined #beagle
Guest88 has joined #beagle
Guest88 has quit [Client Quit]
rob_w has joined #beagle
ikarso has joined #beagle
<mattb0ne>
hnv: I will try that
vagrantc has quit [Ping timeout: 250 seconds]
vagrantc has joined #beagle
mattb0ne has quit [Remote host closed the connection]
<zmatt>
hnv: though people should be warned that booting from uSD when there's a substantially different distro on eMMC can cause weird problems due to u-boot incompatibility, solvable using the S2 button or by simply wiping eMMC (or at least wiping the bootloader from eMMC)
ikarso has quit [Quit: Connection closed for inactivity]
starblue1 has quit [Ping timeout: 240 seconds]
starblue1 has joined #beagle
<hnv>
Right
<jfsimon1981>
Hi good afternoon
otisolsen70 has joined #beagle
vagrantc has quit [Quit: leaving]
buzzmarshall has joined #beagle
SJFriedl has quit [Read error: Connection reset by peer]
rcn-ee_ has quit [Quit: Leaving]
rcn-ee has joined #beagle
rob_w has quit [Quit: Leaving]
<fakuivan>
I'm trying to flash the eMMC on a beaglebone black, the instructions I've found specify that the flashing is done once all LEDs turn off, this board is flashing all LEDs at the same time. Is the flashing process complete?
<rcn-ee>
fakuivan, all on and all of; repeat is an error condition.. please plug in a usb-serial adapter into J1 and pastebin your serial log..
<fakuivan>
I don't have a serial adapter on hand :c
<fakuivan>
I've read about this being caused by a 4GB image trying to flash a 2GB eMMC
<fakuivan>
This board has a "3da18 jw896" micron chip as eMMC
<fakuivan>
I didn't try a 2GB image since those are not listed on the main section, but the "Older Debian images"
<fakuivan>
If that's the case, is there a jumper I can bridge to always boot from the sd card?
<rcn-ee>
fakuivan, if it's a 2GB model, there should have been a sticker placed on it saying A6* or A6* but that would have been stuck on the board 10 years ago...
<fakuivan>
A5C in fact
<fakuivan>
This board looks pretty old
<rcn-ee>
Just flash a normal image to a microSD, insert in board... Use your finger hold the boot button, insert power.. then once booted, zero out the eMMC..
<rcn-ee>
Sorry missed my coffee.. that first A6* should have been an A5*..
<zmatt>
fakuivan: I'd generally recommend a console image for those
<zmatt>
if you're comfortable using apt to install whatever packages you want/need after flashing
<fakuivan>
rcn-ee: how do I zero it out? using dd?
<hnv>
what about using a pulldown resistor to bot always from uSD?
<hnv>
*boot
<zmatt>
fakuivan: blkdiscard /dev/mmcblk1
<zmatt>
hnv: possible, but wiping eMMC is more convenient
<zmatt>
fakuivan: or rather, sudo blkdiscard /dev/mmcblk1
<fakuivan>
I see
<fakuivan>
Do I need to mount the emmc?
<zmatt>
no, emmc must not be mounted
<fakuivan>
got it
<zmatt>
of course 2GB is plenty of space for many applications, just not for bloated images that include everything and the kitchen sink ;)
<zmatt>
unfortunately the old micron eMMC was also kinda slow
set_ has quit [Ping timeout: 240 seconds]
<zmatt>
(though sd card may be slower still)
<fakuivan>
This board will be used with a touch screen cape
<fakuivan>
So I'm guessing a GUI will be mandatory
<zmatt>
GUI doesn't necessarily require much space
<zmatt>
depends on what kind of gui
<fakuivan>
that and a web browser, those are pretty bloated from what I understand
<rcn-ee>
fakuivan, "a web browser".... circa 2008, or circa 2022... that alone is bloated...
<zmatt>
e.g. a single-window-fullscreen qt5 application running directly on the framebuffer doesn't require much space at all
<zmatt>
fakuivan: a web browser? you have my condolences
<fakuivan>
It's for an electron app, so sort of a web browser
<rcn-ee>
fakuivan, it's going to be slower then crap...
<zmatt>
(and possibly run out of memory)
<rcn-ee>
512Mb... electron + xorg.. (and probally web-browser)... yeah your out of memoryu...
Guest76 has joined #beagle
<jkridner>
3 months of unread messages.... yeah, not likely to read those. :-)
<Guest76>
Hello,
<Guest76>
I am a Senior Computer System Engineering student that needs the board as controller for a drone project, but I need to understand some critical points that are not clear. So who can I ask ?
<jkridner>
read the topic.... just ask, don't ask to ask.
<jkridner>
I've built a few quadcopters. I like BeagleBone Blue and Ardupilot for that. Depends on what you want to get into. There are small, cheap, open-source MCU-based controllers out there.
<Guest76>
I am thinking of building the fight controller from scratch. is that possible with beagle blue ?
<zmatt>
Guest76: with enough time and dedication you can build anything from scratch
fakuivan has quit [Read error: Connection reset by peer]
florian has quit [Quit: Ex-Chat]
<Guest76>
those links are to install aurdopilot on beaglebone , I am thinking about building a flight contoller, but thanks anyway.
<Guest76>
yes, i know its possible , but is there any controllers that are better from othe in building flight controller from scratch ?
<Guest76>
other**
<rcn-ee>
Guest76, so your asking us to help you build it from scratch?
<zmatt>
it may be worth using off-the-shelf software to get the hardware side working before trying your hand at custom software, that way you avoid debugging software and hardware at the same time
<zmatt>
your question is confusing
<zmatt>
if you just want to drop in a custom flight control algorithm, presumably your best bet is customizing ardupilot so you can reuse the code that deals with stuff like hardware interfacing
<zmatt>
of course if you want to start entirely from scratch, that's totally an option... if you have the time to spend on that (including the time to acquire the necessary knowledge)
<Guest76>
i am sorry is my questions seems confusing, that actually reflects how i am also confused in my thoughs. how much time it may require building it from scratch?
<Guest76>
if**
<zmatt>
that seems like an impossible thing to answer, given the vagueness of the scope of the project and the fact that it will heavily depend on your abilities
<Guest76>
and are you saying that i can add or edit functions on arudopilot program so it can function the way i want ?
<zmatt>
ardupilot is open source, so yes
<Guest76>
what language do i need to use for the program ?
lucascastro has quit [Read error: Connection reset by peer]
<zmatt>
if that's not information you're able to find out on your own, I'm worried for your project
lucascastro has joined #beagle
Guest76 has quit [Ping timeout: 256 seconds]
Konsgn has joined #beagle
Guest80 has joined #beagle
<Guest80>
Hello
<Guest80>
I want to ask about beaglebone blue
<Guest80>
Can you help me
Guest80 has quit [Client Quit]
Guest80 has joined #beagle
Guest80 has quit [Client Quit]
Guest80 has joined #beagle
Guest80 has quit [Client Quit]
fakuivan has joined #beagle
<fakuivan>
rcn-ee: I might reconsider rebuilding the app for NodeGUI
<fakuivan>
It uses Qt in the background, so no chromium
mattb0ne has joined #beagle
<mattb0ne>
mattbone is back with problems
<mattb0ne>
i am getting dns server errors
<mattb0ne>
i may of blew things up with resolv.conf file
<zmatt>
resolv.conf is normally auto-generated and should not be touched
<hnv>
fakuivan: I was looking for a lightweight html+css rendering tool...
<fakuivan>
Qt supports css, I think NodeGUI is only responsible for translating the html components to the Qt ones
<mattb0ne>
what if i did zmatt
<mattb0ne>
is there a way to force an auto generation of the file
<mattb0ne>
i cannot ping 8.8.8.8 at the moment
<zmatt>
mattb0ne: typically it would be regenerated at boot, but it depends a bit on what you did
<zmatt>
if you can't ping 8.8.8.8 then your bbb doesn't have internet access
<zmatt>
which is not a problem related to resolv.conf
<mattb0ne>
hmmmm
<mattb0ne>
had this working and like all things beagle it is not cooperating
<mattb0ne>
the LCD cape has gone kaputz and I lost internet connection after having this work
<mattb0ne>
windows sucks
<mattb0ne>
ok I had to disable sharing and reenable
<mattb0ne>
now on to the cape
<mattb0ne>
need your expertise zmatt
<mattb0ne>
this cape once worked and now I cannot get LED to light up when the board is plugged in
<mattb0ne>
I had two of the same LCD cape and the other one power cycles
<mattb0ne>
I already did the modidication you suggested by taking out the R1 resistor
<mattb0ne>
ok the 2nd LCD cape power cycles and a completely different brand also power cycles
<hnv>
The detection and overlay happens at U-Boot stage?
<zmatt>
this is not hopeful, it doesn't look like it recognized your cape
<zmatt>
yes
<zmatt>
I thought it woulld also show the identifiers of detected capes but maybe I'm wrong
<fakuivan>
@zmatt: rip. Is there anything obvious I could try?
<zmatt>
check which of /sys/bus/i2c/devices/2-005[4-7]/eeprom exists and then hexdump -C /path/to/eeprom | head that one
<fakuivan>
`ls /sys/bus/i2c/devices/2-005{4..7}/eeprom` throws "cannot access '/sys/bus/i2c/devices/2-0054/eeprom': No such file or directory" for all of them
<zmatt>
ehhhhhh
<fakuivan>
The cape also came with a DVD drive, I could boot up an old server of mine and see if there's anything useful about the board
<zmatt>
well that at least explains why your cape wasn't autodetected
<zmatt>
sounds like it doesn't even have an identification eeprom