<zmatt> nick1231026: you can find more information about the interconnects in chapter 10 of the AM335x Technical Reference Manual, though for the most part you don't really need to know much about it since the interconnects are mostly invisible to the casual programmer
<zmatt> and I've updated https://github.com/mvduin/py-uio/blob/master/pru-examples/fw/gpio.h to include the definition of the direction register
<nick1231026> Ok, nice. I see I just need to change a bit in the register
<nick1231026> I am a little confused, is this example for beaglebone black? the pru example I am using has different register numbers
<zmatt> yeah, if you know PRU is the only one messing with the GPIO directions of one particular GPIO controller, you can read the controller's direction register once and just keep that around and then if you want to toggle a direction bit you update that cached value and write it to the GPIO controller (keep in mind that reads of things outside PRUSS are relatively slow)
<zmatt> that header is for the AM335x yes, and the example for the beaglebone black specifically
<zmatt> (or beaglebone variants that are sufficiently similar to the BBB)
<zmatt> what example are you looking at?
<zmatt> nick1231026: https://github.com/jadonk/cloud9-examples/blob/master/common/prugpio.h#L54-L58 ... his GPIO0 address is plain wrong (as is the comment above it which writes "am35xx" while it meant "am335x")
<zmatt> other than that they match mine except I add 0x100 to them because all relevant registers are in range 0x100 - 0x194
<zmatt> this allows me to use single-byte register offsets, which allows them to be used as immediate offsets in load/store instructions
<zmatt> since you were talking about doing things "on some cycles" I was kinda assuming you were programming PRU in assembly rather than C
<zmatt> nick1231026: for C you may be interested in this header I wrote: https://pastebin.com/anqLbyav
<zmatt> (the compiler will no doubt generate terrible code for it, but that's business as usual for the PRU C compiler)
nick1231026 has quit [Ping timeout: 260 seconds]
brook has joined #beagle
nick12310 has joined #beagle
brook_ has quit [Ping timeout: 252 seconds]
<nick12310> Ah, thanks I will check the header out.
Guest76 has joined #beagle
<Guest76> Good day / evening everyone.
brook has quit [Ping timeout: 260 seconds]
<Guest76> I'm getting lost in the online sea of outdated documentation and tutorials.
<zmatt> yeah that is a problem indeed
<Guest76> I got an IoT OS of beaglebone Black and I'm trying to set the resolution of the display
<Guest76> I'm using a pretty small hdmi monitor for an IoT project
<set_> Hey! You guys?
<Guest76> last clue was to edit the uEnv.txt file in boot but that did not pan out
<Guest76> Figured I'd try here.
<set_> Super busy...need a break? One break coming up!
<zmatt> Guest76: I mean, normally it will figure out an appropriate resolution for your monitor (based on what the monitor reports is supported), but you can force the selection by appending e.g. video=800x600 or whatever in the cmdline= variable assignment in /boot/uEnv.txt
<zmatt> Guest76: what change did you make in /boot/uEnv.txt exactly?
<Guest76> That's actually what I was trying to do as well. let me quickly peek
<Guest76> That's what the last instruction doc I was reading told me to do as well
<zmatt> well then that doc was right
<zmatt> you sure the monitor supports the resolution you configured?
vagrantc has quit [Quit: leaving]
<Guest76> if it did not support it, it would not display it right?
<zmatt> display it where?
<Guest76> I mean the image would not even show up on the monitor right?
<Guest76> The usual.
<Guest76> When a monitor received unuspported video resolution it would say something like "unsupported resolution" etc
<Guest76> In my case even if I set the argument, it just defaults to 1920x1080
<zmatt> no, if the resolution isn't supported then the kernel will know that (since the hdmi monitor reports which resolutions are supported) and therefore won't allow that resolution to be picked
<Guest76> I see
<Guest76> is it possible to force it
<zmatt> ... probably? dunno
<Guest76> because I have one of those 5" project hdmi monitors that technically supports 1920x1080 but the text is so small you can't read it
<Guest76> so just because the driver supports it, doesn't mean it's gonna be a good experience sort of deal
<zmatt> it's quite possible the monitor only supports native resolution
<Guest76> I had it run at 640x480 on raspbery pi
<Guest76> so it definetely works
<zmatt> huh ok
<Guest76> The chip shortage has me looking at beaglebone
<zmatt> that makes even less sense... it's not like the linux kernel's resolution-selection logic is any different on the beaglebone than on the rpi
<Guest76> I used to run this project on raspberry pi zero and also rpi4 headless
<Guest76> I know, right
<Guest76> that's why I'm stumped as to why it's behaving differently
<zmatt> just to confirm, can you cat /proc/cmdline ?
<zmatt> just to double-check the kernel parameters
nick12310 has quit [Ping timeout: 260 seconds]
nparafe has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
<Guest76> yeah I gotta ssh to copy the output
nparafe has joined #beagle
<Guest76> it did print something out
<Guest76> what's the command to get ip address?
<zmatt> uhh of what?
<zmatt> "ip addr" shows all network interfaces on linux
<zmatt> if that's what you mean
<Guest76> yeah, I want to post here the output of cat, but to do that I gotta ssh into beaglebone
<Guest76> unless you want dusty phone pic of the screen cli
<zmatt> if the beaglebone is connected via usb then you can reach it as 192.168.7.2 (on windows or linux) or 192.168.6.2 (on mac or linux) or as beaglebone.local (on mac, linux, and maybe windows)
<Guest76> console=ttyS0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 lpj=1990656 rng_core.default_quality=100 quiet
<zmatt> I'm not seeing your video config
<zmatt> what _exactly_ did you change in /boot/uEnv.txt ?
<Guest76> let me check the uEnv.txt
<zmatt> you need to find the existing line that configures the "cmdline" variable and append "video=640x480" to it (separated by a space from any existing parameters)
<zmatt> e.g.:
<zmatt> cmdline=coherent_pool=1M net.ifnames=0 lpj=1990656 rng_core.default_quality=100 quiet video=640x480
<Guest76> here's the contents of the uEnv.txt file
<Guest76> One note
<Guest76> I had to add the cmdline= to it
<Guest76> it was not there
<Guest76> PS I am looged in as debian
<Guest76> not as root
<zmatt> it is there, line 59 of your paste
<Guest76> PS I am logged in as debian
<Guest76> OH
<Guest76> I'm blind
<Guest76> one moment
<Guest76> IT WORKED!
<zmatt> there ya go
xet7 has joined #beagle
<Guest76> once again thanks due to me missing something simple
<Guest76> I was losing my mind tbh, thought everything I read was out of date
<zmatt> nope, this wasn't!
<Guest76> thank you very much
<zmatt> actually I think this never changed at any point
<set_> Yay! My turn!
<zmatt> at least not for as long as I've been around here :D
<set_> bbl...dang it.
<Guest76> gotcha
<Guest76> oh btw, how would one retrive the name of the currently used video driver?
<zmatt> the video driver on the am335x is tilcdc
<Guest76> I'm working on something with pygame which runs in SDL2 and it need to have a correct environment variable set to display.
<Guest76> tilcdc it is then
<zmatt> beware that the video capabilities of the AM335x are quite limited, it's an industrial SoC, not a media SoC like the rpi
nick12310 has joined #beagle
<Guest76> Indeed. I wanted to see how much worse or better the beaglebone ran my application
<zmatt> (and its rarely-used potato GPU requires a kernel driver and userspace package that's not installed by default, and which is incompatible with using X11)
<Guest76> first problem after getting the resolution of the cli fixed was to get the pygame running. I actually did get it to launch, and it played the sounds of the application, but did not display the actuall app.
<Guest76> I see.
<zmatt> so I hope you don't need OpenGL ;)
<Guest76> Oh no
<Guest76> it's just 2D stuff
<zmatt> ok
<Guest76> SDL2 supports a few solutions
<Guest76> not as much as SDL1
<zmatt> ohh driver in that sense
xet7 has quit [Ping timeout: 246 seconds]
<Guest76> yes, what did I reffer to ?
<Guest76> my mistake
<zmatt> I assumed which kernel driver is being used
<Guest76> righto.
<zmatt> for this, if you're not using X11 then I'd say try kmsdrm, otherwise I guess directfb ?
<Guest76> I should probably let nick12310 go ahead with his question
<Guest76> he's been attempting to write one a few times when I butt in
<zmatt> anyone can type at any time they want
<Guest76> and with those being the only two supported drivers, I'd say I can look into those.
<Guest76> that and x11
<Guest76> to be honest. my choices right now are - anything that gets this thing to actually launch
<zmatt> Guest76: kmsdrm sounds like the Right Thing to me, assuming it supports any kernel driver with kms and dumb buffer support (e.g. tilcdc)
<zmatt> and not egl or whatever
nick12310 has quit [Quit: Client closed]
<zmatt> I should probably get some sleep
<Guest76> Appreciate the help
xet7 has joined #beagle
<Guest76> Does the video=HDMI-1-A support flpping?
<Guest76> say if the display is mounted upside down?
brook has joined #beagle
<zmatt> tilcdc does not support any kind of rotation or vertical/horizontal flip
<zmatt> the hardware doesn't support it
<zmatt> like I said, _very_ basic graphics support
<Guest76> gotcha
Shadyman has joined #beagle
<zmatt> the AM335x basically has the dumbest video hardware you can get away with for driving a touchscreen ;) not even hardware mouse cursor support. the only reason it has a (crappy) 3d gpu is because it was originally intended to support android (though this has been dropped since) which requires a gpu
<Guest76> I see
<Guest76> I am pretty sure my project isn't demanding in terms of the graphical load
<Guest76> This was the last rendition
<Guest76> Basically a text based adventure game
<zmatt> I would tend to agree
<Guest76> This chip shortage is forcing me to start looking into custom SoCs and running linux on them
<Guest76> I was told, and I now agree, that I can't rely on raspberry pi stock even for a small run
<zmatt> relying on the rpi is a mistake since the SoC is custom for the rpi foundation and not available on the general market
<Guest76> indeed. It was a starting time
<Guest76> oops
<Guest76> prematurely pressed enter
<Guest76> oh dang, you can edit these messages
<Guest76> nice
<Guest76> I actually started this project on an MCU
<Guest76> with Adafruit GFX
<zmatt> uhh no you can't edit messages here
<Guest76> really?
<Guest76> I figured you can
<Guest76> a
<Guest76> nevermind
<Guest76> up arrow does something else
<zmatt> this is IRC, it's state-of-the-1980's technology
<Guest76> hehe
<Guest76> So yeah, I started this project on an MCU, Arduino Due
<Guest76> Atmel SAM3X8E ARM Cortex-M3
<Guest76> just bare metal
<Guest76> It was a pretty good start, but once I started defining game data, like jsons for level data
<Guest76> I had quickly learned about the malloc headaches
<zmatt> I mean, do you really need json or malloc for a game like this?
<Guest76> json was bloated but vert convenient as I used it extensivelt for my game dev projects.
<Guest76> Tehcnically the way the game is made is very modular
<zmatt> then keep the master data in json and write a tool to convert the json to something sensible for the microcontroller :P
<Guest76> I wanted to add expandability to the game
<Guest76> And having been spoilt by scripting languages, it was apparent that a linux solution would be the way
<zmatt> you don't need JSON for that... people make plenty of Super Mario Romhacks and let me assure you it doesn't use JSON ;-)
<zmatt> (nor malloc)
<zmatt> *Super Mario World romhacks
<Guest76> well those games are static in size
<zmatt> some romhacks are pretty big, I know they've managed to patch their way around some limitations of the original game in terms of number of levels
<Guest76> It's less to do with JSON itself and more that dicitonaries make for an extremely easy way to move around data and establish the game world.
<zmatt> anyway, yeah linux-based development does have its comforts and luxuries
<Guest76> There would be a lot of key value pair movement
<Guest76> and for that I'd have to do a lot of memory management
<Guest76> not to mention audio sfx and music playback
<Guest76> individually these elements are alright enough to handle, but once put together on an MCU, it becomes a bit much.
<zmatt> to be fair that's not really any different on microcontrollers than on linux, it's just that you generally have more ram to waste on being sloppy
<Guest76> And linux already handles memory for me
<Guest76> so I just have to keep within the limitations
<Guest76> which is less of a hassle
<zmatt> I mean, that's not really any different on a microcontroller.... like, not from a practical point of view
<Guest76> maybe it's just me
<zmatt> in both cases you just malloc() and don't worry about the details behind the scene
<Guest76> I found I focused more on the game design on the raspberry pi than I did with memory management
<Guest76> adding audio was super easy, with the spi audio solutions
<Guest76> same with ethernet
<Guest76> it's already a part of linux so I didn't have to program my own telnet
<zmatt> yeah, a lot of things are definitely easier to get working
<zmatt> on linux compared to a baremetal environment
<zmatt> mostly just for fun I've done small bits of baremetal programming on the AM335x and before that an even larger SoC.... it's neat to have direct access to so much resources, but it takes ages to actually get anything *done*
<Guest76> indeed.
<zmatt> I do remember on that other SoC when I got the ddr3 memory controller operational and suddenly had access to external RAM instead of just the on-chip SRAM.... I had absolutely no idea what I was gonna do with all that ram, the internal SRAM was already plenty really ;)
Guest98 has joined #beagle
<zmatt> in contrast, now the bootloader used to linux doesn't even manage to fit its fat ass in internal SRAM and as a result has to do two-stage loading
<zmatt> *used to load linux
Guest98 has quit [Client Quit]
Guest98 has joined #beagle
Guest98 has quit [Client Quit]
<Guest76> lol, I see
<Guest76> I was reffered to this nugget
<Guest76> In response to my problem of getting bit in the butt for relying on rpi
<Guest76> I suppose the rpi is super demanding due to it's accessibility
<zmatt> there's also a company that makes a module containing the AM335x + PMIC + DDR3 ram + decoupling caps ... so basically the most critical parts that normally surround the AM335x (and require the most from the pcb design), stuffed together in one package
<zmatt> it's not cheap though
<Guest76> The write of this blog mentioned that one can find pre-made board + schematic designs which I can just send to fab facotories to get produced and installed with bga components?
<Guest76> I don't suppose you have experience with these?
<Guest76> or if you've come across an example of these?
<zmatt> the beaglebone's schematic and pcb design is open
<Guest76> Well that's a big plus over the rpi
<Guest76> here's to hoping I can get this pygame running
brook has quit [Remote host closed the connection]
<zmatt> the company that makes the module I just mentioned, Octavo, also released a variant that embeds an eMMC, which means you need _very_ little around it to boot: https://twitter.com/pdp7/status/1100349116515827712
<zmatt> seems a bit unnecessary to me compared to just adding an external eMMC to your pcb design, but it's kinda funny
<Guest76> oh my lord
<Guest76> lmao that bga solder work
<zmatt> if you think this is crazy, do a google image search on "bga dead bug" ;)
<Guest76> oh god
<Guest76> I was thinking this yeah
<Guest76> lol
<zmatt> oh right I was going to get some sleep
* zmatt zZ
<Guest76> alrighty
<Guest76> thanks for the conversation
nick12310 has joined #beagle
starblue has quit [Ping timeout: 252 seconds]
starblue has joined #beagle
BB-Flash has joined #beagle
<BB-Flash> If a BeagleBone Black Wireless PWR LED blinks twice after applying power (either USB or barrel connector), is it just bricked?
<set_> No.
<set_> brb
<Guest76> So are you guys involved in the beaglebone project or are you more good Samaritans helping out noobs like us?
<set_> Me...I like to help when I can.
<BB-Flash> Some are involved in the BB project, most are noobs like me :-)
<set_> I am a stupendous person!
<set_> I like the ServoCape right now.
<set_> I cannot wait to see what is next...
<BB-Flash> I am more of an 'end user' and have deployed about a 100 probably of these in production around the world, so my view is very narrow to what I do with them and don't have time to go about exploring other things outside of what I do...wish I did have time though as it's a super cool product for sure
<set_> Yep.
<Guest76> I see
<Guest76> nice to meet you all
<set_> What are you doing w/ the BBB or related boards now?
<BB-Flash> I use BBB in an IoT type application, pulling data from sensors of different types and pushing them into a cloud based application
<set_> Nice!
<set_> PRUs?
<BB-Flash> Looks like two of my boards are bricked, they were inside a vehicle powered by 12V supply
<set_> Ut oh.
<set_> 12v to the BBB?
<set_> Not good.
<BB-Flash> I usually use the Power Board which supports up to 30V mounted on top, so no idea why they got fried
<Guest76> I'm working on this but on beagle bone
<set_> Oh! That PowerCape? I have not figured that one out yet.
<set_> Well, sort of.
<set_> I wonder if I can use that PowerCape w/ the ServoCape. You know, instead of DC-DC converters...
<BB-Flash> What do you mean by not figured that out? It's basically a voltage rectifier and takes in higher voltages and provides 5V and 3.3V outputs
<BB-Flash> Yeah the PowerCape is a DC-DC converter
<set_> Right...I am shaky around voltages. I make errors no matter how sure I get.
<set_> I am going to read about it now.
<set_> brb
<BB-Flash> Yeah they are pretty dang reliable, I have used them a lot over the past couple of years, I suspect someone may have exceeded the input voltage or something... the power board does light up though when plugged into a 12V supply on the bench, so all the more confusing.
<set_> Hmm.
<set_> Yep. 30v.
<set_> I am working on a quadruped right now to test things.
<BB-Flash> Something like Spot, the Boston Dynamics Robot?
<set_> Not that awesome.
<set_> Did Boston Dynamics get sold?
<set_> I think they did.
<BB-Flash> :-D) I have been fortunate to lay my hands on those... they are mean engineering machines
<set_> Wozzers.
<BB-Flash> Hyundai
<set_> Aw.
<set_> Big dollar!
<set_> I am small time. I make and that is about it.
<BB-Flash> They have changed hands a few times from Google to Softbank to now Hyundai
<set_> I tried some maker faires in town.
<set_> Oh.
<set_> They made the faire outside for the mechatronics w/ and w/out power. Huh?
<set_> I lost it.
<set_> I planned on bringing the BBBlue w/ arduRover.
<set_> I am glad I did not.
<set_> Anyway, old stories.
<set_> They even stopped the maker shop on my side of town. My town is going downhill and w/ gas only. It is a harsh reality.
<set_> It has been that way for a while (Historically).
<set_> BB-Flash: So, how can you access your BBB?
<set_> UART or via browsers?
<BB-Flash> Sorry don't understand what do you mean by how do I access my BBB. Usually do SSH to the USB port. Onsite, sometimes they are connected to a wireless network with a known IP and I can usually SSH to that by controlling another PC on the same network
<set_> Oh.
<set_> Okay.
<set_> That is what I meant.
<set_> I figured you did some server and sharing to handle remote tasks.
<BB-Flash> There have been occasions where I have made a roughneck type in Linux commands using a terminal in the middle of winter in the middle of nowhere... I usually ask them to update their resume after that and mentioning 'some Linux experience'
<set_> Ha.
<set_> "did he say ./?"
<set_> I am still young in the Linux/Unix environments.
<set_> So, using them is not always so straight forward for me (yet).
<set_> There is a lot to programming and Linux/Unix environments.
<set_> BBBs know.
<Guest76> Is there by any chance an instruction manual on how to install kmsdrm onto beagle debian?
<BB-Flash> Programming in anything is not an easy task especially for production environment, programming as a hobby is fun
<Guest76> I'm seeing some odroid gitlab instructions
<set_> I get so stressed trying to have fun w/ programming. And, you are right, I would only assume. I am not a contractor in that field.
vagrantc has joined #beagle
<set_> Guest76: I am not sure.
<Guest76> im reading through the docs
<Guest76> perhaps better ask tomorrow
<set_> kmsdrm, oh!
<set_> Right. 10:00 is close.
<Guest76> I think I made some good progress for today, don't want to poil the mood
<Guest76> gonna play some fallout 4 on steadeck.
<Guest76> Thanks everyone for the chats and help
<set_> Yep. am335x boards!
BB-Flash has quit [Quit: Client closed]
<set_> That was my chant.
<set_> Good luck w/ gaming and chatting in your future endeavors. Back to the spoiled life I lead. Blaise.
* set_ eight minutes!
Guest76 has quit [Quit: Client closed]
<ds2> progamming is easy... debugging is hard ;)
samnob has quit [Quit: I'm not smart enuf to edit bouncer.conf]
samnob has joined #beagle
akaWolf has quit [Ping timeout: 246 seconds]
<nick12310> Can someone help? I think I messed up my pin configuration somehow, I'm not able to select pins as gpio. This is the error I'm getting: /var/lib/cloud9/common/write_init_pins.sh: line 6: /sys/devices/platform/ocp/ocp:P9_18_pinmux/state: No such file or directory
<nick12310> writing "gpio" to "/sys/devices/platform/ocp/ocp:P9_25_pinmux/state"
<nick12310> (just the first line), seems like the directory just doesn't exist. How can I fix this?
<nick12310> For context, I may have mucked something up in my uEnv.txt, here is a paste of it if someone could take a look https://justpaste.it/65vwq
nick12310 has quit [Quit: Client closed]
AKN has joined #beagle
akaWolf has joined #beagle
akaWolf has quit [Ping timeout: 260 seconds]
akaWolf has joined #beagle
nick12310 has joined #beagle
AKN has quit [Ping timeout: 260 seconds]
AKN has joined #beagle
AKN has quit [Ping timeout: 248 seconds]
otisolsen70 has joined #beagle
otisolsen70 has quit [Remote host closed the connection]
otisolsen70 has joined #beagle
ikarso has joined #beagle
AKN has joined #beagle
akaWolf has quit [Ping timeout: 260 seconds]
indigaz has joined #beagle
nick12310 has quit [Ping timeout: 260 seconds]
akaWolf has joined #beagle
vagrantc has quit [Quit: leaving]
AKN has quit [Read error: Connection reset by peer]
akaWolf has quit [Ping timeout: 248 seconds]
mag has quit [Ping timeout: 248 seconds]
<zmatt> well, I can't give an answer if you don't stick around...
<ketas> maybe he re-comes
rob_w has joined #beagle
mag has joined #beagle
shoragan is now known as Guest3417
Guest3417 has quit [Killed (silver.libera.chat (Nickname regained by services))]
shoragan_ is now known as shoragan
shoragan_ has joined #beagle
samnob has quit [Ping timeout: 260 seconds]
samnob has joined #beagle
akaWolf has joined #beagle
akaWolf has quit [Ping timeout: 260 seconds]
akaWolf has joined #beagle
akaWolf has quit [Ping timeout: 260 seconds]
akaWolf has joined #beagle
Vijay has joined #beagle
<Vijay> Hi
<Vijay> We need 610pcs of BBONE-BLACK-IND-4G.
<Vijay> Can you please advice where to buy?
ft has quit [Quit: leaving]
Vijay has quit [Quit: Client closed]
florian_kc has joined #beagle
Shadyman has quit [Remote host closed the connection]
shoragan_ has quit [Quit: quit]
<zmatt> is google down?
<zmatt> :P
florian_kc is now known as florian
starblue has quit [Ping timeout: 248 seconds]
starblue has joined #beagle
uart0_person has joined #beagle
<uart0_person> Hello
<uart0_person> So i tried to create a share folder with samba and in my windows machine it finds the folder, but it doesn't allow to connect
<zmatt> yeah iirc samba can be fiddly to get working right... which is why I suggested using e.g. sshfs which doesn't require any setup on the beaglebone
<uart0_person> now I will try this
akaWolf has quit [Ping timeout: 260 seconds]
uart0_person has quit [Quit: Client closed]
akaWolf has joined #beagle
brook has joined #beagle
brook has quit [Remote host closed the connection]
samnob has quit [Quit: I'm not smart enuf to edit bouncer.conf]
brook has joined #beagle
samnob has joined #beagle
brook has quit [Remote host closed the connection]
brook has joined #beagle
akaWolf has quit [Ping timeout: 252 seconds]
rob_w has quit [Remote host closed the connection]
akaWolf has joined #beagle
ikarso has quit [Quit: Connection closed for inactivity]
akaWolf has quit [Ping timeout: 248 seconds]
akaWolf has joined #beagle
samnob has quit [Quit: I'm not smart enuf to edit bouncer.conf]
samnob has joined #beagle
samnob has quit [Quit: I'm not smart enuf to edit bouncer.conf]
samnob has joined #beagle
florian has quit [Quit: Ex-Chat]
vagrantc has joined #beagle
uart0_person has joined #beagle
<uart0_person> Hello
<uart0_person> What are some lightweight ide that can be used with a pocketbeagle?
akaWolf has quit [Ping timeout: 248 seconds]
akaWolf has joined #beagle
akaWolf has quit [Ping timeout: 248 seconds]
akaWolf has joined #beagle
uart0_person has quit [Quit: Client closed]
akaWolf has quit [Ping timeout: 252 seconds]
ft has joined #beagle
akaWolf has joined #beagle
uart0_person has joined #beagle
<uart0_person> Hello
akaWolf has quit [Ping timeout: 260 seconds]
akaWolf has joined #beagle
akaWolf has quit [Ping timeout: 260 seconds]
akaWolf has joined #beagle
<uart0_person> I am almost giving up trying to access the pocket from windows and just copy paste the codes into nano
akaWolf has quit [Ping timeout: 260 seconds]
Posterdati has quit [Ping timeout: 248 seconds]
ft has quit [Quit: leaving]
akaWolf has joined #beagle
ft has joined #beagle
akaWolf has quit [Ping timeout: 248 seconds]
akaWolf has joined #beagle
Posterdati has joined #beagle
otisolsen70 has quit [Quit: Leaving]
uart0_person has quit [Quit: Client closed]
akaWolf has quit [Ping timeout: 260 seconds]
<zmatt> you've tried sshfs? or vscode with ssh remote development?
<zmatt> like, "copy paste" is obviously silly, you can just use scp or rsync to transfer files if need be, but there are user-friendlier solutions
akaWolf has joined #beagle
akaWolf has quit [Ping timeout: 260 seconds]
akaWolf has joined #beagle
akaWolf has quit [Ping timeout: 260 seconds]
akaWolf has joined #beagle
vvn has quit [Quit: WeeChat 3.7]
akaWolf has quit [Ping timeout: 260 seconds]
akaWolf has joined #beagle
brook_ has joined #beagle
brook has quit [Ping timeout: 252 seconds]
brook_ has quit [Ping timeout: 248 seconds]