[Buildroot] Help for another newbie, AT91sam9x25 incorrect defconfig or incorrect rootfs.ubi

[Buildroot] Help for another newbie, AT91sam9x25 incorrect defconfig or incorrect rootfs.ubi

[Ted Salazar]

Hi All,

I'm designing a board that is based on the sam9x25-ek but I am using the ek
until my board is assembled. I installed Code Sourcery 2014 and have built
the following:

1. Built the At91Bootstrap Ver 3.7.2:
location: tsalazar at Ubuntu14-64:~/at91bootstrap/binaries/
Output file: at91sam9x5ek-nandflashboot-uboot-3.7.2.bin

2. Built Uboot ver 2015.01:
location: tsalazar at Ubuntu14-64:~/u-boot-at91/
Output file: u-boot.bin

3. Built the Kernel ver 3.6.9  (I plan to upgrade to 3.18 but I'm trying to
duplicate a working demo first)
location: tsalazar at Ubuntu14-64:~/linux-at91/arch/arm/boot/
Output file: at91sam9x25ek.dtb  
location: tsalazar at Ubuntu14-64:~/linux-at91/arch/arm/boot/
Output file: zImage

4. Built buildroot-at91 ver 2014.05 ( This is where I have all my problems)

https://github.com/linux4sam/buildroot-at91/tree/buildroot-2014.05-at91/configs

I can't find a at91sam9x25ek_defconfig file to use. I was told that any
at91sam9 would work for my file system so I tried using
at91sam9263ek_defconfig.

at91rm9200df_defconfig	configs: update boards to u-boot custom version
option	2 years ago
at91sam9260dfc_defconfig	at91sam9260dfc_defconfig: fix linux defconfig name
2 years ago
at91sam9260eknf_defconfig	defconfigs: add the _AT_LEAST_X_Y headers options
a year ago
at91sam9261ek_defconfig	at91sam9261ek_defconfig: fix linux defconfig name	2
years ago
at91sam9263ek_defconfig	at91sam92*: update defconfigs to use latest u-boot	3
years ago
at91sam9g20dfc_defconfig	defconfigs: add the _AT_LEAST_X_Y headers options	a
year ago
at91sam9g45m10ek_defconfig	at91sam9m10g45ek: add gst-launch preview support

After I do the following commands I get a .ubi file

$ make at91sam9263ek_defconfig
$ make menuconfig
$ make

location: tsalazar at Ubuntu14-64:~/buildroot-at91/output/images
Output file: rootfs.ubi

When I replace all the files in Atmel's NandFlash Demo script with all of
these output files the debug hangs here at the rootfs. 
 
UBIFS error (pid 1): ubifs_mount: cannot open "ubi0:rootfs", error -19
VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0): error -19
Please append a correct "root=" boot option; here are the available
partitions:
1f00             256 mtdblock0  (driver?)
1f01             512 mtdblock1  (driver?)
1f02             256 mtdblock2  (driver?)
1f03             256 mtdblock3  (driver?)
1f04             256 mtdblock4  (driver?)
1f05             512 mtdblock5  (driver?)
1f06            6144 mtdblock6  (driver?)
1f07          253952 mtdblock7  (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)

Q1) Does someone know where I can get an at91sam9x25ek_defconfig file for
BuildRoot-at91 Ver 2014.05?

Q2)Maybe even more importantly, I know I need to understand how much each
bootloader stage and the file system uses up the in NandFlash. What is best
practices way of setting up the memory map? I assume this is done at every
build stage in menuconfig?

I grabbed this from the debug on boot but I am just using defaults at this
point and need to know where I set the memory map and best practices and
what I should watch out for.

Creating 8 MTD partitions on "atmel_nand":
0x000000000000-0x000000040000 : "bootstrap"
0x000000040000-0x0000000c0000 : "uboot"
0x0000000c0000-0x000000100000 : "env"
0x000000100000-0x000000140000 : "env_redundant"
0x000000140000-0x000000180000 : "spare"
0x000000180000-0x000000200000 : "dtb"
0x000000200000-0x000000800000 : "kernel"
0x000000800000-0x000010000000 : "rootfs"

I'm going to call it day and try to learn more about ubi tomorrow.

Any words of wisdom even if it is a link to must have reading is welcome.

Thanks,
Ted Salazar

