• Home
  • Help
  • Search
  • Login
  • Register
Pages: [1]
Author Topic: Debian Installer for d2plug  (Read 5136 times)
tspoon
Newbie
*

Karma: 0
Posts: 5


View Profile
« on: June 03, 2012, 11:48:02 PM »

Hi all, I'm wondering if anyone can help me with this, I am trying to run the Debian 'versatile' installer for my d2plug, but it fails to start.
I sourced the files from :

ftp.debian.org/debian/dists/stable/main/installer-armel/current/images/versatile/netboot/initrd.gz
ftp.debian.org/debian/dists/stable/main/installer-armel/current/images/versatile/netboot/vmlinuz-2.6.32-5-versatile

I then use mkimage like so:

mkimage -A arm -O linux -T ramdisk -C gzip -a 0x3000000 -e 0x3000000 -n "debian" -d vmlinuz-2.6.32-5-versatile uimage

The result is :

Image Name:   debian
Created:      Sun Jun  3 09:52:17 2012
Image Type:   ARM Linux RAMDisk Image (gzip compressed)
Data Size:    1246756 Bytes = 1217.54 kB = 1.19 MB
Load Address: 0x03000000
Entry Point:  0x03000000

This is put on the first partition of an sd card (fat) and on startup the following commands:

usb start;
fatls usb 1:1;

fatload usb 1:1 0x2000000 uimage;
fatload usb 1:1 0x3000000 initrd;
usb stop;
bootm 0x2000000 0x3000000;

The message I get is:

Marvell>> bootm 0x2000000 0x3000000;
## Booting kernel from Legacy Image at 02000000 ...
   Image Name:   debian
   Created:      2012-06-04   6:44:57 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    1246756 Bytes =  1.2 MB
   Load Address: 03000000
   Entry Point:  03000000
   Verifying Checksum ... OK
Wrong Image Type for bootm command
ERROR: can't get kernel image!

I found these instructions online at another forum, but I don't really have enough knowledge to know why they don't work correctly. Is anybody here able to point out the problem or suggest a good place to start checking? Thanks in advance...

Logged

mentor
Jr. Member
**

Karma: 2
Posts: 67


View Profile
« Reply #1 on: June 04, 2012, 06:18:36 AM »

Sorry I not has experement on Debian

but after see you build uImage precedure , I see some thing maybe wrong

you used mkimage ...-T ramdisk ... to generate , but uboot bootcmd comand can't reginize this type , so you see your error meaage

correct type should be kernel , I attach I used latest D2 kernel log for your reference

.....
   Created:      2010-07-15  11:15:16 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3205164 Bytes =  3.1 MB
....




Logged

tspoon
Newbie
*

Karma: 0
Posts: 5


View Profile
« Reply #2 on: June 04, 2012, 02:10:19 PM »

Thanks for that mentor, that would make sense, given the error message:

Wrong Image Type for bootm command
ERROR: can't get kernel image!

that is received. I'll try again tonight after work and report back. Cheers.
Logged

tspoon
Newbie
*

Karma: 0
Posts: 5


View Profile
« Reply #3 on: June 05, 2012, 12:20:38 AM »

Unfortunately no luck, I used mkimage with '-T kernel', and an image is made, but when I try to run it, it now says:

Marvell>> bootm 0x2000000 0x3000000;
## Booting kernel from Legacy Image at 02000000 ...
   Image Name:   debian
   Created:      2012-06-05   7:13:46 UTC
   Image Type:   ARM Linux Kernel Image (gzip compressed)
   Data Size:    1246756 Bytes =  1.2 MB
   Load Address: 03000000
   Entry Point:  03000000
   Verifying Checksum ... OK
Wrong Ramdisk Image Format
Ramdisk image is corrupt or invalid

Before it wanted a kernel image, but when given a kernel image it now wants a ramdisk image. It's probably simple, but the error codes are confusing me. Any more clues from onlookers would be welcome, cheers.

Logged

mentor
Jr. Member
**

Karma: 2
Posts: 67


View Profile
« Reply #4 on: June 07, 2012, 08:03:29 PM »

I think if you used latest kernel src to build uImage ,it should be running at your board ,not see below issue right?

if it is true , you could refernce latrest kernel src to check how to generate uImage to do , it should be solve your issue

if you want to gvie a try , you could reference kernel src "/arch/arm/boot Makefile" or "/arch/arm/Makefile" to do
Logged

bigbear59
Newbie
*

Karma: 0
Posts: 26


View Profile
« Reply #5 on: September 27, 2012, 04:16:11 PM »

Try:
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x3000000 -e 0x3000000 -n "debian" -d initrd.gz uinitrd

use your D2Plug uImage, copy d2plug.uImage & d2plug.uImage to the 1st partition

Quote
Marvell>>  fatload usb 1:1 0x2000000 d2plug.uImage
reading d2plug.uImage
...
3157776 bytes read
Marvell>>  fatload usb 1:1 0x3000000 uinitrd
reading uinitrd
...

2796264 bytes read
Marvell>> bootm  0x2000000 0x3000000
## Booting kernel from Legacy Image at 02000000 ...
   Image Name:   Linux-2.6.32.55-dove-5.4.2
   Created:      2012-02-03   8:55:19 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3157712 Bytes =  3 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 03000000 ...
   Image Name:   Debian ramdisk 2.6.39.2
   Created:      2012-09-27  22:20:28 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    2796200 Bytes =  2.7 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 2.6.32.55-dove-5.4.2

got this from http://dl.dropbox.com/u/308049/D2Plug%20Debian%20HowTo.pdf

Hope this helps
BigBear
« Last Edit: September 27, 2012, 04:18:51 PM by bigbear59 » Logged

Give me a fish, I eat for a day.  Teach me to fish, I eat for a lifetime.
"Do you have any spades?"

tyzef
Newbie
*

Karma: 0
Posts: 3


View Profile
« Reply #6 on: February 06, 2013, 04:21:01 PM »

For me it's works fine for installing debian base but now i've some problem with x server ... i think i've not good drivers for video dove ... Did anyone have succeed ?
Logged

Pages: [1]
Print
Jump to: