<zmatt>
ugh, that looks like the pwm output is being annoying about changing the frequency
<set_>
frequency only works...
<set_>
1. If it is under 100.
<set_>
2. above 0.
<set_>
So far at least.
<set_>
The lower the frequency, the faster the LED fades on/off.
<zmatt>
I seem to recall there's a bug in the driver where once you set the frequency of both outputs of one ehrpwm device (which must always use the same frequency), you can no longer ever change the frequency even if both outputs are disabled
<zmatt>
frequency has no effect on fade time
<set_>
Hmm.
<set_>
I can see it!
<set_>
Well, it is more of a blink now instead of a fade.
<zmatt>
using a low frequency just causes visible flicker
<set_>
Right.
<set_>
Dang.
<set_>
So, dang. I guess that is it.
<set_>
I will read about the sysfs pwm interface some more and keep trying.
<set_>
I am taking some diploma class online for C programming now. So, back to the books!
<set_>
Hopefully, they teach me something that will become stuck instead of this fly-by-night tutorials that I keep reading?
<zmatt>
to fix the issue with changing the frequency, just reboot
<set_>
Okay. So, once I get the frequency down pat, keep the boot. But every time I need to change frequency, I need to reboot?
<zmatt>
if I remember correctly you can change the frequency fine as long as you only ever use one of the two outputs of a pwm instance, e.g. *either* /dev/bone/pwm/1/a *or* /dev/bone/pwm/1/b but not both
<zmatt>
this is assuming the issue is what I think it is
<set_>
Oh. Okay.
<zmatt>
once you use both, you can't change the frequency anymore... at least, that was the bug I seem to remember, I'm too lazy to test it right now
<set_>
No issue. I am only using p9.16 so far.
<set_>
so, /dev/bone/pwm/1/b/.
<set_>
rebooting!
<set_>
NameError: name 'seconds' is not defined
<set_>
I defined it and it just turns on.
<zmatt>
hmm, am I not allowed to use a previous parameter in a default argument for the next parameter in python?
<zmatt>
I know javascript is fine with doing that, maybe python isn't
<zmatt>
and I guess it may be nicer to just always use the current led value as from-value instead of having to specify it manually: https://pastebin.com/RKEHTcm0
<set_>
Okay.
<set_>
I will test it.
<set_>
That works too. My led is a bust.
<set_>
It is so dim.
<set_>
Hey @zmatt: When messing w/ CAN1 on the BBB, would I need to have it plugged into another piece of hardware to read specifics on the routes of the CAN interface? Does that make sense?
<set_>
Or...
<set_>
Can I just plug in the tranceiver to the BBB on CAN1 and get readings or does it need to be plugged into the OBD-II port on a vehicle?
<set_>
I tried to set up wireshark so I can visually see what CAN1 is doing on the BBB w/ my tranceiver.
<set_>
Wireshark does not run. Too much consumption probably.
harshil has joined #beagle
ft has quit [Ping timeout: 244 seconds]
ft has joined #beagle
otisolsen70 has joined #beagle
otisolsen70 has quit [Ping timeout: 250 seconds]
otisolsen70 has joined #beagle
GenTooMan has quit [Read error: Connection reset by peer]
SJFriedl has joined #beagle
GenTooMan has joined #beagle
vagrantc has joined #beagle
brook has joined #beagle
brook_ has quit [Ping timeout: 248 seconds]
brook has quit [Read error: Connection reset by peer]
brook has joined #beagle
brook has quit [Remote host closed the connection]
brook has joined #beagle
SteveMarple has quit [Remote host closed the connection]
lucascastro has joined #beagle
Guest48 has joined #beagle
<Guest48>
i am working with pulse audio and want to use a microsd as a directory.
<Guest48>
anyone familiar with the situation?
<zmatt>
?? what do these two things have to do with each other?
<zmatt>
(also, pulseaudio is something you generally only use on desktop systems)
<Guest48>
I have debian installed on the beaglebone and can't find the microsd directory path
<zmatt>
there isn't one unless you do one of 1. mount it manually 2. configure an fstab entry to mount it automatically, or 3. install some service that mounts removable media automatically
<Guest48>
can you guide me on completing this process?
<Guest48>
I saw a tutorial online on buidling a multi room audio system with Google Home and MPD using the beaglebone black
harshil has quit [Remote host closed the connection]
<Guest48>
I did every step but got stuck trying to change the directory to my SD card so that Pulse Audio could pull music from the SD card instead of the default directory
<zmatt>
ah
otisolsen70 has quit [Quit: Leaving]
<zmatt>
you mean where mpd can pull music from
<Guest48>
yes sir
<zmatt>
create an empty directory where you want the mountpoint for the sd card to be, e.g. /mnt/sd
<Guest48>
I don't know how
<zmatt>
sudo mkdir -p /mnt/sd
<Guest48>
i did it and then it asked for the password
<zmatt>
it's asking for the password of the account you're logged in as
<Guest48>
i entered it and its back to the debian@beaglebone
<zmatt>
now add the following line to the /etc/fstab config file:
<zmatt>
you can edit the config file e.g. with: sudo pico /etc/fstab
<Guest48>
i will type it now
<Guest48>
there is two lines already
<zmatt>
once you've added that line, it should mount automatically at boot. you can also mount it immediately (without having to reboot) using: sudo mount /mnt/sd
<Guest48>
should i just type under them
<zmatt>
yes, don't touch any existing lines
<Guest48>
i am done typing it
<Guest48>
exit and save?
<zmatt>
note that this will give mpd write-access to the card... I don't know if it has any use for that (e.g. for organizing music), but if it doesn't or you don't want it to have write-access to the card, use "uid=debian" instead of "uid=mpd" in that line
<zmatt>
(the uid option in this line is used to specify which user on the system will "own" the contents of the sd card)
<zmatt>
after that yes save and exit
<zmatt>
and then, like I said, sudo mount /mnt/sd
<Guest48>
I have the link for the tutorial
<zmatt>
I found it 10 minutes ago, I know how to use google ;)
<Guest48>
apologies
<Guest48>
I didn't intend to depreciate your knowledge
<Guest48>
so I will type sudo mount /mnt/sd
<zmatt>
yeah, once you've executed that, the contents of your sd card should be accessible at the path /mnt/sd
<Guest48>
it says wrong fs type, bad option, bad superblock on /dev/mmcblk0p1, missing codepage or helper program, or other error
<zmatt>
that suggests the sd card doesn't have a FAT filesystem on it
<Guest48>
format to fat?
<zmatt>
do you have any idea how the card has been formatted?
<Guest48>
fat32 i believe
<zmatt>
well it doesn't seem like it
<zmatt>
try: sudo file -s /dev/mmcblk0p1
<Guest48>
i used a windows laptop
<Guest48>
i will format to fat32 now
<Guest48>
nevermind it was ExFAT
<Guest48>
Should i use a mac to format it perhaps?
<zmatt>
I'd suggest using fat32
<zmatt>
you can use the beaglebone to format is
<Guest48>
I only had two options on windows
<Guest48>
NTFS or ExFat
<Guest48>
I will try to format via ma
<Guest48>
Mac
<zmatt>
the way to format it on the beaglebone would be: sudo mkfs.vfat -n MUSIC /dev/mmcblk0p1
<zmatt>
("MUSIC" here is the name given to the disk)
<zmatt>
formatting using a mac should work to
<zmatt>
probably
<Guest48>
it says I can format MS-DOS(FAT)
<zmatt>
yep that's fine
<Guest48>
i have reset and mounted
<zmatt>
btw, note that once the card is mounted you should preferably not just remove it without unmount it first using "sudo umount /mnt/sd" (note that's "umount", not "unmount")
<Guest48>
I will keep that in mind and save the line
<zmatt>
anyway, you can now just configure /mnt/sd as music directory in mpd's config
<zmatt>
as explained in the tutorial
<Guest48>
Do i put the music straight into the drive or should i put it in a folder?
<zmatt>
how you organize your music on the sd card is up to you
<zmatt>
if you configured uid=debian in the fstab line (which in retrospect I should probably have used instead of uid=mpd) then you can also use any SFTP program to transfer files via the network to the sd card while it's mounted on the beaglebone
<Guest48>
I have the beagleboard connected via ethernet and USB but i tried using the ip address given on the site and it didn't work
<zmatt>
192.168.7.2 should work if connected via usb to windows or linux, 192.168.6.2 should work if connected via usb to mac or linux
<zmatt>
when connected via ethernet it'll get an ip address from the router on your network. depending on the router, the beaglebone may be findable using its hostname "beaglebone"
<zmatt>
using the hostname "beaglebone.local" should work on any mac or linux system regardless of how the beaglebone is connected (usb or ethernet)
<Guest48>
i will try now
<zmatt>
it might also work on windows 10+, not 100% sure about that though (I don't use windows)
<Guest48>
I unmounted the SD but when I put it back in, I had to mount it through a command.
<zmatt>
yes
<Guest48>
There is no automatic way to do this?
<Guest48>
auto mount?
<zmatt>
not a super easy way. there exist services that do that for you like udisks but I don't really have experience with them
<Guest48>
no worries
<Guest48>
I will just remember to unmount and mount
<zmatt>
it will however automatically (try to) mount it at startup
<zmatt>
another option would be to enable file sharing on your music directory on windows and access it directly from mpd, but that would require your windows pc to be available to be able to play music. I'm guessing the intention here is to have a self-contained solution
<Guest48>
correct
ketas has quit [K-Lined]
<Guest48>
Hello again
<Guest48>
I just launched MPD interface and on the bottom is says ncmpcpp: Timeout while connecting
<Guest48>
also no active mpd connection
<Guest48>
I don
<Guest48>
i don't know what has to be done
<zmatt>
are you running ncmpcpp on the beaglebone or on another computer? in the latter case you need to provide it with the hostname or ip address of the beaglebone using the --host option
<Guest48>
beaglebone
<Guest48>
I am getting the media from the SD card so do i needed to provide it with ip address
<Guest48>
also how to we happen to do this?
<zmatt>
then presumably mpd isn't actually running, check with systemctl status mpd
<zmatt>
??
<zmatt>
I don't know what you meant by that last question
<Guest48>
i have tried yet
<Guest48>
I will check the status
<zmatt>
I was just saying that if you run an mpd client (such as ncmpcpp) on a different computer to control mpd on your beaglebone, you'll need to pass the hostname/ip of the beaglebone to the mpd client
<zmatt>
if you run an mpd client on the beaglebone itself then that's not needed, it'll default to connecting to mpd on the same device
<Guest48>
active says failed
<Guest48>
Failed to start Music Daemon
<Guest48>
also code=exited, status =1/Failure
<zmatt>
yeah so something is wrong, e.g. perhaps due to a configuration mistake... you'll need to check the logs to see what's wrong. I can't help you in detail right now, I kinda need my hands available to eat my pizza ;)
<Guest48>
no worries!
<Guest48>
Would you like me to chat in ten minutes?
<Guest48>
or at what time can I reach out again?
<Guest48>
if you don't mind as I don't want to cause any inconvience
<zmatt>
I suggest just sticking around, maybe I'll have time later, maybe someone else has time
<Guest48>
ok
<zmatt>
if your beaglebone has internet access via ethernet, try: journalctl -u mpd | pastebinit to create a url to share your mpd's logs
<zmatt>
I do see that line 332 is missing an ending ", and all three auto_output blocks are missing a closing }
<zmatt>
*audio_output blocks
<zmatt>
yeah the error is slightly misleading, because it hasn't seen a } yet it thinks on line 324 it's still inside the audio_output block you started at line 319
<zmatt>
and because it's still inside an audio_output block, it's expecting a line of the form option "value" which line 324 isn't
<Guest48>
can i share the revised file?
<zmatt>
you don't need to ask that, just give the link :P
<zmatt>
oh yeah, you uncommented line 239 and 247 but there's no (uncommented) settings in there
<Guest48>
should i just close the quotes on the lines?
<zmatt>
remember that lines that start with a # are just comments, they're ignored, so this is what your config file actually looks like to mpd: https://pastebin.com/raw/eYCAfQbD
<zmatt>
that empty audio_output { } block you've got is not valid
<zmatt>
so just comment out those two lines (line 239 and 247)
<Guest48>
i will attempt to try again
<Guest48>
it worked but i may have forgotten to mount the sd
<Guest48>
let me check
<Guest48>
it works but now it isn't importing any music from the sd card
<zmatt>
note that ncmpcpp probably by default opens in the (initially empty) queue window, the file browser is window 3 (accessed by pressing 3) .. at least it's like that for ncmpc so I assume also for ncmpcpp
<Guest48>
yes
<Guest48>
it says empty
<Guest48>
although i have one song on the sd card
<zmatt>
what does ls /mnt/sd show?
<Guest48>
how do i leave the ncmpcpp menu to check
<zmatt>
q
<Guest48>
i restarted the board
* set_
watches to learn more!
<Guest48>
no such file or directory
<zmatt>
uhh what
<Guest48>
i am confused since we did everything initially
<Guest48>
i also checked if it was mounted
<zmatt>
sure you didn't just make a typo?
<set_>
soap operas in mcu instances!
<zmatt>
set_, can you wait with your usual word salad contributions till some other time?
<set_>
Sure. Yes sir.
<Guest48>
its ls/mnt/sd
<zmatt>
Guest48: ls /mnt/sd
<Guest48>
L or i
<zmatt>
lowercase L
<zmatt>
and the space between ls and /mnt/sd is not optional :P
<Guest48>
its showing my file now
<Guest48>
let try to run ncmpcpp
<Guest48>
still says empty
<Guest48>
should the audio file be a certain format?
<zmatt>
I mean, it should be a format mpd supports, but I'm pretty sure it supports quite a lot
<Guest48>
i used mp3
<zmatt>
that's definitely fine
<Guest48>
what seems to be the issue then?
<Guest48>
the config file looked correct
<Guest48>
the name was right
<zmatt>
yeah, I have no idea
<Guest48>
but do we have to add ls to the path
<Guest48>
maybe that is a solution?
<zmatt>
???
<Guest48>
the path was only written as /mnt/sd
<zmatt>
ls is a command to list files
<zmatt>
try telling mpd to rescan the music directory using: mpc update --wait
<zmatt>
I would assume it does that automatically at startup but maybe I'm wrong about that
<Guest48>
that would be in the central console
<zmatt>
in the shell yeah
<zmatt>
there's also a way to trigger that from within ncmpcpp but I don't know the key for that
<Guest48>
it says command not found
<zmatt>
install with sudo apt-get install mpc
<zmatt>
(mpc is a very simple mpd client useful for sending individual commands to mpd)
<Guest48>
installing now
<Guest48>
its done
<Guest48>
tried ncmpcpp and it still shows 0
<zmatt>
in its file browser tab?
<Guest48>
yes
BB-Flash has joined #beagle
demirok has quit [Quit: Leaving.]
<zmatt>
then not sure what's going on, sorry... I'm also kinda out of support-giving-energy
<Guest48>
i did a restart as it solves some common issues
<set_>
Have no fret, I am here for you!
<zmatt>
set_: please try to not confuse people more than they already are :P
<set_>
Let me go and look up what exactly is going on!
<set_>
Fine.
<zmatt>
like, I know you mean well, but...
<set_>
@zmatt: If you are too tired, it is going to be an all nighter!
<set_>
I know, I know.
<set_>
I mean well but I revert and octupus stuff.
<Guest48>
zmatt I apologize for the inconvenience I have caused
<set_>
it is to the highest regard I octopus salad the equation.
<Guest48>
I am a noob at this stuff and you definitely helped close the gap in my understanding
<BB-Flash>
Hey guys, having an issue with a GPS unit with an FTDI driver... used to work fine before and provided a /dev/ttyUSB0 serial port but no longer does on the new units... old driver was "Prolific USB-to-Serial Comm Port" on Win and new one is listed as "Prolific PL2303GC USB Serial COM Port"... just leaving it here in case someone has any insight and
<BB-Flash>
ran into the same issue. Thanks!
<set_>
Okay. Fine, I give up. BBL!
<set_>
am I allowed to try help yet?
<set_>
ARM may have a driver...I will research it and see if it is something that comes w/ a driver or not on Win 7/8/10/11?
<BB-Flash>
I have looked around for a driver and have just been going around in circles
<BB-Flash>
The specific device is BU-353S4
<set_>
Oh. I found there is a prolificusa site. I am sure they have drivers but I think, from what I read, the older driver may work w/ newer OSs.
<set_>
Let me dig around some more.
<BB-Flash>
thanks! As soon as my BB is up, I will copy past the dmesg --follow output from one vs the other
<set_>
Yeppers. prolificusa.com has drivers but further down the page. Not the first one!
<set_>
BB-Flash: Use pastebin.com instead.
<set_>
Do not paste the entire dmesg in this chat, please.
<BB-Flash>
ha ha, got it... no I won't I will just grab the end of it :-D
<set_>
Use pastebin.com.
<set_>
Please. Some people get tired of me chatting nonsense. I can only do so much.
<set_>
Speaking of...where did everyone go?
<BB-Flash>
This forum is usually this quiet...periodically there is some chatter but otherwise quiet
<BB-Flash>
[ 182.320279] usb 1-1: Product: USB-Serial Controller D
<BB-Flash>
[ 182.320286] usb 1-1: Manufacturer: Prolific Technology Inc.
<BB-Flash>
[ 182.406577] usbcore: registered new interface driver usbserial_generic
<BB-Flash>
[ 182.406667] usbserial: USB Serial support registered for generic
<BB-Flash>
[ 182.458412] usbcore: registered new interface driver pl2303
<BB-Flash>
[ 182.458534] usbserial: USB Serial support registered for pl2303
<BB-Flash>
[ 182.541310] usb 1-1: pl2303 converter now attached to ttyUSB0
<set_>
pl2303. Okay. What is the issue?
<set_>
ls -l /dev/ttyUSB0
<BB-Flash>
314.827567] usb 1-1: new full-speed USB device number 4 using musb-hdrc
<BB-Flash>
[ 314.976747] usb 1-1: New USB device found, idVendor=067b, idProduct=23a3, bcdDevice= 1.05
<BB-Flash>
[ 314.976766] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<BB-Flash>
[ 314.976775] usb 1-1: Product: USB-Serial Controller
<BB-Flash>
[ 314.976782] usb 1-1: Manufacturer: Prolific Technology Inc.
<BB-Flash>
[ 314.976789] usb 1-1: SerialNumber: DZBVb106315
<set_>
Hmm.
<BB-Flash>
so the first is the one which works fine... the one with a newer driver does not give a ttyUSB0
<set_>
Right.
<set_>
The newer driver does not work. Use an older driver.
<set_>
At least, that is the consensus.
<BB-Flash>
It's usually plug and play and I have never messed with it
<set_>
If you got search pl2303 Windows 11, there are a bunch of ideas on ms's site.
<set_>
They all lead to the driver at prolificusa.com but the prolificusa people say, and MS's site says, use the driver further down the page.
<set_>
I think it may be the last entry on the page.
<set_>
it actually is a MS thing.
<set_>
the prolificusa site says that it is WHQA or whatever certified. I guess it is okay?
<BB-Flash>
Is that relevant for BB too? I was hunting around for an older PL2303 Linux driver to see if I can override what's getting loaded automatically when it's plugged in
<set_>
I think not. It is the driver and how Windows is seeing it, using it, and communicating to it.
<set_>
Now. I could be wrong. I only know so much. Let me check.
<BB-Flash>
To my knowledge pl2303 comes with the BB debian OS and that's how I have always gotten a ttyUSB0 when the unit is plugged in. With these newer units, I did not, so I plugged into my Windows PC and saw that there were two different drivers being loaded - pl2303 v/s pl2303gc
<set_>
usb to rs232?
<BB-Flash>
Yep that's correct
<set_>
Okay.
<BB-Flash>
The FTDI chip in the device handles that automatically
<set_>
So, there is a problem w/ the newer driver says the source of the product. Now, if Linux help, good. I am sure there are drivers for linux but...
<BB-Flash>
What's the issue you are facing? Maybe I can offer some help in some fashion... I am no kernel expert and pretty much work on out of the box configuration but have deployed BBs in hundreds of live production environments
<set_>
Nice!
<set_>
No issue here except for GenTooMan having me drop his name around here...
<set_>
Are you using Linux or this bridge to open a terminal?
<set_>
Sorry. Let me better ask that question...
<BB-Flash>
ha ha, I was wondering what you meant:-) I am chatting from my Windows PC, but yeah connected via BB to the USB GPS unit
<set_>
Are you using a Linux OS development env. or are you just trying to terminal into the BBB via the bridge?
<BB-Flash>
yeah I am doing a putty into the BB
<set_>
From Win 11?
<BB-Flash>
Win 10
<set_>
Okay.
<set_>
So, I think there is a driver but I do not think the BBB needs this driver to communicate just yet. I am about small steps.
<BB-Flash>
yeah BB usually never needed a driver and directly usually gave me ttyUSB0
<set_>
oh... /dev/ttyUSB0 is for usb. Yes. Or it used to be...have you tried /dev/ttyACM0 or /dev/ttyGCM0 <<< guessing on this last one (sort of).
<set_>
Let me plug in.
<set_>
oh?
<set_>
You do not find /dev/ttyUSB0?
<BB-Flash>
Yeah I didn't want to confuse why I described what's going on in Device Manager but there seems to be a correlation... one device when plugged in shows up as pl2303, the other shows as pl2303gc
<BB-Flash>
the one with pl2303 when plugged in into BB provides the ttyUSB0, the pl2303gc does not
<set_>
One of those are the updated (supposedly nonworking driver).
<BB-Flash>
yep
<BB-Flash>
but yeah no way to connect to it, at least I have not figured it as of now
<set_>
Hmm. Okay.
<set_>
Try the header on it.
<set_>
I think it is tty0.
<BB-Flash>
Here they are back to back
<BB-Flash>
1397.299563] usb 1-1: new full-speed USB device number 5 using musb-hdrc
<BB-Flash>
[ 1397.448448] usb 1-1: New USB device found, idVendor=067b, idProduct=2303, bcdDevice= 4.00
<BB-Flash>
[ 1397.448467] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
<BB-Flash>
[ 1397.448476] usb 1-1: Product: USB-Serial Controller D
<BB-Flash>
[ 1397.448483] usb 1-1: Manufacturer: Prolific Technology Inc.
<BB-Flash>
[ 1412.943552] usb 1-1: new full-speed USB device number 6 using musb-hdrc
<BB-Flash>
[ 1413.092502] usb 1-1: New USB device found, idVendor=067b, idProduct=23a3, bcdDevice= 1.05
<BB-Flash>
[ 1413.092521] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<BB-Flash>
[ 1413.092529] usb 1-1: Product: USB-Serial Controller
<BB-Flash>
[ 1413.092536] usb 1-1: Manufacturer: Prolific Technology Inc.
<BB-Flash>
[ 1413.092543] usb 1-1: SerialNumber: DZBVb106315
<BB-Flash>
oh you think it's tty0?
<set_>
No.
<set_>
I think tty0 is the 'FTDI' header on the BBB.
<set_>
I think it gets routed to S0.
<set_>
UART0.
<set_>
so, /dev/ttyS0 should be UART0, right?
<BB-Flash>
I have tried ttyS0
<set_>
So, if you use your USB to FTDI on the header for /dev/ttyS0 and use config-pin p9.whatever uart && config-pin p9.whatever uart, then you can ultimately bash in.
<set_>
That is one idea w/out using the older driver...
<set_>
I mean...USB == PWR, GND, UART!
<set_>
Oh.
<set_>
It is like their driver is connecting and then disconnecting from another driver.
<BB-Flash>
ok, I deploy in production environments and there is no scope to change stuff around unfortunately so if it does not work with the plug in USB, I will have to look for some other option and I am looking for it... just that the lead times on different components are months now
<set_>
OTG. Okay, I am getting somewhere.
<set_>
Right.
<BB-Flash>
So it looks like PL2303GC is connecting in some other way to BB that it's not leading to registering on ttyUSB0
<set_>
Yeppers.
<set_>
So, the musb gadget thing has changed a bit.
<set_>
I cannot recall what happened but the whole identity of WiFi and Ethernet has changed, too.
<set_>
So, instead of using connman, people have mitigated to the networkd system for connectivity.
<BB-Flash>
6. pl2303// add pl2303, save, close modules , S6.png
<BB-Flash>
7. reboot// reboot OS , S7.png
<BB-Flash>
8. plug in new cable, and then enjoy!
<BB-Flash>
sorry to paste walls of text
<set_>
use pastebin.com
<set_>
I am not sure if that will help, number 4.
<set_>
Do you have a large ARM system?
<set_>
So, they do not have a real make file.
<set_>
They have a LKM.
<BB-Flash>
Sorry I don't understand what you mean by if I have a large ARM system, the BeagleBone is the only Linux device I use
<set_>
oh.
<set_>
Okay.
<BB-Flash>
4.19.94-ti-r42 is my kernel
<set_>
Aw.
<set_>
Okay.
<set_>
I think you need a larger ARM system to build your LKM and then port that to the BBB.
<BB-Flash>
So I assume I have to use 4.19_ok
<set_>
Right.
<BB-Flash>
Don't think I need an ARM system, I have another WiFi adapter for which I build the driver on the BB itself, it takes some time, like 35 min but it does work
<set_>
Well, at least the same C/C++ and gcc versions, presumably.
<set_>
Wozzers.
<set_>
I guess I am wrong.
<set_>
That is a LKM, right. Loadable Kernel Module.
<BB-Flash>
I am just going to use psftp to move the folder over and try to follow the instrucitons
<set_>
Okay. Good luck...I would not do that move.
<BB-Flash>
If my device gets bricked, not a big deal, I have about 50 more to destroy :-D
<set_>
You can always reflash it.
<set_>
Why are you using kernel 4.19.x now?
<set_>
Did you build it or was it part of the BBB.io peoples' builds?
<BB-Flash>
Long story, I usually use BeagleBone Black Wireless, I am forced to use BeagleBone black regular with the Ethernet port because BBBW is not available for like months
<BB-Flash>
I am using 10.3 flasher image which by default installs the 4.19 kernel
<set_>
Right.
<set_>
They have updated images. Who knows? This is why I brought up usb-gadgets or whatever it is called. It may just work.
<set_>
I am not sure, for sure.
<set_>
I am sorry. I thought you had an enormous ARM machine to help w/ building and LKM, rebuilding the kernel, and so on.
<set_>
It is hard w/out those machines.
<set_>
TI and bbb.io has them.
<set_>
I think the x15 is one or let me check.
<BB-Flash>
ok, just built the driver (or whatever that's called) and about to test!
<set_>
Nice!
<set_>
Yeppers. The x15 has some capabilities for producing but not like the TI boards but this chat does not accept TI built boards (I think).
* GenTooMan
accidentally drops set_'s name and can't find it now.
<set_>
Here I is!
<set_>
am. Here I am!
* set_
wonders where the slaping fish tails ever went?
<GenTooMan>
hopefully the tails are still on the poor fish...
<set_>
I know. We got local yocals here fishing and then stomping on the fish instead of eating them. LA?
<set_>
It made national news on my Google AI bout of a news feed!
<set_>
Oh and when I say accept, "accept" means does not support. (I think).
Guest48 has quit [Quit: Client closed]
<BB-Flash>
did not work :-(
<set_>
Uh.
<set_>
I know...LKM. Rebuild the kernel.
<GenTooMan>
just blame set_ works for me... blaming set that is.
<set_>
I think. Let me go and research this a bit more.
* set_
blames himself all the time!
<set_>
Wait. I am set_!
<BB-Flash>
Is there a way to upgrade the Linux kernel on the BB to 5.5 and above?