[beagleboard] Why ADC helper driver does not work?
In my project I use ADC. But I try to avoid dynamic overlay loading in order to
increase boot speed.
So I move code from ADC overlay (BB-ADC-00A0.dts) to main device tree source
(am335x-boneblack.dts):
/ {
...
ocp {
/* ADC filesystem helper
*/
test_helper: helper {
compatible = "bone-iio-helper";
vsense-name = "AIN0", "AIN1", "AIN2", "AIN3", "AIN4",
"AIN5", "AIN6", "AIN7";
vsense-scale = <100 100 100 100 100
100 100 100>;
status = "okay";
};
};
};
/* Enable ADC */
&tscadc {
status = "okay";
adc {
ti,adc-channels = <0 1 2 3 4 5 6 7>;
};
};
After boot I found out that directory /sys/devices/ocp.*/helper.*/ does not
contain AIN files. dmesg out dos not contain messages from
bone-iio-helper driver. Somehow bone-iio-helper driver haven't been loaded
while device tree processing.
Is there a way to fix this issue?
--
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/796e4fb3-a2cd-4f4e-acd2-53540c259ae4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: PREBOOT delay. Is it possible to reduce it?
The actual reson for the delay was the increased cost of memory reservation, the size of which increased from 1 kb to 16 mb: diff --git a/include/configs/ti_armv7_common.h b/include/configs/ ti_armv7_common.h index 6982918..6e0bf09 100644 --- a/include/configs/ti_armv7_common.h +++ b/include/configs/ti_armv7_common.h @@ -127,7 +127,7 @@ * we are on so we do not need to rely on the command prompt. We set a * console baudrate of 115200 and use the default baud rate table. */ -#define CONFIG_SYS_MALLOC_LEN (1024 << 10) +#define CONFIG_SYS_MALLOC_LEN (16 << 20) #define CONFIG_SYS_HUSH_PARSER #define CONFIG_SYS_PROMPT "U-Boot# " But you can completely avoid the loss of time if you omit the initial cleaning of the redundant memory: #undef CONFIG_SYS_MALLOC_CLEAR_ON_INIT -- 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/a21f4524-8e75-4eb7-9373-8cad796dd36d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] PREBOOT delay. Is it possible to reduce it?
Hi, I'm try to optimize boot time BeagleBone Black board. The forum already has a few helpful tips to reduce boot time in stage u-boot and linux kernel loading. But one question remains uncovered. I found that there is a delay (near 2 sec) between the power on and the emergance of first debug message on serial port. I wonder what's going on in those two seconds. Is it CPU initialization procedure, or the way to avoid jitter when plug in power supply. Is it possible to reduce this delay? ~[00:000] - plug in power supply [*02:291*] ▒ *<--- Look here* [02:310] U-Boot SPL 2015.10-dirty (Nov 14 2015 - 13:18:58) [02:490] MMC: block number 0x100 exceeds max(0x0) [02:494] MMC: block number 0x200 exceeds max(0x0) [02:498] *** Error - No Valid Environment Area found [02:503] *** Warning - bad CRC, using default environment [02:519] [02:551] [02:551] U-Boot 2015.10-dirty (Nov 14 2015 - 13:18:58 -0800) [02:555] [02:555] Watchdog enabled [02:559] I2C: ready [02:613] DRAM: 512 MiB [02:661] Reset Source: Power-on reset has occurred. [02:665] MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 [03:112] *** Warning - bad CRC, using default environment [03:132] [03:207] Net: not set. Validating first E-fuse MAC [03:249] cpsw [03:250] Hit any key to stop autoboot: 0 (autoboot.c) [03:255] gpio: pin 53 (gpio 53) value is 1 [03:330] switch to partitions #0, OK [03:332] mmc0 is current device Regards. - Andrey Kuznetcov -- 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. For more options, visit https://groups.google.com/d/optout.
[beagleboard] PREBOOT delay. Is it possible to reduce it?
Hi, I'm try to optimize boot time BeagleBone Black board. The forum already has a few helpful tips to reduce boot time in stage u-boot and linux kernel loading. But one question remains uncovered. I found that there is a delay (near 2 sec) between the power on and the emergance of first debug message on serial port. I wonder what's going on in those two seconds. Is it CPU initialization procedure, or the way to avoid jitter when plug in power supply. Is it possible to reduce this delay? ~[00:000] - plug in power supply [*02:291*] ▒ *<--- Look here* [02:310] U-Boot SPL 2015.10-dirty (Nov 14 2015 - 13:18:58) [02:490] MMC: block number 0x100 exceeds max(0x0) [02:494] MMC: block number 0x200 exceeds max(0x0) [02:498] *** Error - No Valid Environment Area found [02:503] *** Warning - bad CRC, using default environment [02:519] [02:551] [02:551] U-Boot 2015.10-dirty (Nov 14 2015 - 13:18:58 -0800) [02:555] [02:555] Watchdog enabled [02:559] I2C: ready [02:613] DRAM: 512 MiB [02:661] Reset Source: Power-on reset has occurred. [02:665] MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 [03:112] *** Warning - bad CRC, using default environment [03:132] [03:207] Net: not set. Validating first E-fuse MAC [03:249] cpsw [03:250] Hit any key to stop autoboot: 0 (autoboot.c) [03:255] gpio: pin 53 (gpio 53) value is 1 [03:330] switch to partitions #0, OK [03:332] mmc0 is current device Regards. - Andrey Kuznetcov -- 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. For more options, visit https://groups.google.com/d/optout.
[beagleboard] PREBOOT delay. Is it possible to reduce it?
Hi, I'm try to optimize boot time BeagleBone Black board. The forum already has a few helpful tips to reduce boot time in stage u-boot and linux kernel loading. But one question remains uncovered. I found that there is a delay (near 2 sec) between the power on and the emergance of first debug message on serial port. I wonder what's going on in those two seconds. Is it CPU initialization procedure, or the way to avoid jitter when plug in power supply. Is it possible to reduce this delay? ~[00:000] - plug in power supply [*02:291*] ▒ *<--- Look here* [02:310] U-Boot SPL 2015.10-dirty (Nov 14 2015 - 13:18:58) [02:490] MMC: block number 0x100 exceeds max(0x0) [02:494] MMC: block number 0x200 exceeds max(0x0) [02:498] *** Error - No Valid Environment Area found [02:503] *** Warning - bad CRC, using default environment [02:519] [02:551] [02:551] U-Boot 2015.10-dirty (Nov 14 2015 - 13:18:58 -0800) [02:555] [02:555] Watchdog enabled [02:559] I2C: ready [02:613] DRAM: 512 MiB [02:661] Reset Source: Power-on reset has occurred. [02:665] MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 [03:112] *** Warning - bad CRC, using default environment [03:132] [03:207] Net: not set. Validating first E-fuse MAC [03:249] cpsw [03:250] Hit any key to stop autoboot: 0 (autoboot.c) [03:255] gpio: pin 53 (gpio 53) value is 1 [03:330] switch to partitions #0, OK [03:332] mmc0 is current device Regards. - Andrey Kuznetcov -- 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. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: PREBOOT delay. Is it possible to reduce it?
I have tried run defferent images from SD: 1.Debian 2015-07-28 console with *u-boot v2015.01* writed to unallocated space in front of first partition -* 2 second delay remains* 2.Jessie Snapshot console with *u-boot v2015.10* writed to unallocated space in front of first partition -* 2 second delay remains* 3. Angstrom v2012.12 (kernel 3.8.13) with *u-boot 2013.04-dirty* writed to FAT32-MLO BOOT partition - *start immediately after plug in power supply* So, I assumed that the problem is in the method of placing the loader. But if replace u-boot v2015.01 with u-boot v2013.04, then delay disappears. The new version has something that leads to a pause. What could it be? -- 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. For more options, visit https://groups.google.com/d/optout.
