Hi.
I'm doings some tests with the sabresd board and the flash (emmc).
I noticed that there is boot0 and boot1 created for that chip.
What is the reason for this 2 boot "devices" and where in the code can I change that.
I notice that (I have to confirm this tomorrow) I portioning the Linux part to a few GB, but when I reboot next time it is only around 300Mb.
Thanks,
Niklas
1.
Please let me know what do You mean under "boot0" and "boot1" ?
Are there BOOT_MODE[1:0] pins of the i.MX6 ?
If so, these pins just define boot modes, described in section 8.2.1 (Boot mode pin settings) of i.MX6 Reference
Manual (IMX6DQRM, Rev. 1, 04/2013). Boot devices are configured using so called BOOT_CFG fuses / pins.
Please refer to chapter 8 of the RM for more details.
2.
As for Linux partition of 300 MB, please check ucl2.xml file in "<MFG_dir>\Profiles\MX6Q Linux Update\OS Firmware\"
if the MFG is applied to deploy the images. In ucl2.xml file we can see details about deploying process. Perhaps
it makes sense to check script "mksdcard.sh.tar", which provides instructions for sfdisk.
Hi Yuri.
When I look in the /dev (plus during boot up) there is mmcbl1boot0 and mmcbl1boot1 (which is for the flash).
Not sure why this one is created and where in the code (I haven't had time to investigate this).
I also tried to format the Linux partition in my flash (mmcblk1p2) with mkfs, but get following errors:
root@imx6qsabresd:~# mkfs.ext3 /dev/mmcblk1p2
-sh: mkfs.ext3: command not found
root@imx6qsabresd:~# mkfs -t ext3 /dev/mmcblk1p2
mkfs.ext3: No such file or directory
Thanks,
Niklas
Hello Niklas,
were you able to solve the mkfs.ext3 : command not found issue?
I am stuck at the same point right now.
thanks,
nishad
Hi nishad.
I recall I manually compiled.installed that package (E2fsprogs) on the board. I haven't played around with it since then.
But I need to do that soon again, for our custom board. Then I'll look in to fixing the recipes, so I don't manually have to install it.
Right now I have problem that I don't have gcc in my image (not sure if you have had that problem).
Before I could include tools-sdk in my build, but no it doesn't compile if I include that.
Regards,
Niklas
Hello Niklas,
Thanks for the prompt reply,
I included the e2fsprogs and I was able to acquire all the files for forming .ext3 and .ext4 partiotons. I partitioned the eMMC and stored my rootfs in it.
I have attached the console log of my rootfs booting from eMMC.
Thanks again,
nishad
From: Niklas Molin
Sent: Friday, March 21, 2014 7:18 PM
To: nishad nishad
Subject: Re: - sabresd flash
sabresd flash
reply from Niklas Molin in i.MX Community - View the full discussion
Hi nishad.
Did you manually compile the e2fsprogs or include it in your image build?
When I include it in my image build, it won't show up in my rootfs (might
be some other recipes I include that causing the problem.
Thanks,
Niklas
On Sat, Mar 22, 2014 at 12:43 AM, nishad nishad <
Hi Niklas,
I included it in my image build. This is the procedure that I followed,
I am using the L3.0.35_4.1.0 BSP.
U-boot : 2008:09
mx6q_sabreauto_weimnor
Minimum profile.
I included just the one e2fsprogs package in addition to the default minimum profile packages and built the image.
Loaded the images in the NOR flash,
Once I booted my system from the parallel nor, it showed up in my rootfs.
yes, there might be some conflicting packages.
May be a fresh LTIB build with just the e2fsprogs package and then adding the other packages serially would help you find out the conflicting package.
hope it helps.
thanks,
nishad
From: Niklas Molin
Sent: Sunday, March 23, 2014 3:00 AM
To: nishad nishad
Subject: Re: - sabresd flash
sabresd flash
reply from Niklas Molin in i.MX Community - View the full discussion
Hi nishad.kamdar@bitmapper.com.
I'm using Yocto, so there might be some difference.
But I haven't had time to look into this lately.
I'll dig into this when I'm starting with the eMMC again.
Thanks,
Niklas