PS: I am also not sure what the env and env_redundant is for. If someone is
familiar with that terminology please tell.



--
View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/Help-for-another-newbie-AT91sam9x25-incorrect-defconfig-or-incorrect-rootfs-ubi-tp101939.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.

[Buildroot] Help for another newbie, AT91sam9x25 incorrect defconfig or incorrect rootfs.ubi

[Thomas Petazzoni]

Dear Ted Salazar,

On Sun, 24 May 2015 00:26:27 -0700 (PDT), Ted Salazar wrote:

> 1. Built the At91Bootstrap Ver 3.7.2:
> location: tsalazar at Ubuntu14-64:~/at91bootstrap/binaries/
> Output file: at91sam9x5ek-nandflashboot-uboot-3.7.2.bin
> 
> 2. Built Uboot ver 2015.01:
> location: tsalazar at Ubuntu14-64:~/u-boot-at91/
> Output file: u-boot.bin
> 
> 3. Built the Kernel ver 3.6.9  (I plan to upgrade to 3.18 but I'm trying to
> duplicate a working demo first)
> location: tsalazar at Ubuntu14-64:~/linux-at91/arch/arm/boot/
> Output file: at91sam9x25ek.dtb  
> location: tsalazar at Ubuntu14-64:~/linux-at91/arch/arm/boot/
> Output file: zImage

Why do you build AT91Bootstrap, U-Boot and the kernel? Buildroot will
build them for you, no need to build these manually.

> 4. Built buildroot-at91 ver 2014.05 ( This is where I have all my problems)
> 
> https://github.com/linux4sam/buildroot-at91/tree/buildroot-2014.05-at91/configs

This is the Atmel fork of Buildroot. You're contacting the official
Buildroot mailing list, we only support the mainline Buildroot.

You should rather try the updated Atmel defconfigs recently posted by
Alexandre Belloni (they are only available in the Buildroot patchwork
for the moment, since they haven't been applied yet).

> Q1) Does someone know where I can get an at91sam9x25ek_defconfig file for
> BuildRoot-at91 Ver 2014.05?

No, because you're talking about an Atmel fork of Buildroot, and this
mailing list is only supporting the official Buildrot.

You should apply the patch http://patchwork.ozlabs.org/patch/473928/ on
the mainline Buildroot and use the at91sam9x5ek_defconfig. Also, make
sure to apply http://patchwork.ozlabs.org/patch/473935/ and read the
readme.txt file. These patches should be applied to the next Buildroot
version.

Best regards,

Thomas Petazzoni
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] Help for another newbie, AT91sam9x25 incorrect defconfig or incorrect rootfs.ubi

[Ted Salazar]

Hi Thomas,

Thanks for your responses to my Question 1. My responses are below [TS]

From: Thomas Petazzoni-2 [via Buildroot (busybox)] [mailto:ml-node+s2317881n101941h89 at n4.nabble.com]
Sent: Sunday, May 24, 2015 3:45 AM
To: Ted Salazar
Subject: Re: Help for another newbie, AT91sam9x25 incorrect defconfig or incorrect rootfs.ubi

Dear Ted Salazar,

On Sun, 24 May 2015 00:26:27 -0700 (PDT), Ted Salazar wrote:

> 1. Built the At91Bootstrap Ver 3.7.2:
> location: tsalazar at Ubuntu14-64:~/at91bootstrap/binaries/
> Output file: at91sam9x5ek-nandflashboot-uboot-3.7.2.bin
>
> 2. Built Uboot ver 2015.01:
> location: tsalazar at Ubuntu14-64:~/u-boot-at91/
> Output file: u-boot.bin
>
> 3. Built the Kernel ver 3.6.9  (I plan to upgrade to 3.18 but I'm trying to
> duplicate a working demo first)
> location: tsalazar at Ubuntu14-64:~/linux-at91/arch/arm/boot/
> Output file: at91sam9x25ek.dtb
> location: tsalazar at Ubuntu14-64:~/linux-at91/arch/arm/boot/
> Output file: zImage

Why do you build AT91Bootstrap, U-Boot and the kernel? Buildroot will
build them for you, no need to build these manually.

[TS: I am open to using the mainline BuildRoot but I just got started with the Atmel flow because it was recommended by Atmel for their processor and they have a working Flash Demo for the EK my board will be based on so I was trying to reproduce that Flash Demo. ]

