00:47 <set_> I am back!

00:48 <set_> There is so much going on, I have not had time to make things up! Anyway, I am goin' back to teknic motors w/ their SDK to try again (some day but no today)...

00:48 <set_> I hope everyone is doin' well.

00:49 <set_> I am...I am doin well. I can breathe and walk thankfully.

00:49 <set_> Anyway, back to the BBB, i.e. and other related hardware!

00:50 <set_> Just an update here. The business that employs me got hit by lightning. Ha.

00:50 <set_> Server down!

00:50 <set_> Anyway, now there are dangling wires everywhere when I mow.

00:50 <set_> Ha. double ha.

00:50 <set_> Wish me luck!

00:51 <set_> Speaking of the beagleboard.org stuff, has anyone used the Tag Connect w/ a BBAI-64 yet?

00:52 <set_> I grabbed one and personally have not used it yet. I need to learn CCS and the wiring for the debugger.

00:52 <set_> Then, maybe I can finally be proud of what @zmatt teaches me! Just kiddin'. I already am. Ha.

00:56 <set_> Not mattb0ne. He done left?

05:27 <Guest60> [ 0.000000] TI gptimer clocksource: always-on /ocp/interconnect@44c00000/segment@200000/target-module@31000

05:27 <Guest60> [ 0.000023] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 89478484971ns

05:27 <Guest60> [ 0.008116] clocksource: dmtimer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns

05:27 <Guest60> [ 0.018464] TI gptimer clockevent: 24000000 Hz at /ocp/interconnect@48000000/segment@0/target-module@40000

05:28 <Guest60> [ 0.031315] Console: colour dummy device 80x30

05:28 <Guest60> [ 0.035925] printk: console [tty0] enabled

05:28 <Guest60> [ 0.040280] printk: bootconsole [earlycon0] disabled

05:28 <Guest60> with further debugging found that; kernel is rebooting while "calibrating delay loop..." inside this function;

05:28 <Guest60> calibrate_delay_converge()->calibrate_delay(void)->main()

05:28 <Guest60> any help on the same is appreciable.

14:31 <NishanthMenon> set_: https://nmenon.github.io/k3ocd/#j721e-beaglebone-ai64 (replying to your question on tag connect with bb-ai64)

14:56 <zmatt> of the various low-cost jtag debuggers in my collection I still like the xds100v2 the most by far, in no small part due to its cpld which not just acts as a level shifter but also keeps all target I/O high-impedance until both xds100v2 and the target are powered and the target-power-loss flag has been cleared by software

14:57 <zmatt> (thanks to which I can safely hotplug it without causing a glitch on the target reset line)

15:54 <set_> NishanthMenon: Thank you.

15:54 <set_> I need to check my model of debugger.

15:54 <set_> I am going to look at k3ocd too.

15:56 <set_> I see I need additional cables. Dang it. I thought I had it covered. I may use loose wires instead of the connector...

15:56 <set_> I will test soon at some point.

16:01 <set_> @zmatt: I got the xds110.

16:01 <set_> It handles the BBB and k3.

16:01 <set_> I think this is why I purchased this one, i.e. both are accepted.

16:02 <set_> I am still reading and following along the long process of learning. So...

16:07 <set_> Hmm.

16:08 <set_> I may be wrong. In CCS, it shows the j721e being accepted by the probe but I just went through some more docs.

16:08 <set_> They do no have it listed. Omap?

16:09 <set_> or is it davinci?

16:11 <set_> J721E/DRA829/TDA4VM - Cortex A72 Embedded Processor ?

16:11 <set_> See, I go to CCS and it is listed, i.e. not as BBAI-64 but as the target processor.

16:13 <set_> The docs. help w/ the BBB but not the j721e for whatever reason or maybe I have not made it that far in the docs.

16:13 <set_> Off to read!

16:24 <set_> Nothing most likely...

16:25 <set_> I picked TI's debugger for no reason (to test it basically).

19:42 <Guest53> Hello everyone. I'm extremely new to the BeagleBone(s), I just got an BeagleBone AI-64 and it's my first time experimenting with such hardware. I just have a quick question if that is ok? Thanks in advance!

19:59 <Guest53> I'm booting image from SD card, I managed to set it up - my issue is that after I've installed everything BeagleBone is working fine (and fast) but after I start VS Code the speed drops significantly (to the point that it takes a minute just to register a mouse click). I understand that it might be a bit too much since environment is being ran

19:59 <Guest53> inside docker container and I'm left with only about 800MB free space (I only had 32GB SD card at hand). I tried searching for a reason why is it slowing down but I didn't find an answer to it (sorry if I didn't look long enough) - does anyone have any ideas? Is it the fact that I'm only left with 800MB, or do I need to configure something? Is

19:59 <Guest53> docker container the issue here, should I try running the project without docker? Like I said I'm brand new to this so sorry in advance if my guesses are far off or if I'm missing something obvious, any help is much appreciated. Thanks!

20:10 <set_> Guest53: I think bb-code-server comes preinstalled.

20:10 <set_> If not, apt install bb-code-server. It is a light weight VS Code versus the entire versioning.

20:13 <Guest53> Thanks! And Docker container ran inside the bb-code-server shouldn't (if using "plain" VS Code was the issue here) cause additional problems?

20:14 <set_> I am not sure exactly.

20:15 <set_> Docker Containers sometimes work well.

20:15 <set_> I used many docker containers before today. But...just not on the BBAI-64. I ran donkeycar on the AI-64, though. They have a venv instead of an entire container.

20:16 <set_> I think something as large as VS Code would contain many programs not exactly suited for aarch64 arch.

20:17 <set_> Guest53: It is hard to tell. In a pastebin.com paste, please list your commands.

20:17 <set_> This way, maybe someone can replay what was happening on your end w/ one of their boards.

20:18 <set_> For instance, sudo apt install _____.

20:18 <set_> Or docker build ______.

20:19 <set_> Guest53: about bb-code-server. There is a few people maybe working on this idea.

20:20 <set_> Anyway, you can go to the git.beagleboard.org and find more relevant ideas or you can pitch in and make some pull requests too!

20:22 <set_> brb

20:22 <Guest53> Thank you so much! I will try using the bb-code-server first and if the problem persists I will list the commands in a pastebin. I would try it now but I disconnected BB since I have to head out of the office in a couple of minutes. I will save your responses and start from there.

20:23 <Guest53> Thanks for the git idea, I didn't even think of that - also I'm pretty sure I'm not gonna have anything to contribute for a while:D  . Thanks for all these tips!

20:28 <set_> no issue.

20:28 <set_> I try to help.

20:30 <Guest53> hopefully tomorrow I'll be back with a news that your idea solved the issue - either way, thanks once again for your time and effort. Good night and happy coding! :)

21:14 <set_> Code it!

22:50 <cappie> hi, I'm having an issue reading from the ADC on a Beaglebone black, `cat /sys/bus/iio/devices/iio\:device0/in_voltage0_raw` just hangs and creates a process that can't be killed outside of resetting the board.  I was on kernel 4.19.94-r73, but tried updating to 5.10.168-bone71 but I still have the same issue.  Anyone know what could be going on?

22:50 <cappie> It is a new board with Debian Buster IoT Image 2020-04-06

23:07 <ball> Was the PocketBeagle discontinued?