**** BEGIN LOGGING AT Thu Jul 11 03:01:20 2019 **** BEGIN LOGGING AT Thu Jul 11 03:40:59 2019 Jul 11 03:41:11 zmatt that circuit is a bit different now that I look at it. Jul 11 05:03:27 GenTooMan: :D Jul 11 05:05:45 GenTooMan: weird isn't it? you can also find the schematic here: https://archive.org/stream/agc_handbook_jp2#page/n94/mode/1up Jul 11 08:02:28 I'm looking for a mini-pci adapter that can do a simultaneous wifi AP and client like the beaglebone wireless. Any ideas what I should look for ? Dual band useful but not essential Jul 11 08:03:56 Can anyone shed some light on the use of remoteproc to access PRU? Have been reading all documentation, but when writing 'start' to remoteprocX/state I get an error: 'file not found' Jul 11 08:50:13 pru-noob: I don't really know anything about remoteproc, I use uio-pruss Jul 11 08:50:43 how exactly are you doing the write, and where do you get that error? Jul 11 08:59:18 you mean something like: "-bash: echo: write error: No such file or directory" Jul 11 09:00:35 that means it can't find the firmware. the firmware filename is configured via the "firmware" attribute, and the firmware should be located in /lib/firmware/ Jul 11 09:02:09 "-bash: echo: write error: No such file or directory" is exactly what I'm getting Jul 11 09:02:48 Was following a tutorial where the firmware is 'loaded' by echo'ing the firmware name to /sys/class/remoteprocX/firmware Jul 11 09:03:00 But probably the firmware file is not located in /lib/firmware Jul 11 09:03:09 I will check - thanks for the pointer! Jul 11 09:05:25 so it literally just means what it says... "no such file" ;) Jul 11 09:06:10 Yes, that seems to fix it - I was assuming the issue was with the 'state' file - not the firmware file Jul 11 09:06:38 Thanks for the help - up to blinking an LED :) Jul 11 09:10:44 man, remoteproc doesn't have much of an interface does it Jul 11 09:12:19 a few more things in debugfs, but still not much Jul 11 09:12:48 I see a virtio device showed up once I started the example firmware, but I don't see any way to interact with it Jul 11 09:13:01 I think I'll just stick to uio ;) Jul 11 09:14:54 (e.g. the pru examples in my https://github.com/mvduin/py-uio include stuff like inspecting and modifying pru registers, signalling the host via interrupts, mapping shared memory, etc) Jul 11 12:33:48 zmatt the schematic for the AGC volital memory makes sense suddenly, what they are working with the the magnetic bias from the core. So if it's bias one way one transistor turns on if it's bias the other the other transistor turns on. they used NPN likely because PNP were difficult to get functional. The mark on the coils off the core gives it away. The diode might be for addressing and the common line for sensing. There is a Jul 11 12:33:48 common line for groups of 4 cores it looks like. **** ENDING LOGGING AT Fri Jul 12 02:59:57 2019