> 4. Built buildroot-at91 ver 2014.05 ( This is where I have all my problems)
>
> https://github.com/linux4sam/buildroot-at91/tree/buildroot-2014.05-at91/configs

This is the Atmel fork of Buildroot. You're contacting the official
Buildroot mailing list, we only support the mainline Buildroot.

You should rather try the updated Atmel defconfigs recently posted by
Alexandre Belloni (they are only available in the Buildroot patchwork
for the moment, since they haven't been applied yet).

[TS: Yes I was aware of Alexandre's patches but several things were not clear enough to me to be able to use it. Sorry this is basic to you but not to me.

1.       Who  runs the at91.com/Linux4Sam website? I thought this was an Atmel run website? If so and you only support mainline BuildRoot then why does Alexandre's sam9x5ek patches contain Linux4sam URLs (ie URL=https://github.com/linux4sam/linux-at91.git and URL="git://github.com/linux4sam/u-boot-at91.git" ) shown here http://patchwork.ozlabs.org/patch/473928/

2.       The Atmel flow that I have been using, requires various at91sam9x5ek defconfig files. For example,  to build

AT91Bootstrap => at91sam9x5eknf_uboot_defconfig is required

Uboot => at91sam9x5ek_nandflash_defconfig is required

Kernel => at91_dt_defconfig is required

File System using AtmelBuildRoot => at91sam9x25ek_defconfig (which does not exist and what I was looking for but I never understood how to get Alexandre's patch until you sent me the link http://patchwork.ozlabs.org/patch/473928/ ) I never saw a way to download this from the BuildRoot mailing list email. Thank you for sending the link.

3.       Does Alexandre's patch create all of the required at91sam9x5 defconfig files needed in order to build the AT91Bootstrap, uboot, Kernel and .ubifs filesystem too?

4.       OK, if Alexandre's patch does not work on Atmel's forked BuildRoot then I will try using mainline BuildRoot. In fact, I'll probably try both BuildRoot versions no matter what. I'll read the manual at http://buildroot.uclibc.org/downloads/manual/manual.html

> Q1) Does someone know where I can get an at91sam9x25ek_defconfig file for
> BuildRoot-at91 Ver 2014.05?

No, because you're talking about an Atmel fork of Buildroot, and this
mailing list is only supporting the official Buildrot.

You should apply the patch http://patchwork.ozlabs.org/patch/473928/ on
the mainline Buildroot and use the at91sam9x5ek_defconfig. Also, make
sure to apply http://patchwork.ozlabs.org/patch/473935/ and read the
readme.txt file. These patches should be applied to the next Buildroot
version.

[TS: Thank you]

Best regards,

Thomas Petazzoni
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
_______________________________________________
buildroot mailing list
[hidden email]</user/SendEmail.jtp?type=node&node=101941&i=0>
http://lists.busybox.net/mailman/listinfo/buildroot

________________________________
If you reply to this email, your message will be added to the discussion below:
http://buildroot-busybox.2317881.n4.nabble.com/Help-for-another-newbie-AT91sam9x25-incorrect-defconfig-or-incorrect-rootfs-ubi-tp101939p101941.html
To unsubscribe from Help for another newbie, AT91sam9x25 incorrect defconfig or incorrect rootfs.ubi, click here<http://buildroot-busybox.2317881.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=101939&code=dGVkLnNhbGF6YXJAbWF4aW1pbnRlZ3JhdGVkLmNvbXwxMDE5Mzl8OTI4OTc3Mjk=>.
NAML<http://buildroot-busybox.2317881.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>




--
View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/Help-for-another-newbie-AT91sam9x25-incorrect-defconfig-or-incorrect-rootfs-ubi-tp101939p101953.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150524/48eb5dfd/attachment.html>

[Buildroot] Help for another newbie, AT91sam9x25 incorrect defconfig or incorrect rootfs.ubi

[Alexandre Belloni]

Hi,

On 24/05/2015 at 19:06:36 -0700, Ted Salazar wrote :
> 
> [TS: Yes I was aware of Alexandre's patches but several things were not clear enough to me to be able to use it. Sorry this is basic to you but not to me.
> 
> 1.       Who  runs the at91.com/Linux4Sam website? I thought this was an Atmel run website? If so and you only support mainline BuildRoot then why does Alexandre's sam9x5ek patches contain Linux4sam URLs (ie URL=https://github.com/linux4sam/linux-at91.git and URL="git://github.com/linux4sam/u-boot-at91.git" ) shown here http://patchwork.ozlabs.org/patch/473928/
> 

Atmel is. I'm using their version of the kernel, u-boot and
at91bootstrap because they are maintaining stble versions of each.

> 3.       Does Alexandre's patch create all of the required at91sam9x5 defconfig files needed in order to build the AT91Bootstrap, uboot, Kernel and .ubifs filesystem too?
> 

Yes.

> 4.       OK, if Alexandre's patch does not work on Atmel's forked BuildRoot then I will try using mainline BuildRoot. In fact, I'll probably try both BuildRoot versions no matter what. I'll read the manual at http://buildroot.uclibc.org/downloads/manual/manual.html
> 

It will also work on buildroot-at91 but this doesn't make any sense to try that. As it is older and is actually outdated.


-- 
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] Help for another newbie, AT91sam9x25 incorrect defconfig or incorrect rootfs.ubi

[Ted Salazar]

Hi Alexandre,

Thanks again for your response. I think mainline BuildRoot is the way to go.

Just two quick questions on the commands to apply your patch...from BuildRoot documentation.

$ git checkout -b <test-branch-name>
$ wget -O - <mbox-url> | git am

Q1: Does <test-branch-name> = http://git.buildroot.net/buildroot/tag/?id=2015.02 ?
Q2: Does <mbox-url> = http://patchwork.ozlabs.org/patch/473928/mbox/ ?

Thanks
Ted

21.3.1. Applying Patches from Patchwork
The main use of Buildroot's Patchwork website for a developer is for pulling in patches into their local git repository for testing purposes.

When browsing patches in the patchwork management interface, an mbox link is provided at the top of the page. Copy this link address and run the following commands:

$ git checkout -b <test-branch-name>
$ wget -O - <mbox-url> | git am



-----Original Message-----
From: Alexandre Belloni [mailto:alexandre.belloni at free-electrons.com] 
Sent: Monday, May 25, 2015 7:38 AM
To: Ted Salazar
Cc: buildroot at busybox.net
Subject: Re: [Buildroot] Help for another newbie, AT91sam9x25 incorrect defconfig or incorrect rootfs.ubi

Hi,

On 24/05/2015 at 19:06:36 -0700, Ted Salazar wrote :
> 
> [TS: Yes I was aware of Alexandre's patches but several things were not clear enough to me to be able to use it. Sorry this is basic to you but not to me.
> 
> 1.       Who  runs the at91.com/Linux4Sam website? I thought this was an Atmel run website? If so and you only support mainline BuildRoot then why does Alexandre's sam9x5ek patches contain Linux4sam URLs (ie URL=https://github.com/linux4sam/linux-at91.git and URL="git://github.com/linux4sam/u-boot-at91.git" ) shown here http://patchwork.ozlabs.org/patch/473928/
> 

Atmel is. I'm using their version of the kernel, u-boot and at91bootstrap because they are maintaining stble versions of each.

> 3.       Does Alexandre's patch create all of the required at91sam9x5 defconfig files needed in order to build the AT91Bootstrap, uboot, Kernel and .ubifs filesystem too?
> 

Yes.

> 4.       OK, if Alexandre's patch does not work on Atmel's forked BuildRoot then I will try using mainline BuildRoot. In fact, I'll probably try both BuildRoot versions no matter what. I'll read the manual at http://buildroot.uclibc.org/downloads/manual/manual.html
> 

It will also work on buildroot-at91 but this doesn't make any sense to try that. As it is older and is actually outdated.


--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering http://free-electrons.com

[Buildroot] Newbie help, AT91sam9x25 patch Installation Questions

[Ted Salazar]

To all you patch experts...Just curious why the BuildRoot manual checksout a branch to patch instead a tag? The newest branch is 2013.xx but the newest stable tag is 2015.02, which is what I want. Also, don't I need to add a patch command at the end of those two commands as well? Something like $ patch < hello.patch ?

21.3.1. Applying Patches from Patchwork
The main use of Buildroot?s Patchwork website for a developer is for pulling in patches into their local git repository for testing purposes.

When browsing patches in the patchwork management interface, an mbox link is provided@the top of the page. Copy this link address and run the following commands:

$ git checkout -b <test-branch-name>
$ wget -O - <mbox-url> | git am

I hope to get your life saving patches installed tomorrow.

Thank you,
Ted
________________________________________
From: Ted Salazar
Sent: Monday, May 25, 2015 2:18 PM
To: Alexandre Belloni
Cc: buildroot at busybox.net
Subject: RE: [Buildroot] Help for another newbie, AT91sam9x25 incorrect defconfig or incorrect rootfs.ubi

Hi Alexandre,

Thanks again for your response. I think mainline BuildRoot is the way to go.

Just two quick questions on the commands to apply your patch...from BuildRoot documentation.

$ git checkout -b <test-branch-name>
$ wget -O - <mbox-url> | git am

Q1: Does <test-branch-name> = http://git.buildroot.net/buildroot/tag/?id=2015.02 ?
Q2: Does <mbox-url> = http://patchwork.ozlabs.org/patch/473928/mbox/ ?

Thanks
Ted

21.3.1. Applying Patches from Patchwork
The main use of Buildroot?s Patchwork website for a developer is for pulling in patches into their local git repository for testing purposes.

When browsing patches in the patchwork management interface, an mbox link is provided at the top of the page. Copy this link address and run the following commands:

$ git checkout -b <test-branch-name>
$ wget -O - <mbox-url> | git am



-----Original Message-----
From: Alexandre Belloni [mailto:alexandre.belloni at free-electrons.com]
Sent: Monday, May 25, 2015 7:38 AM
To: Ted Salazar
Cc: buildroot at busybox.net
Subject: Re: [Buildroot] Help for another newbie, AT91sam9x25 incorrect defconfig or incorrect rootfs.ubi

Hi,

On 24/05/2015 at 19:06:36 -0700, Ted Salazar wrote :
>
> [TS: Yes I was aware of Alexandre's patches but several things were not clear enough to me to be able to use it. Sorry this is basic to you but not to me.
>
> 1.       Who  runs the at91.com/Linux4Sam website? I thought this was an Atmel run website? If so and you only support mainline BuildRoot then why does Alexandre's sam9x5ek patches contain Linux4sam URLs (ie URL=https://github.com/linux4sam/linux-at91.git and URL="git://github.com/linux4sam/u-boot-at91.git" ) shown here http://patchwork.ozlabs.org/patch/473928/
>

Atmel is. I'm using their version of the kernel, u-boot and at91bootstrap because they are maintaining stble versions of each.

> 3.       Does Alexandre's patch create all of the required at91sam9x5 defconfig files needed in order to build the AT91Bootstrap, uboot, Kernel and .ubifs filesystem too?
>

Yes.

> 4.       OK, if Alexandre's patch does not work on Atmel's forked BuildRoot then I will try using mainline BuildRoot. In fact, I'll probably try both BuildRoot versions no matter what. I'll read the manual at http://buildroot.uclibc.org/downloads/manual/manual.html
>

It will also work on buildroot-at91 but this doesn't make any sense to try that. As it is older and is actually outdated.


--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering http://free-electrons.com

[Buildroot] Newbie help, AT91sam9x25 patch Installation Questions

[Alexandre Belloni]

Hi,

On 26/05/2015 at 23:58:17 -0700, Ted Salazar wrote :
> To all you patch experts...Just curious why the BuildRoot manual checksout a branch to patch instead a tag? The newest branch is 2013.xx but the newest stable tag is 2015.02, which is what I want. Also, don't I need to add a patch command at the end of those two commands as well? Something like $ patch < hello.patch ?
> 
> 21.3.1. Applying Patches from Patchwork
> The main use of Buildroot?s Patchwork website for a developer is for pulling in patches into their local git repository for testing purposes.
> 
> When browsing patches in the patchwork management interface, an mbox link is provided at the top of the page. Copy this link address and run the following commands:
> 
> $ git checkout -b <test-branch-name>
> $ wget -O - <mbox-url> | git am
> 
> I hope to get your life saving patches installed tomorrow.
> 

Use:

git clone git://git.buildroot.net/buildroot
git checkout 2015.02
wget -O - http://patchwork.ozlabs.org/patch/473928/mbox/ | git am
wget -O - http://patchwork.ozlabs.org/patch/473935/mbox/ | git am
make at91sam9x5ek_defconfig
make

Those are step by step instructions but like I already said, you should
probably read more documentation or get a training.

-- 
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com