brook has quit [Remote host closed the connection]
brook has joined #beagle
brook has quit [Remote host closed the connection]
vagrantc has quit [Quit: leaving]
Shadyman has joined #beagle
starblue has quit [Ping timeout: 272 seconds]
starblue has joined #beagle
thinkfat_ has quit [Ping timeout: 240 seconds]
thinkfat_ has joined #beagle
av500 has quit [Ping timeout: 272 seconds]
renrelkha has quit [Quit: bye]
renrelkha has joined #beagle
_whitelogger has joined #beagle
buzzmarshall has quit [Quit: Konversation terminated!]
ikarso has joined #beagle
Raajeshwar has joined #beagle
rob_w has joined #beagle
<Raajeshwar>
We have Beaglebone black wifi boards that are not connecting to the local wifi network. We are able to capture the Journalctl logs. Please do the needful in this issue. Logs are available in the pastebin link: https://pastebin.com/k3sUzG3m
ft has quit [Quit: leaving]
jfsimon1981 has quit [Remote host closed the connection]
jfsimon1981 has joined #beagle
otisolsen70 has joined #beagle
jfsimon1981 has quit [Remote host closed the connection]
jfsimon1981 has joined #beagle
Shadyman has quit [Remote host closed the connection]
Raajeshwar has quit [Ping timeout: 244 seconds]
Raajeshwar has joined #beagle
florian has joined #beagle
set_ has quit [Ping timeout: 260 seconds]
set_ has joined #beagle
Raajeshwar has quit [Ping timeout: 244 seconds]
ikarso has quit [Quit: Connection closed for inactivity]
Raajeshwar has joined #beagle
Raajeshwar has quit [Ping timeout: 244 seconds]
Raajeshwar has joined #beagle
aussetg has quit [Remote host closed the connection]
aussetg has joined #beagle
starblue has quit [Ping timeout: 246 seconds]
starblue has joined #beagle
aussetg has quit [Remote host closed the connection]
aussetg has joined #beagle
ikarso has joined #beagle
xet7 has joined #beagle
uart0_person has joined #beagle
Raajeshwar has quit [Ping timeout: 244 seconds]
Raajeshwar has joined #beagle
uart0_person7 has joined #beagle
uart0_person7 has quit [Client Quit]
uart0_person72 has joined #beagle
uart0_person has quit [Ping timeout: 244 seconds]
<uart0_person72>
Hi zmatt ,
<uart0_person72>
someone said that after the patching I needed to go to kernel device tree adjust the console uart used for output
<uart0_person72>
that just means selecting the baud right?
<zmatt>
uart0_person72: I'm pretty sure no DT changes are needed
<zmatt>
unless you want the console to actually *work* and not be merely out of the way
<zmatt>
but my impression was you don't actually care about the console, you just want it off of uart0
<uart0_person72>
yes that's it
<uart0_person72>
then the person misunderstood me
<uart0_person72>
ok
<uart0_person72>
about the uart, do I need to set the baud anywhere, or can I just set inside a script using a serial library?
<zmatt>
you configure the baudrate (and other settings) of the serial port when you open the port in your software
<uart0_person72>
ok, thanks, thank you very much
<uart0_person72>
you are always so helpful. A few months ago when I was doing a project with pocketbeagle capes you also helped me a lot
nslu2-log has quit [Quit: Disconnecting from stoned server.]
nslu2-log has joined #beagle
Raajeshwar has quit [Ping timeout: 244 seconds]
Raajeshwar has joined #beagle
uart0_person72 has quit [Quit: Client closed]
otisolsen70 has quit [Quit: Leaving]
rob_w has quit [Remote host closed the connection]
ikarso has quit [Quit: Connection closed for inactivity]
brook has joined #beagle
brook has quit [Remote host closed the connection]
brook has joined #beagle
buzzmarshall has joined #beagle
Raajeshwar has quit [Quit: Client closed]
brook has quit [Ping timeout: 240 seconds]
brook has joined #beagle
alan_o has joined #beagle
alan_o has quit [Client Quit]
alan_o has joined #beagle
alan_o has quit [Ping timeout: 244 seconds]
brook has quit [Remote host closed the connection]
brook has joined #beagle
alan_o has joined #beagle
brook_ has joined #beagle
brook has quit [Read error: Connection reset by peer]
florian has quit [Quit: Ex-Chat]
alan_o has quit [Ping timeout: 252 seconds]
av500 has joined #beagle
hnv has joined #beagle
alan_o has joined #beagle
GenTooMan has quit [Ping timeout: 250 seconds]
GenTooMan has joined #beagle
alan_o has quit [Ping timeout: 260 seconds]
vagrantc has joined #beagle
brook_ has quit [Remote host closed the connection]
brook has joined #beagle
brook has quit [Ping timeout: 244 seconds]
brook_ has joined #beagle
GenTooMan has quit [Ping timeout: 244 seconds]
ft has joined #beagle
uart0_person has joined #beagle
alan_o has joined #beagle
hnv has quit [Quit: Client closed]
hnv has joined #beagle
uart0_person has quit [Quit: Client closed]
conjuncture has joined #beagle
DrPatater is now known as Patater
Guest59 has joined #beagle
Guest59 has quit [Client Quit]
brook_ has quit [Remote host closed the connection]
uart0_person has joined #beagle
<uart0_person>
zmatt so I did the steps, but the pocketbeagle is not booting
<zmatt>
that's unfortunate.... maybe check the serial console to see what's going on? oh wait never mind :D
<uart0_person>
I was expecting for that joke
<zmatt>
hehehe
<uart0_person>
So I did everything we talked about it. I downloaded the u-boot, made the modifications to the file you said, every ttys0 became ttys1 and then saved. Then I installed the gcc cross compiler and the dependencies, used the three commands to compile. Found which was the sd name in the machine, that /dev/name_device, used the command you told me to do
<uart0_person>
the backup, then used that two commands to install the two files
<zmatt>
might be a good idea to actually first try this without making any changes to u-boot, just to confirm the build is okay and this much newer u-boot is compatible with your current image
<uart0_person>
you mean do the same steps but without replacing tty?
<zmatt>
yeah
<zmatt>
and obviously skip making the backup this time since you already have one
<uart0_person>
I don't understand in board/ti/am335x/board.c if I need to replace return &eserial1_device for return &eserial0_device or remove it altogether
uart0_person11 has joined #beagle
<uart0_person11>
ok they said eserial1_device = ttyS0
<uart0_person11>
to I just need to find out if eserial2_device is ttyS1 then I can replace them
uart0_person has quit [Ping timeout: 244 seconds]
uart0_person11 has quit [Client Quit]
uart0_person has joined #beagle
brook has quit [Remote host closed the connection]
brook has joined #beagle
zjason` has quit [Read error: Connection reset by peer]
zjason` has joined #beagle
uart0_person has quit [Quit: Client closed]
brook has quit [Remote host closed the connection]
Guest7738 has joined #beagle
<Guest7738>
Hi, I just bought a beaglebone black and I'm trying to get started but I can't download the drivers. I have a Mac with BigSur 11.3 and I'm using the USBA-USBC connector that comes with the beaglebone.
<zmatt>
Guest7738: no drivers should be needed
<zmatt>
usbc ? the bbb has no usbc
brook has joined #beagle
<zmatt>
it has mini-usb
<Guest7738>
sorry mini-usb
<Guest7738>
How do I access the Linux terminal on the beaglebone then?
<zmatt>
it *should* show up as network interface when connected via usb.... though I do vaguely recall there was some kind of issue with apple having managed to break something in newer versions of macos, but I think that has already been worked around in the current beaglebone image?
<zmatt>
of course if you have trouble with usb networking, connecting it via ethernet should work as an alternative (in which case you'd access it using the hostname beaglebone.local, e.g. "ssh debian@beaglebone.local")
<zmatt>
rcn-ee: do the 2020-04-06 images already use CDC-NCM instead of CDC-ECM as workaround for the macOS issue?
<Guest7738>
I'm not sure what you mean by the network interface and current beaglebone image. There's a drive that appears on my desktop that is called Beaglebone and it has files like App, Drivers, scripts, and static
<zmatt>
yeah you can ignore that drive
<zmatt>
I don't think there's anything of use on there
<zmatt>
by network interface I mean... network interface
<zmatt>
to access the beaglebone via ssh or http you need a network connection to it... this can be done either via ethernet or via usb
<zmatt>
people generally connect via usb because that allows for a single cable to be used for poewr and data
<zmatt>
*power
vagrantc has quit [Quit: leaving]
<Guest7738>
How do I check that the network is connected? I'm using the usb cable
<zmatt>
Guest7738: it would show up in networking in system preferences
<zmatt>
Guest7738: or just try ssh debian@beaglebone.local in the terminal
<zmatt>
which should work if you have any network connection to the beaglebone
<Guest7738>
I don't have network connection to the beaglebone
<Guest7738>
I'm trying to manually enter the IP address. Would it be 192.168.6.2?
<zmatt>
manually enter?
<zmatt>
if you don't have a network connection to it when connected via usb then my guess would be the system on the beaglebone doesn't have the workaround for the mac issue yet...
<zmatt>
I don't know if that means it happens to have a really old system (e.g. this beaglebone happened to have been lying on some shelf in a warehouse for a long time before you got it) or maybe the latest official image (2020-04) doesn't actually include this fix yet
<Guest7738>
I'm in Network in Systems preferences on the mac. Under The beagleboneblack, there's configure IPv4 and on the dropdown menu it says manual
<zmatt>
don't do that, use automatic (DHCP)
<zmatt>
but wait, you're saying the beaglebone *does* show up as network interface?
<Guest7738>
It shows up but it says it's not connected
<zmatt>
uhhh
<Guest7738>
I'm not using ethernet, is that part of the issue?
<zmatt>
that doesn't really make sense... if it can detect the interface it should implicitly have a connection
<zmatt>
using ethernet would be a workaround, but that doesn't explain why the usb network interface shows up yet isn't working
<Guest7738>
Is there a key for the wifi I'd have to enter for the beagleboard to connect?
<zmatt>
the beaglebone black doesn't support wifi
<zmatt>
unless you have a beaglebone black wireless (which has wifi+bt *instead of* ethernet)
<zmatt>
(as the name suggests this is an eMMC-flasher image... write it to a microSD card using Etcher (https://etcher.io/) and then boot the beaglebone from that sd card and it should proceed to automatically reflash the eMMC)
<zmatt>
(you could also use a bullseye testing image instead of a buster image, but the bullseye images are still somewhat experimental)
<zmatt>
Guest7738: this is assuming the issue is the one I'm thinking of... I'm not a mac user myself and don't see many mac users here so I don't know whether there's any other mac-specific issues that people might run into
<Guest7738>
ok, I'll have to buy an SD and adapter before I can do that
<zmatt>
that's a useful thing to have anyway
<Guest7738>
Ya, I figured I'll need the extra storage
<zmatt>
for what?
<Guest7738>
I'm using the beagle mostly for data processing/analysis, so I think it'll need more storage than what's already on there