Hi John, On Sun, Mar 3, 2019 at 6:49 AM <[email protected]> wrote: > > Hi Robert, > > The problem is the cape was built and tested with the older SLOTs based > Debian. Most of the links and books refer to this. Now we no longer have > them. So I'm trying to write myself a new user guide so that in 3 months > when I've forgotten everything I don't have waste hours sifting through out > of date information all over again. > > 1. From the command line how do I show which capes are detected since I can't > cat $SLOTS anymore?
1a: cat /proc/cmdline 1b: look at serial boot log > 2. This no longer works: cat /sys/bus/i2c/devices/1-0057/eeprom | hexdump -C > a) How do I find my cape eeprom > b) How do I dump my cape eeprom? This looks like an i2c error, i'll look at this week.. but try, resetting the pinmux.. debian@test-bbb-2:~$ config-pin P9_19 i2c debian@test-bbb-2:~$ config-pin P9_20 i2c > 3. Is there something more up to date than this for programming a new cape > eeprom or is this still valid. > https://github.com/jbdatko/eeprom_tutorial/blob/master/eeprom.md > if it's not valid is there a document that is? The original eeprom document has not changed since the 3.8.x era... > 4. There were questions in the previous postings about error messages. But not important enough to restate.. > 5. If I write a new dts do I have to > a) make src/arm/BB-W1-P8.11-00A0.dtbo > b) sudo make install > c) reboot every time to test this? Yeap, that's the minimal needed.. 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYiyfjzewR2NmwS89SaByU5q7eHT9LC9r8pzMkGqeZtmKw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
