Alex_BB has joined #beagle
<Alex_BB> Thank you for your help yesterday.  Using a new image from https://forum.beagleboard.org/t/debian-11-x-bullseye-monthly-snapshots-arm64/32318 and some kludgy symlinking I was able to get imgdnn_test to run.  I'll file a bugreport on pvrsrvctl shortly
zmatt has quit [Ping timeout: 256 seconds]
zmatt has joined #beagle
Alex_BB has quit [Ping timeout: 245 seconds]
Shadyman has joined #beagle
starblue has quit [Ping timeout: 268 seconds]
starblue has joined #beagle
zmatt has quit [Ping timeout: 246 seconds]
zmatt has joined #beagle
DrPatater has quit [Quit: Explodes into a thousand pieces]
DrPatater has joined #beagle
otisolsen70 has joined #beagle
ft has quit [Quit: leaving]
otisolsen70 has quit [Read error: Connection reset by peer]
Shadyman has quit [Quit: Leaving.]
weevoy has quit [Ping timeout: 240 seconds]
florian has joined #beagle
starblue has quit [Ping timeout: 256 seconds]
starblue has joined #beagle
buckket has quit [Quit: buckket]
buckket has joined #beagle
weevoy has joined #beagle
mattb0ne has joined #beagle
<mattb0ne> yeah I am trying to implement a filter on the PRU now
jfsimon1981_c has joined #beagle
jfsimon1981 has quit [Ping timeout: 256 seconds]
jfsimon1981 has joined #beagle
jfsimon1981 has quit [Remote host closed the connection]
Stat_headcrabed has joined #beagle
xet7 has joined #beagle
xet7 has quit [Ping timeout: 240 seconds]
xet7 has joined #beagle
vagrantc has joined #beagle
Stat_headcrabed has quit [Quit: Stat_headcrabed]
jfsimon1981_c has quit [Remote host closed the connection]
jfsimon1981_c has joined #beagle
Stat_headcrabed has joined #beagle
florian has quit [Quit: Ex-Chat]
xet7 has quit [Quit: Leaving]
ft has joined #beagle
Stat_headcrabed has quit [Quit: Stat_headcrabed]
xet7 has joined #beagle
xet7 has quit [Remote host closed the connection]
mattb0ne has quit [Ping timeout: 240 seconds]
jfsimon1981_c has quit [Remote host closed the connection]
jfsimon1981 has joined #beagle
Guest34 has joined #beagle
Guest34 has quit [Client Quit]
Cocus has joined #beagle
<Cocus> hi!
<Cocus> I'm trying to build a yocto image for the old beagleboard (omap3350, with MACHINE="beagleboard" set on my local.conf). I'm using dunfell for yocto's poky and meta-oe branches, but I'm also using meta-ti (which in turn requires meta-arm and meta-arm-toolchain). I've created a wic image with the u-boot, uImage, MLO and the dtbs, which I flashed on my
<Cocus> sd card. the uboot seems to load fine, although there's no good script to boot the kernel image. I've used fatload, like "fatload mmc 0:1 0x80300000 uImage", which it sorta seems to load, but the kernel never starts. I've tried with zImage + dtb (fatload mmc 0 0x82000000 zImage and fatload mmc 0 0x88000000 omap3-beagle.dtb, and then bootz
<Cocus> 0x82000000  - 0x88000000), but same thing
<Cocus> what could I be doing wrong? I'm suspecting the defconfig of the kernel is not correct for this platform, and its using the beaglebone am335x instead
<Cocus> I've used dunfell just because it's the "most recent one" that still had the "beagleboard.conf" machine; it uses the linux 5.10 staging from meta-ti, maybe it's too new?
<Cocus> btw, I forgot to add logs, but they're pretty boring. for the uImage, I get
<Cocus> BeagleBoard # fatload mmc 0:1 0x80300000 uImage
<Cocus> 5329472 bytes read in 475 ms (10.7 MiB/s)
<Cocus> BeagleBoard # bootm 0x80300000
<Cocus> ## Booting kernel from Legacy Image at 80300000 ...
<Cocus>    Image Name: Linux-5.10.168-g991c5ce91e
<Cocus>    Image Type: ARM Linux Kernel Image (uncompressed)
<Cocus>    Data Size: 5329408 Bytes = 5.1 MiB
<Cocus>    Load Address: 80008000
<Cocus>    Entry Point: 80008000
<Cocus>    Verifying Checksum ... OK
<Cocus>    Loading Kernel Image
<Cocus> Starting kernel ...
<Cocus> and for the zImage:
<Cocus> BeagleBoard # fatload mmc 0 0x82000000 zImage
<Cocus> 5329408 bytes read in 475 ms (10.7 MiB/s)
<Cocus> BeagleBoard # fatload mmc 0 0x88000000 omap3-beagle.dtb
<Cocus> 97916 bytes read in 13 ms (7.2 MiB/s)
mattb0ne has joined #beagle
Cocus has quit [Ping timeout: 245 seconds]
mattb0ne has quit [Ping timeout: 240 seconds]
ikarso has joined #beagle
zjason` has joined #beagle
zjason has quit [Ping timeout: 240 seconds]
mattb0ne has joined #beagle
<mattb0ne> I do have that spare core but I think I may use that to filter in an perfect world
<mattb0ne> try and have a ring buffer with 1 pru doing the reading of the sensor and one that filters the signal
<mattb0ne> for right now I will let the digitizer filter
<mattb0ne> until everythign else works
mattb0ne has quit [Ping timeout: 240 seconds]
ikarso has quit [Quit: Connection closed for inactivity]
<zmatt> mattb0ne: that sounds like a complete waste of a pru core
<zmatt> the appropriate time to execute the filter is right after receiving the next value from the load cell
<zmatt> and considering how low the sample rate is, it'll take basically 0% cpu load
<set_> )
<set_> Dang it.
<set_> Smiles all around or SAA. Anyway, I jumped in to jump out. BBL!
PhotoJim is now known as PJimAFK
mattb0ne has joined #beagle
Cocus has joined #beagle
<set_> I am back!
<set_> Yea!
<set_> Darn disk failures will put a needle in anyone's rumpus. Sheesh.
<set_> So, what is going on w/ the BBAI-64?
<set_> Anything I should know?
<set_> Like, super portals to other dimensions or engineering marvels made accessible?
<set_> is anyone using the i3c interfaces/peripherals on the BBAI-64 yet?
<set_> and what exactly is ' wake up domain serial port ' ?
<set_> There are two (three pin) headers on the board w/ TTL to USB usages. But one, says ' wake up domain serial port '.
<set_> Like when the board boots before the u-boot is reached or in b/t u-boot and the kernel?
<static_rocket> @set_:libera.chat: serial port connected directly to the mcu domain devices >> https://software-dl.ti.com/tisci/esd/latest/5_soc_doc/j721e/soc_devgrps.html#enumeration-of-device-group-ids
<set_> Anyway, I plugged in and tried to get output/feedback from the ' wake up domain serial port '.
<set_> Aw.
<set_> Thank you.
<static_rocket> information on that is scattered though. bits and pieces of potential use cases other than early device boot are sprinkled around the various ti docs
<set_> Nice. I will look again and again. So, has anyone or you, for instance, been able to attach a TTL to USB adapter and see output w/ this serial yet?
<set_> I mean...someone somewhere. I am sure but...
<static_rocket> I haven't personally tried, not sure about the community
<set_> Would using the...okay.
<set_> No issue.
<set_> I am still finding reasons why I should plug in the XDS110 to the six pin debug header...
<set_> I broke down and got the adapter from that Plug of Nails company. So, it is just a matter of time.
<set_> Oh!
<set_> So, for fast boot sequences, one would set up the AI-64 in a particular manner and then use the the 'wake up domain serial' to get output.
<set_> I see i2c and uart channels are available in this domain.
<set_> So, it seems there is a firewall that cannot be used directly w/ r/w but using this serial domain needs a firewall.
<set_> Hey? What is implied here when people say "System Firmware"?
<set_> Like that link leads me to a million hits of back and forth readings. But, firewall sticks out and so does System Firmware.
<set_> Aw!
* set_ says System Firmware is a generic term for a lot of different mechanisms w/in TI's infrastructure of "things" like TIFS, RM, and PM.
<mattb0ne> what does this mean
<mattb0ne> "The factory setting of control signal voltage is 24V, must need to set 5V/24V
<mattb0ne> rotating switch if it is 5V"
<mattb0ne> what the hell is a rotating switch
<static_rocket> @mattb0ne:libera.chat: I assume you are talking about the CL86T - Closed Loop Stepper Driver
<static_rocket> There's a rotating switch, or rotary switch, that selects one of a few predetermined peak current selections. They have a breakdown in the manual.