--- In Matthieu Crapet <> wrote:
> Greetings,
>
> I am trying for my first time to install NetBSD, according to
Jesse's
> web page.
>
> Everything is ok, except my lack of space on my 256 CF.
> I installed "Base" and "System (/etc)"; "Compiler Tools" doesn't
fit
> (not sure but the install reported an corrupted file ?).
The base system + compilers does fit on a 256M CF but the issue is
that the installation program needs space for both the downloaded
tarfiles and the extracted versions of them. I've gotten around
this by strategically hitting "Ctrl-Z" to suspend the installation
program after successfully extracting a set tarfile. Ctrl-Z will
drop you into a shell where you can then manually "rm" the tarfile
just extracted and then type "fg" to resume installation with extra
free space.
>
> My problem is now to boot. Jesse is storing the kernel into flash,
> that's my problem: I really don't want to touch my flash, I want
to keep
> my Linux.
>
> So I tried the usual way (TFTP) I use with Linux kernel
developpement :
>
> load -r -b 0x00218000 -h 192.168.1.48 zImage
> exec -c "console=ttyAM0,115200 ...etc..."
>
> So I tried the same for BSD's kernel:
>
> load -r -b 0x00200000 -h 192.168.1.48
gzimg_TS7200_wd0_flash_0x60660000
> go
>
> It does not work. Does the 0x60660000 address is written inside
the
> gzimg, I assume yes.
> Is there a way to make launch the kernel from memory ?
You need the ftp://ftp.embeddedarm.com/evbarm/binary/kernel/netbsd-
wd0.bin-TS7200.gz file to load this way. The gzimg's expect to be
executed-in-place at 0x60660000. Also, be sure to gunzip the above
file before loading it from TFTP to 0x200000. The gzimg's have a
decompressor embedded in the front of the image that is hardcoded to
extract to 0x200000 so 0x200000 is the one place you do NOT want it.
>
> I watched on embeddedARM ftp, I found theses 3 files :
>
> gzimg_TS7200nokplcd_wd0_flash_0x60660000
> gzimg_TS7200_wd0_flash_0x60660000
> gzimg_TS7200_wd0_flash_0x60e60000
>
> $ diff gzimg_TS7200_wd0_flash_0x60660000
gzimg_TS7200_wd0_flash_0x60e60000
> $
>
> Surprising ? What's is the "nokplcd" stuff ?
This is a kernel I built for a customer with the matrix keypad
driver and LCD driver disabled. (no kp lcd) By default these
drivers are enabled and if you want to use DIO pins for yourself,
they need to be disabled. The drivers plug into NetBSD's wscons
framework as a regular VT100 console. You can actually run a login
and shell using the LCD and keypad as console and keyboard. With
the drivers enabled, you just write your program as a regular
console text-mode application and don't have to be concerned with
the details of the HD44780 or the polling/debouncing logic of the
keypad.
//Jesse Off
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|