On Thu, Mar 3, 2016 at 2:40 PM, Delbert Martin <[email protected]> wrote: > using below system image > https://rcn-ee.com/rootfs/bb.org/testing/2016-02-26/console/BBB-eMMC-flasher-debian-8.3-console-armhf-2016-02-26-2gb.img.xz > > I'm going out on a limb here, but I can't find dtc or any of the capemgr > stuff in this image. > > is this supposed to be missing on this image? or did I miss some readme file > somewhere that says all that stuff is not included. > I really want to play around with the pru stuff, but the lxqt images don't > have enough free space to even unpack the ti-pru stuff, because I only have > 2G of eMMC > > plus /lib/firmware is missing, which might be part of the problem with the > pru refusing to load firmware. > > pruss-rproc 4a300000.pruss: creating platform devices for PRU cores > [ 14.482866] remoteproc1: 4a334000.pru0 is available > [ 14.482895] remoteproc1: Note: remoteproc is still under development and > considered experimental. > [ 14.482906] remoteproc1: THE BINARY FORMAT IS NOT YET FINALIZED, and > backward compatibility isn't yet guaranteed. > [ 14.484361] remoteproc1: Direct firmware load for am335x-pru0-fw failed > with error -2 > [ 14.484389] remoteproc1: failed to load am335x-pru0-fw > [ 14.489762] pru-rproc 4a334000.pru0: booting the PRU core manually > [ 14.489778] remoteproc1: powering up 4a334000.pru0 > [ 14.489823] remoteproc1: Direct firmware load for am335x-pru0-fw failed > with error -2 > [ 14.489838] remoteproc1: request_firmware failed: -2 > [ 14.496819] pru-rproc 4a334000.pru0: rproc_boot failed > [ 14.502270] remoteproc1: releasing 4a334000.pru0 > [ 14.502485] pru-rproc: probe of 4a334000.pru0 failed with error -2 > [ 14.504894] remoteproc1: 4a338000.pru1 is available > [ 14.504919] remoteproc1: Note: remoteproc is still under development and > considered experimental. > [ 14.504930] remoteproc1: THE BINARY FORMAT IS NOT YET FINALIZED, and > backward compatibility isn't yet guaranteed. > [ 14.505163] remoteproc1: Direct firmware load for am335x-pru1-fw failed > with error -2 > [ 14.505184] remoteproc1: failed to load am335x-pru1-fw > [ 14.510514] pru-rproc 4a338000.pru1: booting the PRU core manually > [ 14.510531] remoteproc1: powering up 4a338000.pru1 > [ 14.510585] remoteproc1: Direct firmware load for am335x-pru1-fw failed > with error -2 > [ 14.510600] remoteproc1: request_firmware failed: -2 > [ 14.517995] pru-rproc 4a338000.pru1: rproc_boot failed > [ 14.524519] remoteproc1: releasing 4a338000.pru1 > [ 14.524736] pru-rproc: probe of 4a338000.pru1 failed with error -2
am335x-pru0-fw & am335x-pru1-fw Are for "YOU" to design/build/etc... > > although now looking at dmesg: > bone_capemgr bone_capemgr: Baseboard: 'A335BNLT,00A6,4613BBBK0054' > [ 3.876067] bone_capemgr bone_capemgr: > compatible-baseboard=ti,beaglebone-black - #slots=4 > [ 3.933156] bone_capemgr bone_capemgr: slot #0: No cape found > [ 3.993135] bone_capemgr bone_capemgr: slot #1: No cape found > [ 4.053153] bone_capemgr bone_capemgr: slot #2: No cape found > [ 4.113135] bone_capemgr bone_capemgr: slot #3: No cape found > [ 4.119065] bone_capemgr bone_capemgr: initialized OK. > > looks like capemgr is in there somewhere? > > is there new documentation I haven't seen relating to how capemgr might work > now. is the device tree stuff I've read about still valid? https://github.com/beagleboard/bb.org-overlays/ > or should I just be using a different image? iot/lxqt image has all the *.dtbo overlays installed in /lib/firmware/ Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
