On Mon, Aug 10, 2015 at 2:16 PM, Robert Nelson <[email protected]> wrote: > On Mon, Aug 10, 2015 at 2:00 PM, Felipe Balbi <[email protected]> wrote: >> Hi, >> >> On Mon, Aug 10, 2015 at 01:56:04PM -0500, Robert Nelson wrote: >>> On Mon, Aug 10, 2015 at 1:05 PM, Robert Nelson <[email protected]> >>> wrote: >>> > On Mon, Aug 10, 2015 at 11:23 AM, Nuno Gonçalves <[email protected]> >>> > wrote: >>> >> 3 weeks ago I asked for it "For what is worth I believe the OMAP and >>> >> PMIC reset reason registers should be part of the boot log so future >>> >> reboot problems can be sorted.". >>> >> >>> >> But I just asked, I didn't actually code! >>> >> >>> >> Not sure if it is easy to retrieve both, or if PMIC is that much >>> >> relevant for this issues. >>> >> >>> >> Anyway, this will surely take out black magic from the equation when >>> >> debugging this problems. >>> > >>> > Okay here's something quick/dirty... >>> > >>> > http://rcn-ee.homeip.net:81/farm/testing/v4.1.x/MLO-am335x_evm-v2015.07-r3 >>> > http://rcn-ee.homeip.net:81/farm/testing/v4.1.x/u-boot-am335x_evm-v2015.07-r3.img >>> > >>> > #patch: >>> > https://github.com/RobertCNelson/Bootloader-Builder/blob/master/patches/v2015.07/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch#L21 >>> > >>> > make sure the eMMC doesn't have it's own bootloader: >>> > >>> > U-Boot 2015.07-00001-gd8d32cf (Aug 10 2015 - 12:54:52 -0500) >>> > >>> > Watchdog enabled >>> > I2C: ready >>> > DRAM: 512 MiB >>> > Reset Source: Global external warm reset has occurred. >>> > Reset Source: Power-on reset has occurred. >>> > MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 >>> > Using default environment >>> > >>> > dd if=/dev/zero of=/dev/mmcblk1 bs=1M count=10 >>> > >>> > sudo dd if=MLO-am335x_evm-v2015.07-r3 of=/dev/sde count=1 seek=1 bs=128k >>> > sudo dd if=u-boot-am335x_evm-v2015.07-r3.img of=/dev/sde count=2 seek=1 >>> > bs=384k >>> > >>> > I need to fire up x86, that's attached to the bbb's (right now i can't >>> > log serial) >>> >>> Okay.... within a few minutes the first board rebooted... >>> >>> "Reset Source: Power-on reset has occurred." .... >> >> weird, this is likely either flakey DC Jack connection, or PMIC going >> bonkers. >> >> How do you guys reproduce this ? Is the board idle or is it running ? >> Which gadget driver ? Is USB cable connected to a host ? A desktop >> host or wired back into the host port of BBB itself ? >> >> I wanna try to reproduce it here. > > Pretty much just grab: > > http://rcn-ee.com/rootfs/bb.org/testing/2015-08-09/console/bb-debian-8.1-console-armhf-2015-08-09-2gb.img.xz > > dd it to a microSD card and just let it idle.. > > powered via DC > ethernet connected (i was echoing "uptime -p" to a file on nfs) > serial debug attached > usb otg = not connected.. (if you connect this it'll stay ON and won't reset) > usb host = not connected > hdmi = not connected > no capes plugged in > > gadget drivers: 4.1.4-ti-rt-r8 > > CONFIG_USB_MUSB_HDRC=y > # CONFIG_USB_MUSB_HOST is not set > # CONFIG_USB_MUSB_GADGET is not set > CONFIG_USB_MUSB_DUAL_ROLE=y > > CONFIG_USB_MUSB_DSPS=y > CONFIG_USB_MUSB_AM335X_CHILD=y > # CONFIG_USB_TI_CPPI41_DMA is not set > CONFIG_MUSB_PIO_ONLY=y > > CONFIG_USB_LIBCOMPOSITE=y > CONFIG_USB_U_ETHER=y > CONFIG_USB_F_ECM=y > CONFIG_USB_F_SUBSET=y > CONFIG_USB_F_RNDIS=y > # CONFIG_USB_CONFIGFS is not set > # CONFIG_USB_ZERO is not set > # CONFIG_USB_AUDIO is not set > CONFIG_USB_ETH=y > CONFIG_USB_ETH_RNDIS=y > > https://github.com/RobertCNelson/ti-linux-kernel-dev/blob/4.1.4-ti-rt-r8/patches/defconfig#L4804-L4813
Opps that's the rt variant.. https://github.com/RobertCNelson/ti-linux-kernel-dev/blob/4.1.4-ti-r8/patches/defconfig#L4810-L4819 (that section is the same, but to dot the i's) 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.
