* [Buildroot] I really need some help
@ 2008-03-05 22:02 Tim Barr
2008-03-06 7:51 ` Ulf Samuelsson
0 siblings, 1 reply; 4+ messages in thread
From: Tim Barr @ 2008-03-05 22:02 UTC (permalink / raw)
To: buildroot
I have been trying for the past 2+ months to successfully complete a
buildroot session for a AT91SAM9260EK. I first installed buildroot via
svn. Then I then did a "make at91sam9260pf_defconfig" to get baseline
config files. Then I ran a "make configured" in order to get a baseline
codeset. I ran "make menuconfig" in the kernel directory in order to
update the kernel config from what defconfig installed, otherwise I kept
getting prompted about missing config info during the make. The only
change I made to the kernel config was to add USB ACM support so I could
talk to a USB wireless module. I have tried both 2.6.22.1 and 2.6.22.10
kernels.
I have been able to figure out workarounds for some of the errors I have
gotten, either manually downloading source files that buildroot could
not find or creating directories that buildroot could not find or would
not create itself. Now I am getting an error about "No mail command
specified". Log file info follows:
# Use fakeroot to pretend all target binaries are owned by root
rm -f
/home/falingtrea/buildroot/project_build_arm_wchar/SuperModem-2.6.22.1/_
fakeroot.rootfs.arm-20080305.ext2
touch
/home/falingtrea/buildroot/project_build_arm_wchar/SuperModem-2.6.22.1/.
fakeroot.00000
cat
/home/falingtrea/buildroot/project_build_arm_wchar/SuperModem-2.6.22.1/.
fakeroot* >
/home/falingtrea/buildroot/project_build_arm_wchar/SuperModem-2.6.22.1/_
fakeroot.rootfs.arm-20080305.ext2
echo "chown -R 0:0
/home/falingtrea/buildroot/project_build_arm_wchar/SuperModem-2.6.22.1/r
oot" >>
/home/falingtrea/buildroot/project_build_arm_wchar/SuperModem-2.6.22.1/_
fakeroot.rootfs.arm-20080305.ext2
# Use fakeroot to pretend to create all needed device nodes
echo
"/home/falingtrea/buildroot/build_arm_wchar/staging_dir/bin/makedevs -d
target/device/Atmel/root/device_table.txt
/home/falingtrea/buildroot/project_build_arm_wchar/SuperModem-2.6.22.1/r
oot" \
>>
/home/falingtrea/buildroot/project_build_arm_wchar/SuperModem-2.6.22.1/_
fakeroot.rootfs.arm-20080305.ext2
# Use fakeroot so genext2fs believes the previous fakery
GENEXT2_REALSIZE=`LC_ALL=C du -s -c -k
/home/falingtrea/buildroot/project_build_arm_wchar/SuperModem-2.6.22.1/r
oot | grep total | sed -e "s/total//"`; \
GENEXT2_ADDTOROOTSIZE=`if [ $GENEXT2_REALSIZE -ge 20000 ]; then echo
16384; else echo 2400; fi`; \
GENEXT2_SIZE=`expr $GENEXT2_REALSIZE + $GENEXT2_ADDTOROOTSIZE`; \
GENEXT2_ADDTOINODESIZE=`find
/home/falingtrea/buildroot/project_build_arm_wchar/SuperModem-2.6.22.1/r
oot | wc -l`; \
GENEXT2_INODES=`expr $GENEXT2_ADDTOINODESIZE + 400`; \
set -x; \
echo "/home/falingtrea/buildroot/build_arm_wchar/genext2fs-1.4/genext2fs
-b $GENEXT2_SIZE " \
"-N $GENEXT2_INODES -d
/home/falingtrea/buildroot/project_build_arm_wchar/SuperModem-2.6.22.1/r
oot " \
" -U -m 0
/home/falingtrea/buildroot/binaries/SuperModem-2.6.22.1/rootfs.arm-20080
305.ext2" >>
/home/falingtrea/buildroot/project_build_arm_wchar/SuperModem-2.6.22.1/_
fakeroot.rootfs.arm-20080305.ext2
+ echo
/home/falingtrea/buildroot/build_arm_wchar/genext2fs-1.4/genext2fs -b
46612 -N 1479 -d
/home/falingtrea/buildroot/project_build_arm_wchar/SuperModem-2.6.22.1/r
oot -U -m 0
/home/falingtrea/buildroot/binaries/SuperModem-2.6.22.1/rootfs.arm-20080
305.ext2
chmod a+x
/home/falingtrea/buildroot/project_build_arm_wchar/SuperModem-2.6.22.1/_
fakeroot.rootfs.arm-20080305.ext2
/home/falingtrea/buildroot/build_arm_wchar/staging_dir/usr/bin/fakeroot
--
/home/falingtrea/buildroot/project_build_arm_wchar/SuperModem-2.6.22.1/_
fakeroot.rootfs.arm-20080305.ext2
make[1]: Entering directory
`/home/falingtrea/buildroot/build_arm_wchar/at-3.1.10'
/home/falingtrea/buildroot/build_arm_wchar/staging_dir/usr/bin/arm-linux
-uclibc-gcc -Os -pipe
-I/home/falingtrea/buildroot/build_arm_wchar/staging_dir/usr/include
-I/home/falingtrea/buildroot/build_arm_wchar/staging_dir/include
--sysroot=/home/falingtrea/buildroot/build_arm_wchar/staging_dir/
-isysroot /home/falingtrea/buildroot/build_arm_wchar/staging_dir -c -O2
-g -Wall -DHAVE_CONFIG_H -DVERSION=\"3.1.9\" -DETCDIR=\"/etc\"
-DLOADAVG_MX=0.8 -DDAEMON_USERNAME=\"root\" -DDAEMON_GROUPNAME=\"root\"
-DLFILE=\"/var/lib/atjobs/.SEQ\" -Wall atd.c
atd.c:498:2: error: #error "No mail command specified."
make[1]: *** [atd.o] Error 1
make[1]: Leaving directory
`/home/falingtrea/buildroot/build_arm_wchar/at-3.1.10'
rootdir=/home/falingtrea/buildroot/project_build_arm_wchar/SuperModem-2.
6.22.1/root
table='target/device/Atmel/root/device_table.txt'
makedevs: line 42: regular file
'/home/falingtrea/buildroot/project_build_arm_wchar/SuperModem-2.6.22.1/
root/etc/shadow' does not exist: No such file or directory
makedevs: line 43: regular file
'/home/falingtrea/buildroot/project_build_arm_wchar/SuperModem-2.6.22.1/
root/etc/passwd' does not exist: No such file or directory
makedevs: line 48: regular file
'/home/falingtrea/buildroot/project_build_arm_wchar/SuperModem-2.6.22.1/
root/usr/share/udhcpc/default.script' does not exist: No such file or
directory
-rw-r--r-- 1 falingtrea falingtrea 47730688 2008-03-05 12:12
/home/falingtrea/buildroot/binaries/SuperModem-2.6.22.1/rootfs.arm-20080
305.ext2
rm -f
/home/falingtrea/buildroot/project_build_arm_wchar/SuperModem-2.6.22.1/.
fakeroot*
Timothy Barr
Hardware Development Engineer
for Multi-Tech Systems, Inc.
<mailto:tbarr@multitech.com> tbarr at multitech.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20080305/d3a07c65/attachment.htm
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Buildroot] I really need some help
2008-03-05 22:02 [Buildroot] I really need some help Tim Barr
@ 2008-03-06 7:51 ` Ulf Samuelsson
0 siblings, 0 replies; 4+ messages in thread
From: Ulf Samuelsson @ 2008-03-06 7:51 UTC (permalink / raw)
To: buildroot
> I have been trying for the past 2+ months to successfully complete a
> buildroot session for a AT91SAM9260EK. I first installed buildroot via
> svn. Then I then did a "make at91sam9260pf_defconfig" to get baseline
> config files.
The "pf" is for parallel flash and will not work on the EK since it does not have any parallel flash.
You should use "make at91sam9260dfc_defconfig" and a dataflash card for this board.
If you want to use the internal dataflash, then you need to fix U-Boot and at91bootstrap,
but it might be easier to download the binaries from www.linux4sam.org
Is "SuperModem-2.6.22.1" your project name?
For: "atd.c:498:2: error: #error "No mail command specified." error message:
If you do not need the "at" package, you can just disable it in menuconfig.
If you need it, then you need to look at "atd.c" somewhere
in the build_arm_wchar/at-3.1.10 to find out why you get the error message.
You should also ensure that the files
/etc/shadow
/etc/passwd
/usr/share/udhcpc/default.script
are in your root file system.
> Then I ran a "make configured" in order to get a baseline
> codeset. I ran "make menuconfig" in the kernel directory in order to
> update the kernel config from what defconfig installed, otherwise I kept
> getting prompted about missing config info during the make. The only
> change I made to the kernel config was to add USB ACM support so I could
> talk to a USB wireless module. I have tried both 2.6.22.1 and 2.6.22.10
> kernels.
Best Regards
Ulf Samuelsson ulf at atmel.com
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Buildroot] I really need some help
@ 2008-03-06 14:14 Tim Barr
2008-03-06 16:28 ` Ulf Samuelsson
0 siblings, 1 reply; 4+ messages in thread
From: Tim Barr @ 2008-03-06 14:14 UTC (permalink / raw)
To: buildroot
> > I have been trying for the past 2+ months to successfully
> complete a
> > buildroot session for a AT91SAM9260EK. I first installed
> buildroot via
> > svn. Then I then did a "make at91sam9260pf_defconfig" to
> get baseline
> > config files.
>
> The "pf" is for parallel flash and will not work on the EK
> since it does not have any parallel flash. You should use
> "make at91sam9260dfc_defconfig" and a dataflash card for this board.
>
> If you want to use the internal dataflash, then you need to
> fix U-Boot and at91bootstrap, but it might be easier to
> download the binaries from www.linux4sam.org
Right now I have been working with the free BSP package from Timesys and
the binaries from linux4sam.
Firstly, I guess I don't understand what is referred to by "parallel
flash". Is the NAND flash on the EK board not considered parallel flash?
Or is the issue because the 9260 has a bug that won't allow it to boot
from NAND Flash. We are planning to switch development efforts to the
9G20 when the EK is available in April, and that part supposedly has the
NAND boot issue fixed.
Secondly, considering what you are saying about the internal dataflash,
can I assume that the Uboot and bootstrap files I got from both Timesys
and linux4sam have the internal dataflash fix, since I am able to boot
the boards without a dataflash card?
And thirdly, which binaries are stored on the dataflash and which can be
on the NAND Flash of the 9260EK board? Is the linux kernel stored on the
dataflash or the NAND flash typically?
>
> Is "SuperModem-2.6.22.1" your project name?
Yes, name with kernel version
>
>
> For: "atd.c:498:2: error: #error "No mail command specified."
> error message:
>
> If you do not need the "at" package, you can just disable it
> in menuconfig. If you need it, then you need to look at
> "atd.c" somewhere in the build_arm_wchar/at-3.1.10 to find
> out why you get the error message.
What is this AT package? Do I disable it in the busy box or the kernel
config? I am an kernel building newbie so I am not familiar with all the
options. I really need a "Building Linux kernels for Dummies" book. :)
>
> Best Regards
> Ulf Samuelsson ulf at atmel.com
>
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Buildroot] I really need some help
2008-03-06 14:14 Tim Barr
@ 2008-03-06 16:28 ` Ulf Samuelsson
0 siblings, 0 replies; 4+ messages in thread
From: Ulf Samuelsson @ 2008-03-06 16:28 UTC (permalink / raw)
To: buildroot
>> > I have been trying for the past 2+ months to successfully
>> complete a
>> > buildroot session for a AT91SAM9260EK. I first installed
>> buildroot via
>> > svn. Then I then did a "make at91sam9260pf_defconfig" to
>> get baseline
>> > config files.
>>
>> The "pf" is for parallel flash and will not work on the EK
>> since it does not have any parallel flash. You should use
>> "make at91sam9260dfc_defconfig" and a dataflash card for this board.
>>
>> If you want to use the internal dataflash, then you need to
>> fix U-Boot and at91bootstrap, but it might be easier to
>> download the binaries from www.linux4sam.org
>
> Right now I have been working with the free BSP package from Timesys and
> the binaries from linux4sam.
>
> Firstly, I guess I don't understand what is referred to by "parallel
> flash".
In this context, it is a non-multiplexed random access flash memory
with address bus, databus, chip select, read and write strobe.
>Is the NAND flash on the EK board not considered parallel flash?
It is a parallel flash, but it is usually referred to as a NAND flash,
implying an 8/16 bit databus and only 1-2 address pins.
If you want to be strict then you can say that a parallel flash
memory is a RAM, because RAM = Random Access Memory.
What is usually called a RAM, is actually a RWM (Read/Write Memory)
The pundit will claim that you can write to a flash as well,but
it is not so easy to do that as it is with a normal RAM.
> Or is the issue because the 9260 has a bug that won't allow it to boot
> from NAND Flash. We are planning to switch development efforts to the
> 9G20 when the EK is available in April, and that part supposedly has the
> NAND boot issue fixed.
There is no prepared defconfig for NAND flash only.
The difference is at91bootstrap and U-boot.
You will be able to use buildroot to build the linux and the rootfs in any case.
> Secondly, considering what you are saying about the internal dataflash,
> can I assume that the Uboot and bootstrap files I got from both Timesys
> and linux4sam have the internal dataflash fix, since I am able to boot
> the boards without a dataflash card?
Yes, the buildroot was created because Atmel poorly supports
the external dataflashcard.
You can use the timesys at91bootstrap/u-boot if you want to use
the internal dataflash, but I think that you will find that during
development, it is much nicer to use the dataflash card.
>
> And thirdly, which binaries are stored on the dataflash and which can be
> on the NAND Flash of the 9260EK board? Is the linux kernel stored on the
> dataflash or the NAND flash typically?
>
The AT91 buildroot pretty much ignores the NAND flash.
I see there is a lot of activity on the u-boot mailing list about
this and that feature of NAND flash which has issues in u-boot.
Again, reconfiguring to not build the boot programs
will allow you to complete the build.
>>
>> Is "SuperModem-2.6.22.1" your project name?
>
> Yes, name with kernel version
>
>>
>>
>> For: "atd.c:498:2: error: #error "No mail command specified."
>> error message:
>>
>> If you do not need the "at" package, you can just disable it
>> in menuconfig. If you need it, then you need to look at
>> "atd.c" somewhere in the build_arm_wchar/at-3.1.10 to find
>> out why you get the error message.
>
> What is this AT package? Do I disable it in the busy box or the kernel
> config? I am an kernel building newbie so I am not familiar with all the
> options. I really need a "Building Linux kernels for Dummies" book. :)
>
It is a package, and you disable it by "make menuconfig".
It is not part of the Linux kernel.
Best Regards
Ulf Samuelsson
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2008-03-06 16:28 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-03-05 22:02 [Buildroot] I really need some help Tim Barr
2008-03-06 7:51 ` Ulf Samuelsson
-- strict thread matches above, loose matches on Subject: below --
2008-03-06 14:14 Tim Barr
2008-03-06 16:28 ` Ulf Samuelsson
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox