[beagleboard] multiple PWM ..
Regarding previous post (Multiple PWM), I'm running Debian 9 -- Linux arm 4.9.61-bone8 thx -- 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 beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/cdf95ae1-ccf6-4854-a53f-1be44d034913%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Problem with multiple PWM overlays
Hello, I'm trying to use 3 PWM channels for RGB Led control -- I can install one overlay successfully & drive a (single color) LED changing the period & duty cycle. *root@arm:~# sudo echo BB-PWM0 > /sys/devices/platform/bone_capemgr/slots [ 162.833955] bone_capemgr bone_capemgr: part_number 'BB-PWM0', version 'N/A'[ 162.841500] bone_capemgr bone_capemgr: slot #4: override[ 162.847210] bone_capemgr bone_capemgr: Using override eeprom data at slot 4[ 162.854545] bone_capemgr bone_capemgr: slot #4: 'Override Board Name,00A0,Override Manuf,BB-PWM0'[ 162.897244] bone_capemgr bone_capemgr: slot #4: dtbo 'BB-PWM0-00A0.dtbo' loaded; overlay id #0root@arm:~# * I next try to install another PWM overlay with the following results --- r *oot@arm:~# sudo echo BB-PWM1 > /sys/devices/platform/bone_capemgr/slots [ 424.900238] bone_capemgr bone_capemgr: part_number 'BB-PWM1', version 'N/A'[ 424.907757] bone_capemgr bone_capemgr: slot #5: override[ 424.913369] bone_capemgr bone_capemgr: Using override eeprom data at slot 5[ 424.920787] bone_capemgr bone_capemgr: slot #5: 'Override Board Name,00A0,Override Manuf,BB-PWM1'[ 424.954871] OF: changeset: add_property failed @/__symbols__/pinctrl_spec[ 424.962243] OF: Error applying changeset (-17)[ 424.971503] bone_capemgr bone_capemgr: slot #5: Failed to create overlayecho: write error: File existsroot@arm:~# * Shouldn't the configuration be separate between the overlays so they can operate independently? I get the same result with any combination. Thanks for the help -- rich.. -- 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 beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/7935123f-6457-4acd-b8f4-1724526e8234%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: initrd.img not detected
Hi William,
Thanks a lot for the reply -- very helpful.
It does bring up another question -- are there environmental variables set
up (by default) by U-boot which may (or may not) be over written by
uEnv.txt stage 1 or 2?
regards, Rich..
On Friday, July 1, 2016 at 8:01:09 PM UTC-4, richa...@yahoo.com wrote:
>
> Hi,
>
> Using Robert Nelson's eewiki site, I'm running 4.4.11-bone10.1 (single
> parition) on my BBB via SD; *initrd.img-4.4.11-bone10.1* in built and in
> /boot. I don't see evidence that the initrd.img was detected/mounted. A
> previous version built earlier this year (4.4.1-bone5) (two partitions)
> shows ...
>
>
>
> *[3.484281] Unpacking
> initramfs...
>
> [3.821276] Freeing initrd memory: 5196K (c808 -
> c8593000)
> *
> I sprinkled some debug statements in the kernel ... at line #625 in
> init/main.c, the following lines indicates *initrd_start* and
> *initrd_below_start_ok* as 0.
>
> locking_selftest();
>* pr_notice("RSF!! initrd_start:%d initrd_below_start_ok:%d\n",
> initrd_start, initrd_below_start_ok);*
>
>
> /uEnv.txt has the line to install the file ..
> *loadxrd=load mmc 0:1 **${rdaddr} /boot/initrd.img-${uname_r}; setenv
> rdsize ${filesize}*
> Diagnostics shows this file being read into memory
>
> Should these values be > 0? Am I missing a command line options? Is there
> a way to track progress of the mount in kernel via pr_debug()?
>
>
> thx for the help ..
>
>
--
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/530d9314-9bed-4efd-927b-95218c62d4fc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: initrd.img not detected
By adding this argument pair to 'bootargs', the kernel 'found' the
initramfs file..
* initrd=${rdaddr},0x${rdsize}*
where *rdaddr* is 0x8808 and *rdsize* is the size of the initramfs
file. I don't know why it had to be explicitly set where it was not
necessary before.
-
Also I found that this line
*loadxfdt=load mmc **0:1 **${fdtaddr}
/boot/dtbs/${uname_r}/${fdtfile}*
needed to be changed to:
*loadxfdt=load mmc 0:1 ${fdtaddr}
/boot/dtbs/${uname_r}/${dtb} *
to access the proper overlay device tree blob. (dtb set in /boot/uEnv.txt)
On Friday, July 1, 2016 at 8:01:09 PM UTC-4, richa...@yahoo.com wrote:
>
> Hi,
>
> Using Robert Nelson's eewiki site, I'm running 4.4.11-bone10.1 (single
> parition) on my BBB via SD; *initrd.img-4.4.11-bone10.1* in built and in
> /boot. I don't see evidence that the initrd.img was detected/mounted. A
> previous version built earlier this year (4.4.1-bone5) (two partitions)
> shows ...
>
>
>
> *[3.484281] Unpacking
> initramfs...
>
> [3.821276] Freeing initrd memory: 5196K (c808 -
> c8593000)
> *
> I sprinkled some debug statements in the kernel ... at line #625 in
> init/main.c, the following lines indicates *initrd_start* and
> *initrd_below_start_ok* as 0.
>
> locking_selftest();
>* pr_notice("RSF!! initrd_start:%d initrd_below_start_ok:%d\n",
> initrd_start, initrd_below_start_ok);*
>
>
> /uEnv.txt has the line to install the file ..
> *loadxrd=load mmc 0:1 **${rdaddr} /boot/initrd.img-${uname_r}; setenv
> rdsize ${filesize}*
> Diagnostics shows this file being read into memory
>
> Should these values be > 0? Am I missing a command line options? Is there
> a way to track progress of the mount in kernel via pr_debug()?
>
>
> thx for the help ..
>
>
--
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/c276f7d9-3a34-4c4a-83e2-b69e2d14cb57%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[beagleboard] initrd.img not detected
Hi,
Per Robert Nelson's eewiki site, I have a running BBB running
4.4.11-bone10.1 version (single partition model);
*initrd.img-4.4.11-bone10.1* is in /boot. A previous version, 4.4.1-bone5,
indicated that initramfs was installed (two partition model)---
[3.484281] Unpacking
initramfs...
[3.821276] Freeing initrd memory: 5196K (c808 -
c8593000)
I don't see those lines now. uEnv.txt in root has ...
"loadxrd=load mmc 0:1 ${rdaddr} /boot/initrd.img-${uname_r}; setenv rdsize
${filesize}"
Diagnostics shows that the file is read into memory OK.
I sprinkled pr_debug() diagnostics in kernel to track progress -- in
start_kernel(void) located in init/main.c
I added around line #625..
locking_selftest();
*pr_notice("initrd_start:%d initrd_below_start_ok:%d\n",
initrd_start, initrd_below_start_ok);*
Both initrd_start and initrd_below_start_ok were 0 ... should these value
be >0? Am I missing a configuration parameter? Are there any
other areas in the kernel to track progress?
thx for any help
--
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/cefe47d0-f786-4472-a469-d67f6c1eb829%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[beagleboard] initrd.img not detected
Hi,
Using Robert Nelson's eewiki site, I'm running 4.4.11-bone10.1 (single
parition) on my BBB via SD; *initrd.img-4.4.11-bone10.1* in built and in
/boot. I don't see evidence that the initrd.img was detected/mounted. A
previous version built earlier this year (4.4.1-bone5) (two partitions)
shows ...
*[3.484281] Unpacking
initramfs...
[3.821276] Freeing initrd memory: 5196K (c808 -
c8593000)
*
I sprinkled some debug statements in the kernel ... at line #625 in
init/main.c, the following lines indicates *initrd_start* and
*initrd_below_start_ok* as 0.
locking_selftest();
* pr_notice("RSF!! initrd_start:%d initrd_below_start_ok:%d\n",
initrd_start, initrd_below_start_ok);*
/uEnv.txt has the line to install the file ..
*loadxrd=load mmc 0:1 **${rdaddr} /boot/initrd.img-${uname_r}; setenv
rdsize ${filesize}*
Diagnostics shows this file being read into memory
Should these values be > 0? Am I missing a command line options? Is there a
way to track progress of the mount in kernel via pr_debug()?
thx for the help ..
--
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/43a4a38c-5b05-4ad9-a1d6-df180e8de2d0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[beagleboard] Incorrect device overlay selected during boot
Hi,
My BBB stack has a 4.3" LCD cape -- powerup diagnostics (dmesg) indicated
the cape was found OK & brightness worked Ok. I was unable to view
(startup) text on the display. (Ver 4.4.1-bone11). After a few days of
debug, I found that the MuxPins were not properly updated and were still
accessing HDMI (not modified as expected). I added an 'echo' into /uEnv.txt
& discovered that the 'overlay file' was not right - it was the default
chosen at power-up.
/boot/uEnv.txt has the lines (amongst others)
dtb=am335x-boneblack-overlay.dtb
Disable: HDMI
/uEnv.txt was modified - *fdtfile* was replaced by *dtb*
#loadxfdt=load mmc 0:1 ${fdtaddr} /boot/dtbs/${uname_r}/${fdtfile}
loadxfdt=load mmc 0:1 ${fdtaddr} /boot/dtbs/${uname_r}/*${dtb}*
Possibly modifying fdtfile is the appropriate method -- Is there a better
solution?
thx
--
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/0da49087-4271-4df2-81f4-e66b763c2ebf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
