Re: [beagleboard] 625 MHz leak?
Gunter, We tried that and this did not work for us. The noise was still there. They said the noise was coming out with a clock signal. Any ideas? Should we check the crystals or something else? Any ideas? Regards, Shu On Saturday, January 31, 2015 at 12:23:15 PM UTC-6, dl4mea wrote: In a similar problem it helped for me to replace the 0.1R that connectes Ethernet shield to the frame of the Beaglebone by a simple solder bridge. This resistor is located on the solder side of the Beaglebone, just below the network connector. I have a spectrum analyzer and a 3GHz active probe and was astonished about the amount of infuence. Sounds crazy but prooven many times meanwhile. Regards, Günter -- 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.
Re: [beagleboard] 625 MHz leak?
Liyaoshi, We have the same problem. I agree with what you mentioned. We checked If the RJ45 cable is not plugged in, but still failed the Radiated emissions test. What else we should look into? the RJ45 connector has the integrated magnetic. Regards, Shu On Wednesday, May 14, 2014 at 9:52:10 PM UTC-5, liyaoshi wrote: 625M clock noise maybe from 125M clocksource， or 25M This might be from ethernet Do you use GIGA ethernet ? And Try to unplug the RJ45 cable 2014-05-15 5:01 GMT+08:00 Gerald Coley ger...@beagleboard.org javascript:: OK. Understood. Different test equipment will yield different results. And it can be effected by the SW you are running. Gerald On Wed, May 14, 2014 at 3:59 PM, l...@ansync.com javascript: wrote: It's not something unique to our board--a stock BBB has the same problem. On Wednesday, May 14, 2014 1:41:29 PM UTC-7, Gerald wrote: Sounds like you may have grounding issues or unterminated pin . Using a probe should let you be able to determine which side of the chip it is. Gerald On Wed, May 14, 2014 at 3:37 PM, l...@ansync.com wrote: It seems to come from right around the processor, but we couldn't pinpoint it any more precisely than that, or even to one side of the board or other. On Wednesday, May 14, 2014 10:56:28 AM UTC-7, Gerald wrote: In order to mitigate it you need to figure out where it is coming from. A probe test will help in that area. Have you run one? Using ferrites on all cables generally helps in these types of issues. Gerald On Wed, May 14, 2014 at 12:01 PM, l...@ansync.com wrote: We have a BBB-based design currently undergoing FCC testing, and they've found a bit of noise at 625 MHz. Has anyone else encountered this, or know what it might be, or how to mitigate it? -- 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...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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...@googlegroups.com javascript:. For more options, visit https://groups.google.com/d/optout. -- 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...@googlegroups.com javascript:. For more options, visit https://groups.google.com/d/optout. -- 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.
Re: [beagleboard] 625 MHz leak?
Lee, Did you find out what cause the noise? We have the same problem right now. Our noise is from 300M to 600M. Regards, Shu On Wednesday, May 14, 2014 at 3:59:24 PM UTC-5, Lee Crocker wrote: It's not something unique to our board--a stock BBB has the same problem. On Wednesday, May 14, 2014 1:41:29 PM UTC-7, Gerald wrote: Sounds like you may have grounding issues or unterminated pin . Using a probe should let you be able to determine which side of the chip it is. Gerald On Wed, May 14, 2014 at 3:37 PM, l...@ansync.com wrote: It seems to come from right around the processor, but we couldn't pinpoint it any more precisely than that, or even to one side of the board or other. On Wednesday, May 14, 2014 10:56:28 AM UTC-7, Gerald wrote: In order to mitigate it you need to figure out where it is coming from. A probe test will help in that area. Have you run one? Using ferrites on all cables generally helps in these types of issues. Gerald On Wed, May 14, 2014 at 12:01 PM, l...@ansync.com wrote: We have a BBB-based design currently undergoing FCC testing, and they've found a bit of noise at 625 MHz. Has anyone else encountered this, or know what it might be, or how to mitigate it? -- 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...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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.
Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on
Mikkil, Thanks for you detailed answer. U15.1: _1OE = 0V U15.2: 1A= 0V U15.3: 2Y= floating (flickering +-0.000,50V) U15.4: GND = 0V U15.5: 2A = UART0_RX = 3.335V U15.6: 1Y = UART0_TX = 3.195V U15.7: 2OE = 3.352V U15.8: VCC = 3.352V Based on the voltages that when U15 is removed, the UART0_RX is at its proper voltage level (3V3) that is defined in the device tree. The strange thing is that when U15 is there, the UART0_RX is not getting 3V3. _1OE is low and 2OE is high. Then the voltage on the j4.4 should be the same as UART0_RX. But J4.4 is not 3.3V (it was 1.4 on my board) even when R165 is removed, therefore, UART0_RX is not 3.3V. How did you get the 0.58V on J4.4 using 1K resistor? I do not why 0.58V works. To my understanding, the default idle state should be high on both TX and RX lines for UART0. Regards, Shu -- 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.
Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on
Mikkel,
You can give a 3.3v directly or use a small resistor to make the voltage on
the 4th pin of J1 higher than 3V. That should work. We rebooted a board
over hundreds of time by using an app on Linux. It did not fail a single
time.
We found this accidently by using serial cable and the board never fails to
boot when the cable is connected. The serial cable gives the 3.3v to the
4th pin which is the UART0_RX.
We tried to figure out what cause the problem and found a weird thing. We
measured the UART3_RX(D16), UART3_TX(D15), UART4_RX(pin11 on header P9) and
UART4_TX(pin13 on header P9). They are all 3.3V and they are in UART mode.
We removed the R165 which is the pull down resistor on the UART0_RX line.
The UART0_RX is around 1.4V and sometimes floating. We also checked the
device tree. The internal pull up of the UART0_RX is turned on.
uart0_pins: pinmux_uart0_pins {
pinctrl-single,pins =
0x170 (PIN_INPUT_PULLUP | MUX_MODE0) /* uart0_rxd.uart0_rxd */
We do not know why the UART0_RX is not getting 3.3V, can you please check
the voltage on both UART0_TX and UART0_RX when U15 is removed?
Again, If somebody can tell me how to fix it in uboot or from software
perspective, I would really appreciate it.
Regards,
Shu
--
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.
Re: [beagleboard] BBB won't boot up (PWR Led does a single quick blink)
Hi, There should be a short on board. The U2 shuts itself down to prevent the high current draw which is caused by the short. That is why the LED goes off after it blinks once. Regards, Shu On Monday, October 27, 2014 10:56:34 PM UTC-5, s...@kopi-d.com wrote: I am in the same situation. Was trying out new images. Did an forced SD change to a non-bootable bbb. Now it won't boot. Just a pwr blink then dead. Are there any other ways to recover other than RMA? PMIC replacement or reflashing of bootloader? Sam On Wednesday, June 18, 2014 9:53:25 PM UTC+8, Gerald wrote: Request an RMA. http://beagleboard.org/Support/RMA And read this. http://www.elinux.org/Beagleboard:BeagleBoneBlack#Hardware Gerald On Mon, Jun 9, 2014 at 5:54 PM, v...@victor.so wrote: My BBB (A5A) was working fine with ARM Arch (installed on the eMMC), but since yesterday it won't turn on. I don't know what changed. When I plug the power source or the USB cable the PWR Led quickly blinks, but the board doesn't turn on. If I press the POWER button, the PWR led does a single blink too, but it doesn't proceed to boot. I also tried to boot from the SD card, but It didn't work. -- 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...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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.
Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on
Mikkel, You don't have to remove the whole U15. You can just give a 3.3V pull-up to the 4th PIN on the J1 connector. Then the board will not be stuck at the UBOOT anymore. My question is how to fix it from software perspective? In u-Boot source, how can we make sure it is not stuck? If anyone can answer my question, i would really appreciate it. Regards, Shu On Friday, October 31, 2014 12:19:11 PM UTC-5, mi...@mikini.dk wrote: On October 16th 2014 21.26.23 UTC+2 Gerald wrote: Is the power LED shutoff too? Gerald Hi Gerald. I'm also affected by the OP's issue of periodic failing boots on BBB (I got all REV Bs). My experience has always been with the power led lighting up and the system stuck without booting. Pressing the reset switch takes the system out of this locked up state, but neither boot switch or power switch has any effect. I am very interested in your input on the successful experiences put forward by Andrew and Marcus in May, about modifying uboot to remedy noise input on UART0_RXD (pin E15 of AM3358). I have done some tests today documenting the basic issue and some followup experiments investigating this specific cause, and I would appreciate if you could take a look and comment on the resulting speculations. You can find the details here; http://www.mikini.dk/index.php/2014/10/beaglebone-black-periodic-boot-failure-establishing-failure-rate-and-possible-cause . Executive summary; removing U15 (SN74LVC2G241: UART0 powerdown isolation) seems to remedy the boot issue on a CircuitCo-produced BBB in my possession. Although my result is inconclusive, as I was careless enough to rush myself into omitting a pre-modification test, verifying the failure rate of the unmodified BBB. Thanks in advance for your help, and for my Beagle puppies ;). Mikkel -- 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.
Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on
Andrew, I tried that already. The file ../include/config.h is automatically generated when recompiling. I added the two lines which I marked red below. After I recompiled the uboot source again, the new generated config.h file replaces the old one that i modified and does not have the two lines. My question is that have the two lines got recompiled into the u-boot.img? Or am I missing something here? /* Automatically generated - do not edit */ #define CONFIG_SERIAL11 #define CONFIG_CONS_INDEX1 #define CONFIG_NAND1 #define CONFIG_SYS_ARCH arm #define CONFIG_SYS_CPU armv7 #define CONFIG_SYS_BOARD am335x #define CONFIG_SYS_VENDOR ti #define CONFIG_SYS_SOCam33xx #define CONFIG_BOARDDIR board/ti/am335x #define CONFIG_AUTOBOOT_KEYED 1 #define CONFIG_AUTOBOOT_DELAY_STR uboot #include config_cmd_defaults.h #include config_defaults.h #include configs/am335x_evm.h #include asm/config.h #include config_fallbacks.h #include config_uncmd_spl.h -- 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.
Re: [beagleboard] How to change Device Tree Blob (.dtb) file since the kernel does not have capemgr to load overlays.
Robert,
I do not know why I posted a reply with an image like 3 hours ago and it
did not show up until now. Below are the logs I got by typing printenv.
The board loads the fdtfile=am335x-boneblack.dtb. I used find -iname
*.dts and I do not see any device tree source in the SD card. I will look
for one online.
My question are:
1. Is the uEnv.txt needed for the board? If so, how to create the file?
2. After making the pinmux changes in the .dts file, how to recompile the
kernel and the device tree source using the following commands? Or is there
an easy way to do the device tree change in the 3.12 kernel?
make omap2plus_defconfig
make zImage dtbs
make modules
make modules_install INSTALL_MOD_PATH=rootfs location
I am really new to Linux. If you can answer my questions, I would be really
appreciate it.
U-Boot# printenv
arch=arm
baudrate=115200
board=am335x
board_name=A335BNLT
board_rev=
bootcmd=gpio set 53; i2c mw 0x24 1 0x3e; run findfdt; mmc dev 0; if mmc
rescan ; then echo micro SD card found;setenv mmcdev 0;else echo No micro
SD card found, setting mmcdev to 1;setenv mmcdev 1;fi;setenv bootpart
${mmcdev}:2;mmc dev ${mmcdev}; if mmc rescan; then gpio set 54; echo SD/MMC
found on device ${mmcdev};if run loadbootenv; then echo Loaded environment
from ${bootenv};run importbootenv;fi;if test -n $uenvcmd; then echo Running
uenvcmd ...;run uenvcmd;fi;gpio set 55; if run loaduimage; then gpio set
56; run loadfdt;run mmcboot;fi;fi;
bootdelay=1
bootdir=/boot
bootenv=uEnv.txt
bootfile=uImage
bootpart=0:2
console=ttyO0,115200n8
cpu=armv7
dfu_alt_info_emmc=rawemmc mmc 0 3751936
dfu_alt_info_mmc=boot part 0 1;rootfs part 0 2;MLO fat 0 1;MLO.raw mmc 100
100;u-boot.img.raw mmc 300 3C0;u-boot.img fat 0 1;uEnv.txt fat 0 1
dfu_alt_info_nand=SPL part 0 1;SPL.backup1 part 0 2;SPL.backup2 part 0
3;SPL.backup3 part 0 4;u-boot part 0 5;kernel part 0 7;rootfs part 0 8
ethact=cpsw
ethaddr=1c:ba:8c:95:7b:cf
fdt_high=0x
fdtaddr=0x80F8
fdtfile=am335x-boneblack.dtb
findfdt=if test $board_name = A33515BB; then setenv fdtfile am335x-evm.dtb;
fi; if test $board_name = A335X_SK; then setenv fdtfile am335x-evmsk.dtb;
fi;if test $board_name = A335BONE; then setenv fdtfile am335x-bone.dtb; fi;
if test $board_name = A335BNLT; then setenv fdtfile am335x-boneblack.dtb; fi
importbootenv=echo Importing environment from mmc ...; env import -t
$loadaddr $filesize
kloadaddr=0x80007fc0
loadaddr=0x8020
loadbootenv=load mmc ${mmcdev} ${loadaddr} ${bootenv}
--
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.
Re: [beagleboard] How to change Device Tree Blob (.dtb) file since the kernel does not have capemgr to load overlays.
Robert, This is what i see from the printenv. It loads the fdtfile=am335x-boneblack.dtb device tree file. Can I create a new .dtb and replace the am335x-boneblack.dtb to load my new .dtb? Or how to create an uEnv.txt ? Regareds, https://lh5.googleusercontent.com/-fRGlYNZjbgg/VDRJduxmw2I/ARU/TOHpt8AAEt4/s1600/1.jpg Shu -- 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] How to change Device Tree Blob (.dtb) file since the kernel does not have capemgr to load overlays.
Hi, Our board uses arago project on it. The kernel is 3.12 and in the directory /sys/devices/, there is no capemgr.* . Therefore, I am not able to use the device tree overlays (.dtbo). We want to change the pinmux on the P8 and P9 header and also turn the internal pull up resistor of the UART0_RX on. Therefore, we need to modify the current beaglebone black .dtb file. My question are as follows: 1. Can I just replace the current am335x-boneblack.dtb with the new .dtb file to make the pinmux changes? Or do i need to load the new .dtb file up and how? 2. I see that there are a lot of .dtb in the /boot/ folder. How to load different .dtb when board boots up? Regards, Shu -- 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.
Re: [beagleboard] How to change Device Tree Blob (.dtb) file since the kernel does not have capemgr to load overlays.
Robert, Thanks for your reply. We do not have the bootloader source. We only use the bootloader image file. There are two partitions in the SD card. In the boot partition, there are only MLO and u-boot.img. In the rootfs partition, in the folder /boot/, there are .dtb files and zImage files. There is no uEnv.txt file. So the uEnv.txt is the bootloader's specification? How can create the uEnv.txt file and make changes in it to let the uboot to use the new .dtb file? Regards, Shu -- 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] UART0(J1 connector) of BeagleboneBlack
We had a weird problem when running our Beaglebone black board with Linux. We boot the system every 5 minutes. The UART0 (J1 connector) of BBB is tied to the serial console of the system by default, and it prints out a lot of logs via serial cable if the cable is connected. The board runs very well when the UART0 is connected with a serial cable. If the serial cable is not connected, the board would run around 1-6 hours and after that, it can not boot up again.The more logs that we print out on the serial console, the quicker the board goes down and can not boot up again. Rebooting will also print a lot of boot logs on the console. Would the buffer on UART0 of BBB side getting full cause the board crashing and not booting up again, since the serial cable is not connected and the UART0 has no outlet? Is there any ways to disable the boot logs when system boots up? Or is there a way to collect those logs? Thanks. The board version is BBB A6C. -- 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] UART0 crashes the Beaglebone black board
We had a weird problem when running our Beaglebone black board with Linux. We boot the system every 5 minutes. The UART 0 of BBB is tied to the serial console of the system by default, and it prints out a lot of logs via serial cable if the cable is connected. The board runs very well when the UART0 is connected with a serial cable. If the serial cable is not connected, the board would run around 1-6 hours and after that, it can not boot up again.The more logs that we print out on the serial console, the quicker the board goes down and can not boot up again. Rebooting will also print a lot of boot logs on the console. Would the buffer on UART0 of BBB side getting full cause the board crashed and not booting up again, since the serial cable is not connected and the UART0 has no outlet? Is there any way to disable the boot logs when system boots up or to collect those logs? -- 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] How to flash the eMMC using JTAG and TI CCS
Hi, We are using BBB for our software development. We were able to use SD card to flash the eMMC of the BBB. I am not sure if there is a faster way, like using JTAG and CCS, to flash the eMMC? Thanks. -- 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.
