From: Ruben Louw <lfxciii@gmail.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] Mini2440 not mounting
Date: Fri, 21 Dec 2012 13:28:19 +0200 [thread overview]
Message-ID: <CAOP6b3j0BVJwoF7p0w079pZ__uLO_X53rqT3V1tb-BZUWg7t=g@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2206 bytes --]
Hi Everyone
I have, what it seems, a problem with my mini2440 in that its not mounting
to my host, I think I might be missing some settings and if anyone can
correct me I'd really appreciate it. I'm using a Mini2440 1gig nand.
I have the following:
1. Using BSP and ptxdist versions 2012.12.0.
2. my host network setup is : a) Address - 192.168.1.7
b) Netmask - 255.255.255.0
c) Gateway - 192.168.1.2
3. my target network setup is : a) Address - 192.168.1.27
b) Netmask - 255.255.255.0
c) Gateway - 192.168.1.2
d) ethaddr -
00:04:f3:00:06:35
e) Serverip - 192.168.1.7
4. I have NFS on my host, not sure if i should use NFS or TFTP and not sure
what the difference is, if any.
5. The log from my mini2440 serial output:
6. I did not run ptxdist platformconfig, because I don not fully understand
what the image has to be. Do I have to run this and select an image, if so,
what image should i use?
7. I do not know where the mini would mount to, maybe that is the main
issue. In the docs its written that the tftp server is /tftpboot, but I
dont have a directory like that anywhere.
8. I made some changes to the
"configs/platform-friendlyarm-mini2440/barebox-128m-env/config" like
changing the autoboot timeout, but when I run go 0x31000000, it boots and
uses default 3 second timeout.
9. I am not sure what the nfsroot setting should be, and when I change it,
it defaults to what it was:
if [ -n $user]; then
nfsroot =
"${eth0.serverip}:/home/${user}/nfsroot/${machine}"
else
nfsroot = "/path/to/nfs/root"
10. I do not receive any errors as my bootup log shows, yet i can not copy
the barebox image from the board support package to the directory ised by
the tftp server "cp platform-mini2440/images/barebox-image
/tftpboot/barebox-mini2440" because the directory
/tftpboot/barebox-mini2440 does not exist.
thank you for any help
Regards
Ruben Louw
[-- Attachment #1.2: Type: text/html, Size: 2422 bytes --]
[-- Attachment #2: Mini2440 serial output --]
[-- Type: application/octet-stream, Size: 2972 bytes --]
##### FriendlyARM BIOS 2.0 for 2440 #####
[x] format NAND FLASH for Linux
[v] Download vivi
[k] Download linux kernel
[y] Download root_yaffs image
[a] Absolute User Application
[n] Download Nboot for WinCE
[l] Download WinCE boot-logo
[w] Download WinCE NK.bin
[d] Download & Run
[z] Download zImage into RAM
[g] Boot linux from RAM
[f] Format the nand flash
[b] Boot the system
[s] Set the boot parameters
[u] Backup NAND Flash to HOST through USB(upload)
[r] Restore NAND Flash from HOST through USB
[q] Goto shell of vivi
[i] Version: 1138-2K
Enter your selection: q
Supervivi> go 0x31000000
go to 0x31000000
argument 0 = 0x00000000
argument 1 = 0x00000000
argument 2 = 0x00000000
argument 3 = 0x00000000
barebox 2011.05.0-ptx-2012.12.0 (Dec 21 2012 - 08:09:20)
Board: Mini 2440
NAND device: Manufacturer ID: 0xec, Chip ID: 0xd3 (Samsung NAND 1GiB 3,3V 8-bit)
Bad block table found at page 524224, version 0x01
Bad block table found at page 524160, version 0x01
nand_read_bbt: Bad block at 0x394e0000
dm9000 i/o: 0x20000300, id: 0x90000a46
eth@eth0: got MAC address from EEPROM: 00:00:00:00:00:00
refclk: 12000 kHz
mpll: 405000 kHz
upll: 48000 kHz
fclk: 405000 kHz
hclk: 101250 kHz
pclk: 50625 kHz
SDRAM1: CL4@101MHz
SDRAM2: CL4@101MHz
Malloc space: 0x33a00000 -> 0x33e00000 (size 4 MB)
Stack space : 0x339f8000 -> 0x33a00000 (size 32 kB)
running /env/bin/init...
Hit any key to stop autoboot: 2
mini2440:/
[-- Attachment #3: Type: text/plain, Size: 48 bytes --]
--
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2012-12-21 11:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-21 11:28 Ruben Louw [this message]
[not found] <CAOP6b3j0BVJwoF7p0w079pZ@mail.gmail.com>
2012-12-22 23:02 ` Dave Festing
2012-12-22 23:14 ` Dave Festing
2012-12-24 7:17 ` Ruben Louw
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOP6b3j0BVJwoF7p0w079pZ__uLO_X53rqT3V1tb-BZUWg7t=g@mail.gmail.com' \
--to=lfxciii@gmail.com \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox