unable to select option from NOR Flash Boot menu

Nagaraju
Hi, i am using micro2440 on linux with serial console  and when i boot from
NOR flash. I get the menu when I see on hyperterminal is as follows:
##### 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: 0945-2K
Enter your selection: s

When I select option q, it displays another character and tells that
particular driver is not installed. similarly when I type 'a' it displays
'c'. when I type 'b', it boots the system with linux image.

Please anyone tell me the reason behind this.
Thanks in advance

davef
The other character and the name of the driver might be useful to someone
troubleshooting your problem!

You know that when you press option q that you should just see a >?

Nagaraju
Please find below responses we are getting w.r.t selection,
entered char - response char
x - x (Good)
v - v (Good)
k - { (wrong)
y - { (wrong)
a - c (wrong)
n - n (Good)
l - l (Good)
w - w (Good)
d - d (Good)
z - z (Good)
g - g (Good)
f - f (Good)
b - b (Good)
s - s (Good)
u - w (Wrong)
r - r (Good)
q - s (Wrong)
i - k (Wrong)

asdf
Maybe a hardware problem of your serial cable?

Nagaraju
the serial cable is working fine. we have tested on another board. There we
are getting the proper response.

davef
Have you tried DNW instead of hyperterminal?

The name of the missing driver?

Nagaraju
We have tried DNW also. It also shows the same behaviour. When we try to
select "Download the linux kernel" option via key "k", or "Download
root_yaffs image" option via key "y", it always shows character "{" on the
screen.

davef
I now understand that there was NO missing driver as mentioned in your
first post.

Good luck.

Andreas Watterott
@Nagaraju:
Have you also tried to re-flash Supervivi with HJTAG?

Nagaraju
Attachment: test.TXT (17.52 KB)
Hi,
Yes we have tried with downloading supervivi into NOR Flash via H-JTAG
also. We still get the same response.

We were unable to load the yaffs image into the board. 
We have followed the below steps:
1. x - for formatting the NAND Flash - SUCCESS
2. v - download supervivi-128(for 256 MB NAND) bootloader  - SUCCESS
3. k - download linux kernel - SUCCESS(after multiple attempts)
4. y - yaffs2 image - FAILURE(We were unable to download this part)
Whenever we type y to download the yaffs image, the } character displays on
the screen and the same menu repeats again.

We tried to reset the board without downloading yaffs image and the result
is as found in the attachment with name "test.txt".
Please give further directions .

Thanks in advance.

davef
Just some ideas:

That is the latest version of Supervivi for your device?

Have you got your keyboard setup to some non-standard format?

What happened to cause multiple attempts at loading the kernel?

I don't recall DNW reporting Bad eraseblocks, but that might be because I
haven't got any. 


> Scanning device for bad blocks
> Bad eraseblock 195 at 0x000001860000
> Bad eraseblock 1257 at 0x000009d20000
> Bad eraseblock 1663 at 0x00000cfe0000

*********
Creating 5 MTD partitions on "NAND 256MiB 3,3V 8-bit":
0x000000000000-0x000000040000 : "supervivi"
0x000000040000-0x000000060000 : "param"
0x000000060000-0x000000560000 : "Kernel"
0x000000560000-0x000040560000 : "root"
mtd: partition "root" extends beyond the end of device "NAND 256MiB 3,3V
8-bit" -- size truncated to 0xfaa0000
0x000000000000-0x000040000000 : "nand"
mtd: partition "nand" extends beyond the end of device "NAND 256MiB 3,3V
8-bit" -- size truncated to 0x10000000
********

I wonder about the size being truncated.  People have reported this before
but do not recall that it was something you needed to sort out.  If you
start tweaking your kernel then you might need to change the kernel
partition size.



> block 153 is bad
> block 1215 is bad
> block 1621 is bad

I wonder why these are not the same blocks as reported above, but can not
offer any suggestions other than Google. 

What happens if you do a y as a first selection?

Good luck,
Dave

Nagaraju
Hi For your Questions:

1. That is the latest version of Supervivi for your device?
Ans: Yes, We have downloaded from the internet

2. What happened to cause multiple attempts at loading the kernel?
Ans: We thought that the kernel was not loaded properly into NAND flash. So
we tried multiple times.

3. What happens if you do a y as a first selection?
Ans: It does take that option 'y' only once. After that it never accepts
the option 'y' and always it displays "}". 

I have some questions. Please answer

1. Which IDE we need to use for debugging of the code?
2. What is the software architecture like which folder to put where? Please
provide the locations and source files names so that we can look into the
code and we too can investigate the issue on our side.

Thanks in advance
Regards,
Nagaraju S

davef
Supervivi is closed source, so you will not be able to debug it.

I have been using u-boot for about a year and more recently barebox. 

If you are just starting out on your embedded Linux journey I would highly
recommend you have a look at this:

http://www.oselas.org/oselas/bsp/pengutronix/mini2440_bsp_en.html

Nagaraju
Thanks for the information.
I have prior experience in vxworks but not in embedded linux.

Please suggest for the following queries.
1. can we download uboot onto the board and proceed further?
2. What is the procedure we need to follow if we are using uboot
bootloader?
Please provide if any documents are there on how to proceed with uboot.