<uart0_person>
that said I needed to already have a static ip
<set_>
No.
<uart0_person>
so edit the interfaces like I said above
<uart0_person>
and caused this mess
<set_>
What are you trying to do?
<set_>
uart0_person: There are some forums for people called forum.beagleboard.org .
<uart0_person>
With raspberry pi, I used samba so I could access the pi folders from my windows machine. With this I could open my code files with an ide
<set_>
They have people there, well and here too, that do things w/ the am335x and Linux.
<set_>
oh!
<uart0_person>
basically, I want to remotely code using the ides inside my windows machine
<uart0_person>
but I don't know how to do anything without guides
<uart0_person>
and the guides I find assume I connecting via wifi to the board
<set_>
sudo apt install bb-code-server
<set_>
Oh.
<set_>
I got it now. Do you have the Ethernet attached yet?
<set_>
I think it is five pins from the Pocket Beagle.
<uart0_person>
do I need ethernet or can I use the usb connection?
<uart0_person>
when seeing the connections inside my windows machine, the pocket connection is listed as ethernet 2
<set_>
Well...
<set_>
Hmm.
<set_>
I have not used the Pocket Beagle before today. I do not have one to test.
<zmatt>
"the remote thing" (neither sshfs nor vscode remote development via ssh) doesn't require any sort of meddling with networking nor any configuration on the beaglebone whatsoever
<zmatt>
since you can already ssh into the beaglebone and that's all it needs
<uart0_person>
I tried adding the same ip I use for ssh into vs code remote plugin
<uart0_person>
Could not establish connection to "192.168.7.2"
<uart0_person>
its the vs code output when I try
<zmatt>
but ssh from the commandline (cmd.exe or powershell) does work?
<zmatt>
(i.e. what step 1 requests you to verify)
<uart0_person>
I use bitvise for ssh, but yeah, using that same ip
<zmatt>
I didn't ask whether ssh using some other software worked
<uart0_person>
oh sorry
<uart0_person>
one moment
akaWolf has quit [Ping timeout: 268 seconds]
<zmatt>
I asked whether using the ssh command invoked from the commandline worked, since that's what vscode requires (as it does the same thing behind the scenes)
<zmatt>
and it's what vscode's guide explicitly asked you to verify
akaWolf has joined #beagle
<uart0_person>
i thought if I could ssh from the software, it meant it worked
<uart0_person>
I need to add a key to known hosts to make it work
akaWolf has quit [Ping timeout: 260 seconds]
<zmatt>
it'll offer to add a key to known hosts if it's missing
<uart0_person>
I did ssh debian@192.168.7.2 and give me warnings saying the key was changed and needed to add the key, but it didn't me the option to add
<zmatt>
if there's a conflicting entry in known hosts then you need to *remove* that entry, not add one
akaWolf has joined #beagle
<zmatt>
recent versions of ssh actually give you the command to remove the conflicting entry, but I guess windows still ships an older versions
<uart0_person>
ok, deleted and now added the ip
<uart0_person>
now I can ssh with powershell
<uart0_person>
ok, it seems i can ssh with vscode now
uart0_person has quit [Quit: Client closed]
<zmatt>
turns out following step 1 of the instructions in the guide actually helps :P
uart0_person has joined #beagle
<uart0_person>
now wait for the setup to finish
brook has quit [Remote host closed the connection]
<uart0_person>
ok, now I can ssh into pocketbeagle with vs code
<uart0_person>
finally
<uart0_person>
just one last question
<uart0_person>
in my pocketbeagle I downloaded the API dronekit
<uart0_person>
is there a way with vs code I can autocomplete the code?
<zmatt>
probably? I've never used vscode myself but I know autocompletion is definitely a feature, though I don't know what things it can autocomplete exactly (but anything not supported out of the box probably has some extension/plugin out there that will)
<uart0_person>
i think the name is IntelliSense
otisolsen70 has quit [Quit: Leaving]
akaWolf has quit [Ping timeout: 260 seconds]
uart0_person has quit [Quit: Client closed]
akaWolf has joined #beagle
brook has joined #beagle
ikarso has quit [Quit: Connection closed for inactivity]
akaWolf has quit [Read error: Connection reset by peer]
akaWolf has joined #beagle
alan_o has quit [Ping timeout: 246 seconds]
brook_ has joined #beagle
brook_ has quit [Read error: Connection reset by peer]
brook_ has joined #beagle
brook has quit [Ping timeout: 255 seconds]
brook_ has quit [Remote host closed the connection]
brook has joined #beagle
alan_o has joined #beagle
nick12310 has joined #beagle
<nick12310>
Hello, I'm having some trouble with PWM accuracy. I'm trying to use it to get a 12.0 MHz clock signal, but it varies between 12.5MHz and 11.1MHz on my oscilloscope, the difference is me changing period from 79 ns to 80 ns. 79 ns is a 12.5 MHz and 80 ns is 11.1 MHz. Why the huge difference at this step? Is the PWM channel just not accurate enough
<nick12310>
for this purpose
vagrantc has joined #beagle
<zmatt>
there are three types of peripherals on the BBB that can generate a PWM signal: eHRPWM and eCAP devices run off a 100 MHz clock hence can only vary the period in 10ns steps, the Timer peripherals run on a 24 MHz clock hence these can produce a 12 MHz clock
<zmatt>
for some reason the timer pwm outputs aren't enabled by default, but there are overlays to enable them (/lib/firmware/BB-PWM-TIMER-P8.*)
<nick12310>
Ah, thanks that makes a lot of sense.
<nick12310>
How do I config timer pins once I have the overlay?
<zmatt>
right, /etc/udev/rules.d/81-pwm-noroot.rules is missing rules for creating symlinks for these in /dev/pwm/ ... hold on
<zmatt>
(note: the timer pwm outputs also have alternative mux options on some P9 pins, if you want to use one of those you'd need to make a custom overlay for that)
akaWolf has joined #beagle
nick12310 has joined #beagle
<nick12310>
so to apply, do I just edit my pwm-noroot.rules file?
<zmatt>
enable the overlay (to create the pwm devices) and edit the udev rules rule (to create symlinks in /dev/pwm/)
<zmatt>
the latter is of course just for convenience of being able to easily locate the pwm outputs
akaWolf has quit [Ping timeout: 252 seconds]
florian has quit [Quit: Ex-Chat]
<nick12310>
Still having trouble getting timer to show up in ls -l /dev/pwm/. I edited the rule adding all four timers and added uboot_overlay_addr0=/lib/firmware/BB-PWM-TIMER-P8.9 to my uEnv.txt file, for timer5
<zmatt>
you mean uboot_overlay_addr0=/lib/firmware/BB-PWM-TIMER-P8.09.dtbo ?
xet7 has quit [Remote host closed the connection]
xet7 has joined #beagle
<nick12310>
Ah. That might be it
<zmatt>
configuring the path of a file that actually exists may help
ft has joined #beagle
<nick12310>
Thank you, it's starting to work. Though now when I write to the pwm, writing period as 83 and duty as 42 seems to be giving me 686 Hz, not 12MHz
<zmatt>
wut
<zmatt>
can you check: grep timer5 /sys/kernel/debug/clk/clk_summary
<zmatt>
... it sure seems to claim it ought to be producing a 12 MHz clock?
<zmatt>
a 12 MHz pwm output I mean
akaWolf has joined #beagle
nick12310 has quit [Quit: Client closed]
nick12310 has joined #beagle
<zmatt>
and the timer5 clock seems to be 24 MHz indeed... if I configure a period of 2 seconds and then monitor the 'timer 5 counter' value (using e.g. watch -n 0.1 sudo ./check-timers ) then the counter indeed appears to wrap every 2 seconds
<nick12310>
Yeah. I really don't know at this point, could it be a hardware issue somehow?
<zmatt>
(interestingly if I try to configure a 3 second period the math in the kernel driver seems to blow up and it programs a 51.5 second period instead, lol)
<zmatt>
nick12310: I don't have an easy way to verify the output (I could do that tomorrow at work), but as far as I can tell the timer is working correctly and at the correct frequency
<nick12310>
Yea, very weird. Anyways thanks for taking a look
<nick12310>
Is it possible to do this with a pru pin? It seems like the timer is giving me enough trouble lol
<zmatt>
that would be much much harder
<zmatt>
are you sure your measurement is right?
<zmatt>
(and you measured the right pin? :P )
akaWolf has quit [Ping timeout: 260 seconds]
<nick12310>
Lol nvm yea... I never zoomed in all the way. There is a 680 Hz square wave for sure. After I actually zoom in a 12 MHz square wave shows up as well.