Re: [beagleboard] Re: kernel panic when flashing eMMC from uSD made from /opt/scripts/tools/beaglebon...

2016-07-27 Thread Matt99eo 

>
> Hi RC,
>

Still trying to make this work.  I have attached a wired network cable and 
can ping outside word.

I then reran the  

beaglebone-black-make-microSD-flasher-from-eMMC.sh

Card makes and when I start the flash on a new device I am getting the same 
result:

Starting eMMC Flasher from microSD media
Version: [1.20160718: mkfs.ext4 1.43...]
-
Checking for Valid bbb-eeprom header
Valid bbb-eeprom header found [335]
-
copying: [/dev/mmcblk0] -> [/dev/mmcblk1]
lsblk:
NAME MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
mmcblk1boot0 179:16   01M  1 disk 
mmcblk1boot1 179:24   01M  1 disk 
mmcblk0  179:00  7.4G  0 disk 
`-mmcblk0p1  179:10  7.4G  0 part /
mmcblk1  179:80  3.7G  0 disk 
-
df -h | grep rootfs:
-
Erasing: /dev/mmcblk1
108+0 records in
108+0 records out
113246208 bytes (113 MB) copied, 17.217 s, 6.6 MB/s
[   32.568856] random: nonblocking pool is initialized
108+0 records in
108+0 records out
113246208 bytes (113 MB) copied, 4.352 s, 26.0 MB/s
Erasing: /dev/mmcblk1 complete
-
Writing bootloader to [/dev/mmcblk1]
dd if= of=/dev/mmcblk1 count=1 seek=1 bs=128k
-
dd: failed to open '': No such file or directory
[   34.346790] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0100
[   34.346790] 
[   34.358792] CPU: 0 PID: 1 Comm: init-eMMC-flash Not tainted 
4.1.21-bone-rt-r20 #1
[   34.366303] Hardware name: Generic AM33XX (Flattened Device Tree)
[   34.372465] [] (unwind_backtrace) from [] 
(show_stack+0x11/0x14)
[   34.380254] [] (show_stack) from [] 
(panic+0x6d/0x188)
[   34.387165] [] (panic) from [] 
(complete_and_exit+0x1/0x18)
[   34.394509] [] (complete_and_exit) from [] 
(sigprocmask+0x59/0x88)
[   34.402465] [] (sigprocmask) from [<0001>] (0x1)
[   34.408330] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0100
[   34.408330] 
[  509.671

For some reason I am still not getting the boot loader.

On board I am cloning I do see MLO

root@arm:/opt/backup/uboot# ls
index.html  MLO  u-boot.img

Next steps?

-- 
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/e062470d-fa57-42e3-bc34-09a5cef1f766%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: kernel panic when flashing eMMC from uSD made from /opt/scripts/tools/beaglebon...

2016-05-31 Thread Matt99eo 
Ok did that and still having there same error. Validated network connection 
and reran script. Below is the output of creating the image and then what I 
am getting when trying to use the image:

Creating uSD:
root@arm:/opt/scripts/tools/eMMC# 
./beaglebone-black-make-microSD-flasher-from-eMMC.sh 

Unmounting Partitions
-
 [3;J
-
Version: [1.20160322: upgrade backup u-boot: v2016.03-r6...]
-
copying: [/dev/mmcblk0] -> [/dev/mmcblk1]
lsblk:
NAME MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
mmcblk0boot0 179:801M  1 disk 
mmcblk0boot1 179:16   01M  1 disk 
mmcblk0  179:00  3.7G  0 disk 
└─mmcblk0p1  179:10  3.7G  0 part /
mmcblk1  179:24   0  3.7G  0 disk 
└─mmcblk1p1  179:25   0  3.7G  0 part 
-
df -h | grep rootfs:
-
update-initramfs: Generating /boot/initrd.img-4.1.21-bone-rt-r20
Erasing: /dev/mmcblk1
108+0 records in
108+0 records out
113246208 bytes (113 MB) copied, 10.8226 s, 10.5 MB/s
108+0 records in
108+0 records out
113246208 bytes (113 MB) copied, 5.8479 s, 19.4 MB/s
Erasing: /dev/mmcblk1 complete
-
Writing bootloader to [/dev/mmcblk1]
dd if=/opt/backup/uboot/MLO of=/dev/mmcblk1 count=1 seek=1 bs=128k
-
0+1 records in
0+1 records out
65708 bytes (66 kB) copied, 0.0937003 s, 701 kB/s
-
dd if=/opt/backup/uboot/u-boot.img of=/dev/mmcblk1 count=2 seek=1 bs=384k
-
0+1 records in
0+1 records out
350020 bytes (350 kB) copied, 0.104779 s, 3.3 MB/s
-
Formatting: /dev/mmcblk1
sfdisk: [sfdisk from util-linux 2.25.2]
sfdisk: [sfdisk --force --Linux --in-order --unit M /dev/mmcblk1]
sfdisk: [1,,L,*]
sfdisk: Checking that no-one is using this disk right now ...
sfdisk: OK

Disk /dev/mmcblk1: 121472 cylinders, 4 heads, 16 sectors/track
sfdisk:  /dev/mmcblk1: unrecognized partition table type
Old situation:
sfdisk: No partitions found
New situation:
Units: 1MiB = 1024*1024 bytes, blocks of 1024 bytes, counting from 0

   Device Boot Start   EndMiB#blocks   Id  System
/dev/mmcblk1p1   * 1   3795   37953886080   83  Linux
/dev/mmcblk1p2 0  -  0  00  Empty
/dev/mmcblk1p3 0  -  0  00  Empty
/dev/mmcblk1p4 0  -  0  00  Empty
Successfully wrote the new partition table

Re-reading the partition table ...

sfdisk: If you created or changed a DOS partition, /dev/foo7, say, then use 
dd(1)
to zero the first 512 bytes:  dd if=/dev/zero of=/dev/foo7 bs=512 count=1
(See fdisk(8).)
mkfs.ext4 /dev/mmcblk1p1 -L BEAGLEBONE
-
mke2fs 1.42.12 (29-Aug-2014)
Discarding device blocks: done
Creating filesystem with 971520 4k blocks and 242880 inodes
Filesystem UUID: 11b1347f-86bb-46e0-8779-764f298bcd3e
Superblock backups stored on blocks: 
32768, 98304, 163840, 229376, 294912, 819200, 884736

Allocating group tables: done
Writing inode tables: done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done 

-
Formatting: /dev/mmcblk1 complete
-
Copying: /dev/mmcblk0p1 -> /dev/mmcblk1p1
rsync: / -> /tmp/rootfs/
rsync: note the % column is useless...
691.19M  99%4.05MB/s0:02:42 (xfr#25078, to-chk=0/31857)   
Copying: Kernel modules
rsync: /lib/modules/4.1.21-bone-rt-r20/ -> 
/tmp/rootfs/lib/modules/4.1.21-bone-rt-r20/
rsync: note the % column is useless...
 55.61M  99%4.04MB/s0:00:13 (xfr#2266, to-chk=0/2652)   
Copying: /dev/mmcblk0p1 -> /dev/mmcblk1p1 complete
-
Final System Tweaks:
UUID=11b1347f-86bb-46e0-8779-764f298bcd3e
Generating: /etc/fstab
# /etc/fstab: static file system information.
#
UUID=11b1347f-86bb-46e0-8779-764f298bcd3e  /  ext4  
noatime,errors=remount-ro  0  1
debugfs  /sys/kernel/debug  debugfs  defaults  0  0
/boot/uEnv.txt: enabling eMMC flasher script
uname_r=4.1.21-bone-rt-r20
#uuid=81b9a3e8-1ff6-4797-b2eb-f4517ab96628
cape_enable=bone_capemgr.enable_partno=BB-APA-01
uuid=11b1347f-86bb-46e0-8779-764f298bcd3e
cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh
-
Syncing: /dev/mmcblk1
./beaglebone-black-make-microSD-flasher-from-eMMC.sh: line 309:  6860 
Terminated  cylon_leds
10+0 records in
10+0 records out
5120 bytes (51 MB) copied, 2.56244 s, 20.0 MB/s
Syncing: /dev/mmcblk1 complete
-
umount: /tmp: not mounted
umount: /tmp: not mounted



And here is the serial output when tyring to use the uSD:

U-Boot SPL 2016.03-dirty (Apr 19 2016 - 15:43:26)
Trying to boot from MMC
bad magic


U-Boot 2016.03-dirty (Apr 19 2016 - 15:43:26 -0700)

   Watchdog enabled

Re: [beagleboard] Re: kernel panic when flashing eMMC from uSD made from /opt/scripts/tools/beaglebon...

2016-05-31 Thread Robert Nelson 
On Tue, May 31, 2016 at 4:32 PM, Matt Maher Peterson <
matt.maherpeter...@hydro-care.com> wrote:

> Sorry about that.
>
> So am I interpreting your response right that I need to go back to 4.1.21
> that I am trying to clone, connect it to the network and run the make uSD
> from emmc again to create a new image?
>

rerun:

beaglebone-black-make-microSD-flasher-from-eMMC.sh

making sure you have the network connected and access enabled..

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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYgkiq%3DbHuU_qa%2BFDceKJXwdAyU9eAYZSh-ZtyYwG9ZuoQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: kernel panic when flashing eMMC from uSD made from /opt/scripts/tools/beaglebon...

2016-05-31 Thread Matt Maher Peterson 
Sorry about that.  

So am I interpreting your response right that I need to go back to 4.1.21 
that I am trying to clone, connect it to the network and run the make uSD 
from emmc again to create a new image?

On Tuesday, May 31, 2016 at 9:06:49 AM UTC-7, RobertCNelson wrote:
>
>
>
> On Tue, May 31, 2016 at 11:00 AM, Matt99eo  > wrote:
>
>> Bump.
>>
>>
>> Still trying to solve this.  Any help appreciated.
>>
>> Is there another method I should use to clone my 4.1.21 Debian Jessie BBB?
>>
>
> Well this had already been answered:
>
> https://groups.google.com/forum/#!category-topic/beagleboard/UIXhMlNXgh0
>
> but then you changed the message "topic" after google groups had already 
> sent the emails out..
>
> Thus losing the reply...
>
> 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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/6c2ffa6f-dc6d-4085-8b96-a7203c4cafeb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: kernel panic when flashing eMMC from uSD made from /opt/scripts/tools/beaglebon...

2016-05-31 Thread Robert Nelson 
On Tue, May 31, 2016 at 11:00 AM, Matt99eo 
wrote:

> Bump.
>
>
> Still trying to solve this.  Any help appreciated.
>
> Is there another method I should use to clone my 4.1.21 Debian Jessie BBB?
>

Well this had already been answered:

https://groups.google.com/forum/#!category-topic/beagleboard/UIXhMlNXgh0

but then you changed the message "topic" after google groups had already
sent the emails out..

Thus losing the reply...

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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYgJ7Q4FL%3Dq9J-nvCVCh-40T%3DUHmXMP_V9m5F4TuHL47PA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.