Sorry WHen I pressed S1 , boot happens fine.! On Wednesday, August 10, 2016 at 1:31:44 PM UTC+5:30, Raulp wrote: > > Thanks William , Robert ! > I pressed removed the power supply , reconnected it , pressed the S3 > switch and it booted with the changed kernel image. > Dont know why? > > On Wednesday, August 10, 2016 at 12:28:03 PM UTC+5:30, William Hermans > wrote: >> >> Since you only got a uboot prompt I'll assume you missed one, or both >> uEnv.txt files. >> >> On Tue, Aug 9, 2016 at 11:55 PM, William Hermans <[email protected]> >> wrote: >> >>> does /media/rootfs/boot/uEnv.txt contain: >>> >>> uname_r=${kernel_version} >>> >>> ? >>> >>> For that matter you never mention if you have a first stage uEnv.xt file >>> ( /uEnv.txt ). Granted this assumes redoing form a blank rootfs. But if >>> this is not a blank rootfs then your step #3 should not be necessry. >>> >>> On Tue, Aug 9, 2016 at 9:31 PM, Raulp <[email protected]> wrote: >>> >>>> I did get the minicom logs but it shows only uboot# prompt. >>>> >>>> What I did was this : >>>> 1-->modified one dtb and ran rebuild.sh >>>> >>>> 2-->Copy Kernel Image >>>> Kernel Image: >>>> ~/ >>>> sudo cp -v ./bb-kernel/deploy/${kernel_version}.zImage >>>> /media/rootfs/boot/vmlinuz-${kernel_version} >>>> 3--->Copy Kernel Device Tree Binaries >>>> ~/ >>>> sudo mkdir -p /media/rootfs/boot/dtbs/${kernel_version}/ >>>> sudo tar xfv ./bb-kernel/deploy/${kernel_version}-dtbs.tar.gz -C >>>> /media/rootfs/boot/dtbs/${kernel_version}/ >>>> -4-->Copy Kernel Modules >>>> ~/ >>>> sudo tar xfv ./bb-kernel/deploy/${kernel_version}-modules.tar.gz -C >>>> /media/rootfs/ >>>> >>>> Did I miss something? >>>> Last resort would be to format and prepare the card again .!! >>>> >>>> On Tuesday, August 9, 2016 at 7:29:55 PM UTC+5:30, RobertCNelson wrote: >>>>> >>>>> On Tue, Aug 9, 2016 at 8:53 AM, Jane <[email protected]> wrote: >>>>> > I did copy the modules and the device trees along with the uimage. >>>>> > System doesnt boots ups ! >>>>> > No logs on Minicom as well.! >>>>> >>>>> No serial logs on Minicom? >>>>> >>>>> 50/50, it's a minicom configuration issue, try again with gtkterm.. >>>>> >>>>> If it doesn't work with gtkterm, then it's likely you didn't install >>>>> the bootloader properly (try again). (or you are using >>>>> VirtualBox/VMware/etc, which the directions say doesn't work and is >>>>> un-supported) >>>>> >>>>> 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/54606420-e696-45eb-975a-c870a54a7b39%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/beagleboard/54606420-e696-45eb-975a-c870a54a7b39%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>>> 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/86ef3a81-78dc-4fc6-aafb-9258f3457dcd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
