[U-Boot-Users] U-Boot on simulated at91rm9200/ep7312 boards (skyeye)
Hi,
Skyeye wiki shows howto load u-boot on the pc emulator. I have been trying to do the same for the at91rm9200 board on my pc but am getting no success. I am therefore sending this mail to both the skyeye-developers and u-boot-users list. I would appreciate if you could suggest some inputs as this is my very first hands on with both the (should i say?) applications.
Input/output is ignored at the boot prompt for the at91rm9200 board (1) I have had success loading u-boot for ep7312 board via skyeeye emulator while the u-boot for at91rm9200 simply doesn't takes any key strokes whatsoever at the boot prompt.
The only difference between the two u-boot config files is that the following three lines are not present in ep7312 board config. As am on emulation mode i have set USART0 instead of DBGU for the at91rm9200 board
#undef CONFIG_DBGU #define CONFIG_USART0 #undef CONFIG_USART1
When i run the skyeye with this config i get the following In: serial Out: serial Err: serial U-Boot> (I get the same message for ep7312 board but the input is actually /dev/stdin and output/err is /dev/stdout)
The keystrokes are simply ignored at the boot prompt. I tried the followoing skyeye configuration uart: fd_in=/dev/stdin, fd_out=/dev/stdout so atleast i could redirect the serial input output via stdin/stdout. But this didn't help me either.
This is really annoying as i can see the skyeye emulator working but am unable to how to redirect the input/output. Any guesses?
Networking issue with ep7312 u-boot.bin and skyeye (2) the u-boot for ep7312 board which loads fine has the following configuration #define CONFIG_ETHADDR 0:4:3:2:1:f #define CONFIG_NETMASK 255.0.0.0 #define CONFIG_IPADDR 10.0.0.2 #define CONFIG_GATEWAYIP 10.0.0.1 #define CONFIG_SERVERIP 10.203.234.11
and skyeye.conf defines net: state=on, type=vnet,base=0xfffa0000, size=0x20,int=16, mac=0:4:3:2:2:f, ethmod=tuntap, hostip=10.0.0.1
When i run the skyeye emulator, u-boot boots fine and shows me the prompt. I could see a new virtual network interface present and can ping the new virtual host as well. But, when i do a tftpboot the boot prompt simply hangs. The tftp logs doesn't shows any file request either
SKYEYE: If you have ELF kernel file, please use -e option to indicate your ELF format kernel filename SKYEYE: If you only have kernel binary image, you should put the filename of kernel binary image in skyeye.conf file arch: arm cpu info: armv4, arm720t, 41807200, ffffff00, 1 mach info: name ep7312, mach_init addr 0x8068030 uart info: input device is /dev/stdin, fd is 4. uart info: output device is /dev/stdout, fd is 5. ethmod num=1, mac addr=0:4:3:2:2:f, hostip=10.0.0.1 SKYEYE: use arm7100 mmu ops Loaded RAM ./u-boot.bin
U-Boot 1.1.4 (Mar 30 2006 - 15:19:26) U-Boot code: C0F80000 -> C0F952F0 BSS: -> C0F99820 RAM Configuration: Bank #0: c0000000 16 MB Flash: 16 MB *** Warning - bad CRC, using default environment
In: serial Out: serial Err: serial EP7312 # EP7312 # EP7312 # tftpboot CS8900 Ethernet chip not found?! *** Warning: no boot file name; using '0A000002.img' TFTP from server 10.203.234.11; our IP address is 10.0.0.2 Filename '0A000002.img'. Load address: 0xc0500000 Loading: *
Guys regarding the second i.e. network issue i digged that
/* if MAC address was not discovered yet, save the packet and do an ARP request */ if (memcmp(ether, NetEtherNullAddr, 6) == 0) { is returning true and actually its sending ARP packets for address discovery. I suppose i have some misconfiguration.
I shall investigate this and update tomorrow.
Sorry if this is off-topic for either of the lists.
cheers, rohit
On 3/30/06, Rohit rohits79@gmail.com wrote:
Hi,
Skyeye wiki shows howto load u-boot on the pc emulator. I have been trying to do the same for the at91rm9200 board on my pc but am getting no success. I am therefore sending this mail to both the skyeye-developers and u-boot-users list. I would appreciate if you could suggest some inputs as this is my very first hands on with both the (should i say?) applications.
Input/output is ignored at the boot prompt for the at91rm9200 board (1) I have had success loading u-boot for ep7312 board via skyeeye emulator while the u-boot for at91rm9200 simply doesn't takes any key strokes whatsoever at the boot prompt.
The only difference between the two u-boot config files is that the following three lines are not present in ep7312 board config. As am on emulation mode i have set USART0 instead of DBGU for the at91rm9200 board
#undef CONFIG_DBGU #define CONFIG_USART0 #undef CONFIG_USART1
When i run the skyeye with this config i get the following In: serial Out: serial Err: serial U-Boot> (I get the same message for ep7312 board but the input is actually /dev/stdin and output/err is /dev/stdout)
The keystrokes are simply ignored at the boot prompt. I tried the followoing skyeye configuration uart: fd_in=/dev/stdin, fd_out=/dev/stdout so atleast i could redirect the serial input output via stdin/stdout. But this didn't help me either.
This is really annoying as i can see the skyeye emulator working but am unable to how to redirect the input/output. Any guesses?
Networking issue with ep7312 u-boot.bin and skyeye (2) the u-boot for ep7312 board which loads fine has the following configuration #define CONFIG_ETHADDR 0:4:3:2:1:f #define CONFIG_NETMASK 255.0.0.0 #define CONFIG_IPADDR 10.0.0.2 #define CONFIG_GATEWAYIP 10.0.0.1 #define CONFIG_SERVERIP 10.203.234.11
and skyeye.conf defines net: state=on, type=vnet,base=0xfffa0000, size=0x20,int=16, mac=0:4:3:2:2:f, ethmod=tuntap, hostip=10.0.0.1
When i run the skyeye emulator, u-boot boots fine and shows me the prompt. I could see a new virtual network interface present and can ping the new virtual host as well. But, when i do a tftpboot the boot prompt simply hangs. The tftp logs doesn't shows any file request either
SKYEYE: If you have ELF kernel file, please use -e option to indicate your ELF format kernel filename SKYEYE: If you only have kernel binary image, you should put the filename of kernel binary image in skyeye.conf file arch: arm cpu info: armv4, arm720t, 41807200, ffffff00, 1 mach info: name ep7312, mach_init addr 0x8068030 uart info: input device is /dev/stdin, fd is 4. uart info: output device is /dev/stdout, fd is 5. ethmod num=1, mac addr=0:4:3:2:2:f, hostip=10.0.0.1 SKYEYE: use arm7100 mmu ops Loaded RAM ./u-boot.bin
U-Boot 1.1.4 (Mar 30 2006 - 15:19:26) U-Boot code: C0F80000 -> C0F952F0 BSS: -> C0F99820 RAM Configuration: Bank #0: c0000000 16 MB Flash: 16 MB *** Warning - bad CRC, using default environment
In: serial Out: serial Err: serial EP7312 # EP7312 # EP7312 # tftpboot CS8900 Ethernet chip not found?! *** Warning: no boot file name; using '0A000002.img' TFTP from server 10.203.234.11; our IP address is 10.0.0.2 Filename '0A000002.img'. Load address: 0xc0500000 Loading: *
On 3/30/06, Rohit rohits79@gmail.com wrote:
Hi,
Input/output is ignored at the boot prompt for the at91rm9200 board (1) I have had success loading u-boot for ep7312 board via skyeeye emulator while the u-boot for at91rm9200 simply doesn't takes any key strokes whatsoever at the boot prompt.
I had the same problem and applied a quick fix against skyeye-1.2.0-RC4. Its ugly but nevertheless should serve the purpose. I used a fresh u-boot (version u-boot-1.1.3) configured with at91rm9200dk_config.
HTH
-- Vijairaj
I had the same problem and applied a quick fix against skyeye-1.2.0-RC4. Its ugly but nevertheless should serve the purpose. I used a fresh u-boot (version u-boot-1.1.3) configured with at91rm9200dk_config.
Thanks a bunch for the patch. You made my weekend ;).
I can now run u-boot for at91rm on skyeye(compiled for DBGU instead USART).
Cheers rohit
On 3/31/06, Rohit rohits79@gmail.com wrote:
Thanks a bunch for the patch. You made my weekend ;).
I can now run u-boot for at91rm on skyeye(compiled for DBGU instead USART).
Please let me know if you are successful in booting the linux kernel. I have not looked in to it for a long time now, but I would love to hear of any developments.
-- Warm Regards, Vijairaj
On 3/31/06, Vijairaj vijairaj.r@gmail.com wrote:
Please let me know if you are successful in booting the linux kernel. I have not looked in to it for a long time now, but I would love to hear of any developments.
Am presently away from work machine so can't tell you the exact lines but on expanding the kernel it says something like the kernel machine ID is different 0x000000fb whilst the mach ID expected is 0x0...106.
I suppose its because i am using the vmlinux image (from the skyeye suite) which is generic i.e. for at91rm9200 board while u-boot compiled is for AT91rm9200DK.
I shall try to compile the image and run on monday. In case if you have the image please can you share the initrd and/or kernel image.
Best Regards, rohit
On 4/1/06, Rohit rohits79@gmail.com wrote:
On 3/31/06, Vijairaj vijairaj.r@gmail.com wrote:
Please let me know if you are successful in booting the linux kernel. I have not looked in to it for a long time now, but I would love to hear of any developments.
Hi All,
I tried to load the kernel and got the following error. Can anyone suggest me what could be wrong here?
thanks rohit
[root@localhost at91rm]# skyeye SKYEYE: If you have ELF kernel file, please use -e option to indicate your ELF format kernel filename SKYEYE: If you only have kernel binary image, you should put the filename of kernel binary image in skyeye.conf file arch: arm cpu info: armv4, arm920t, 41009200, ff00fff0, 2 mach info: name at91rm92, mach_init addr 0x8069c80 uart info: input device is /dev/stdin, fd is 4. uart info: output device is /dev/stdout, fd is 5. SKYEYE: use arm920t mmu ops Loaded RAM ./u-boot.bin Loaded RAM ./uImage
U-Boot 1.1.4 (Apr 3 2006 - 14:31:42)
U-Boot code: 21F00000 -> 21F16EEC BSS: -> 21F33E04 RAM Configuration: Bank #0: 20000000 32 MB Atmel: Flash: 0 kB *** Warning - bad CRC, using default environment
In: serial Out: serial Err: serial U-Boot> bootm ## Booting image at 21000000 ... Image Name: Linux Kernel Image Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 534804 Bytes = 522.3 kB Load Address: 02100000 Entry Point: 02100000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK
Starting kernel ...
undefined instruction pc : [<2100000c>] lr : [<21f129f8>] sp : 21eddc10 ip : 00000001 fp : 21eddca4 r10: 21f1a1d0 r9 : 21e59fb8 r8 : 21eddfdc r7 : 21000040 r6 : 00000000 r5 : 00000000 r4 : 00000000 r3 : 02100000 r2 : 20000100 r1 : 000000fb r0 : 0001c200 Flags: nZCv IRQs off FIQs off Mode SVC_32 Resetting CPU ...
In message 586f5d00604030206t615823c0h5a2b16bdf554f945@mail.gmail.com you wrote:
I tried to load the kernel and got the following error. Can anyone suggest me what could be wrong here?
This discussion has nothing to do with U-Boot. Please don't send off topic messages to the u-boot-users list.
------=_Part_13826_19531358.1144055189931 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
And STOP posting HTML!!
Wolfgang Denk
participants (3)
-
Rohit -
Vijairaj -
Wolfgang Denk