TS-7200 16mb kernel image

Re: TS-7200 16mb kernel image

> I'm attempting to create a kernel image for a 16mb version of
> the TS-7200. Can someone give me some pointers?
>
> Here is my fis list:
>
> RedBoot> fis list
> Name              FLASH addr  Mem addr    Length      Entry point
> (reserved)        0x60000000  0x60000000  0x00E20000  0x00000000
> RedBoot           0x60E20000  0x60E20000  0x00040000  0x00000000
> RedBoot config    0x60FC0000  0x60FC0000  0x00001000  0x00000000
> FIS directory     0x60FE0000  0x60FE0000  0x00020000  0x00000000
>
> If I understand this correctly, I need to crosscompile evbarm
> and create gzimg_TS7200_wd0_flash_0x60e60000. Here are the
> steps I've taken:
> - Under .../sys/arch/evbarm/stand/gzboot/, cp -Rf
>   TS7200_flash_0x60660000 TS7200_flash_0x60e60000.
> - Modify Makefile RELOC= 0x60e60000, and change ldscript to set 0x60e60000.
> - With an empty ../obj, I did a ./build.sh -u -U -m evbarm kernel=TS7200 distribution, but got the build
distribution errors:
>
> =======  1 extra files in DESTDIR  =========
> Files in DESTDIR but missing from flist.
> File is obsolete or flist is out of date ?
> ------------------------------------------
> ./usr/mdec/gzboot_TS7200_0x60e60000.bin
> =========  end of 1 extra files  ===========

The next step would then be to add this file name to

  src/distrib/sets/lists/base/md.evbarm

Regards,

- Håvard

Re: TS-7200 16mb kernel image

Hi Håvard -- thanks for your help. I was able to create the kernel image; 
however I'm now stuck on booting the kernel. Here are the messages during 
boot:

RedBoot> g 0x60E60000
>> NetBSD/TS7200 Gzip Boot, Revision 1.2
>> (root <at> ..., Mon Aug  3 17:32:57 PDT 2009)
>> Load address: 0x200000
Uncompressing image...FATAL: error -3 from zlib

Does this indicate a checksum error?

Here's a summary of the steps I've taken so far to create 
gzimg_TS7200_wd0_flash_0x60e60000:

- cp -Rf TS7200_flash_0x60660000 TS7200_flash_0x60e60000 and modify Makefile 
RELOC= 0x60e60000 and ldscript.
- Add SUBDIR to /usr/src/sys/arch/evbarm/stand/gzboot/Makefile.
- Modify /usr/src/distrib/evbarm/gzboot/gzimg/Makefile targets to RELOC_ADDR 
0x60e60000 for TS7200.
- Add gzboot_TS7200_0x60e60000.bin to 
/usr/src/distrib/sets/lists/base/md.evbarm.
- Build tools, kernel, and distribution.
- From /usr/src/distrib/evbarm/gzboot/gzimg: make 
DESTDIR=/usr/src/obj/destdir.evbarm  MACHINE=evbarm MACHINE_ARCH=arm 
AWK=/usr/src/obj/tooldir.NetBSD-5.0_STABLE-i386/bin/nbawk 
CKSUM=/usr/src/obj/tooldir.NetBSD-5.0_STABLE-i386/bin/nbcksum 
DB=/usr/src/obj/tooldir.NetBSD-5.0_STABLE-i386/bin/nbdb  HOST_SH=/bin/sh 
MAKE=/usr/src/obj/tooldir.NetBSD-5.0_STABLE-i386/bin/nbmake 
MKTEMP=/usr/src/obj/tooldir.NetBSD-5.0_STABLE-i386/bin/nbmktemp 
MTREE=/usr/src/obj/tooldir.NetBSD-5.0_STABLE-i386/bin/nbmtree 
PAX=/usr/src/obj/tooldir.NetBSD-5.0_STABLE-i386/bin/nbpax 
SED=/usr/src/obj/tooldir.NetBSD-5.0_STABLE-i386/bin/nbsed 
TSORT=/usr/src/obj/tooldir.NetBSD-5.0_STABLE-i386/bin/nbtsort
- gzimg_TS7200_wd0_flash_0x60e60000 is located in 
/usr/src/distrib/evbarm/gzboot/gzimg/obj.
- Generally followed the instructions in the evbarm ports install under 
Preparation for the Technologic Systems TS-7200, replacing 0x60660000 with 
0x60e60000.

Thanks - Joel

--------------------------------------------------
From: "Havard Eidnes" <he <at> NetBSD.org>
Sent: Monday, August 03, 2009 05:35
To: <idatum <at> comcast.net>
Cc: <port-arm <at> netbsd.org>
Subject: Re: TS-7200 16mb kernel image

>> I'm attempting to create a kernel image for a 16mb version of
>> the TS-7200. Can someone give me some pointers?
>>
>> Here is my fis list:
>>
>> RedBoot> fis list
>> Name              FLASH addr  Mem addr    Length      Entry point
>> (reserved)        0x60000000  0x60000000  0x00E20000  0x00000000
>> RedBoot           0x60E20000  0x60E20000  0x00040000  0x00000000
>> RedBoot config    0x60FC0000  0x60FC0000  0x00001000  0x00000000
>> FIS directory     0x60FE0000  0x60FE0000  0x00020000  0x00000000
>>
>> If I understand this correctly, I need to crosscompile evbarm
>> and create gzimg_TS7200_wd0_flash_0x60e60000. Here are the
>> steps I've taken:
>> - Under .../sys/arch/evbarm/stand/gzboot/, cp -Rf
>>   TS7200_flash_0x60660000 TS7200_flash_0x60e60000.
>> - Modify Makefile RELOC= 0x60e60000, and change ldscript to set 
>> 0x60e60000.
>> - With an empty ../obj, I did a ./build.sh -u -U -m evbarm kernel=TS7200 
>> distribution, but got the build distribution errors:
>>
>> =======  1 extra files in DESTDIR  =========
>> Files in DESTDIR but missing from flist.
>> File is obsolete or flist is out of date ?
>> ------------------------------------------
>> ./usr/mdec/gzboot_TS7200_0x60e60000.bin
>> =========  end of 1 extra files  ===========
>
> The next step would then be to add this file name to
>
>  src/distrib/sets/lists/base/md.evbarm
>
> Regards,
>
> - Håvard 

Re: TS-7200 16mb kernel image

> Hi Håvard -- thanks for your help. I was able to create the kernel image; 
> however I'm now stuck on booting the kernel. Here are the messages during 
> boot:
>
> RedBoot> g 0x60E60000
> >> NetBSD/TS7200 Gzip Boot, Revision 1.2
> >> (root <at> ..., Mon Aug  3 17:32:57 PDT 2009)
> >> Load address: 0x200000
> Uncompressing image...FATAL: error -3 from zlib
>
> Does this indicate a checksum error?

It does appear to do so -- looking at the zlib(3) man page seems
to indicate so:

     #define Z_OK            0
     #define Z_STREAM_END    1
     #define Z_NEED_DICT     2
     #define Z_ERRNO        (-1)
     #define Z_STREAM_ERROR (-2)
     #define Z_DATA_ERROR   (-3)
     #define Z_MEM_ERROR    (-4)
     #define Z_BUF_ERROR    (-5)
     #define Z_VERSION_ERROR (-6)
     /* Return codes for the compression/decompression functions.
      * Negative values are errors,
      * positive values are used for special but normal events.
      */

Regards,

- Håvard

Re: TS-7200 16mb kernel image

On Tue, Aug 04, 2009 at 09:58:02AM +0200, Havard Eidnes wrote:
> > Hi H?vard -- thanks for your help. I was able to create the kernel image; 
> > however I'm now stuck on booting the kernel. Here are the messages during 
> > boot:
> >
> > RedBoot> g 0x60E60000
> > >> NetBSD/TS7200 Gzip Boot, Revision 1.2
> > >> (root <at> ..., Mon Aug  3 17:32:57 PDT 2009)
> > >> Load address: 0x200000
> > Uncompressing image...FATAL: error -3 from zlib
> >
> > Does this indicate a checksum error?
> 
> It does appear to do so -- looking at the zlib(3) man page seems
> to indicate so:
> 
>      #define Z_OK            0
>      #define Z_STREAM_END    1
>      #define Z_NEED_DICT     2
>      #define Z_ERRNO        (-1)
>      #define Z_STREAM_ERROR (-2)
>      #define Z_DATA_ERROR   (-3)
>      #define Z_MEM_ERROR    (-4)
>      #define Z_BUF_ERROR    (-5)
>      #define Z_VERSION_ERROR (-6)
>      /* Return codes for the compression/decompression functions.
>       * Negative values are errors,
>       * positive values are used for special but normal events.
>       */

If this is a zlib fubar, it might be related to the 'cvs -z' lossage.

	David

--

-- 
David Laight: david <at> l8s.co.uk

Re: Gumstix verdex patch

Hi! all,

From: KIYOHARA Takashi <kiyohara <at> kk.iij4u.or.jp>
Date: Wed, 08 Jul 2009 18:28:55 +0900 (JST)

> I almost ended the transplant work of gumstix.  (exclude malo(4))
> I am planning to merge it sequentially next week.

> 2. saost(4)'s frequency configure at run-time.  Need support both PXA270
>    and PXA255.  It influence to hpcarm and zaurus and evbarm boards
>    (TWINTAIL, VIPER, LUBBOCK) perhaps.
>      ftp://ftp.netbsd.org/pub/NetBSD/misc/kiyohara/gumstix/saost-runtime-config-20090625.diff

committed.

> 3. I misstake sinse 2007/08/21.
>    (http://mail-index.netbsd.org/source-changes/2007/08/21/0030.html)
>    This patch influence to zaurus perhaps.
>      ftp://ftp.netbsd.org/pub/NetBSD/misc/kiyohara/gumstix/gpio-config-20090221.diff  

committed.

> 4. The peripheral device of pxa might not be able to do an appropriate
>    match. It is necessary to confirm the address more.  We do not have
>    the method of fixing the order of matching the device.
>    pxaip_attach_critical() configure some peripheral devices.  However
>    pxaohci and pxaudc and others can match.
> 
>      ftp://ftp.netbsd.org/pub/NetBSD/misc/kiyohara/gumstix/drivers-match-20090221.diff

I thought that the match by not the address but the name was better.
In this case, the unknown address surrounding will be able to match.

ftp://ftp.netbsd.org/pub/NetBSD/misc/kiyohara/gumstix/drivers-match-20090804.diff

I will commit this patch next week.

Thanks,
--
kiyohara

Re: TS-7200 16mb kernel image

Hi David -- what is 'cvs -z' lossage? 

I build the kernel image and then from /usr/src/distrib/evbarm/gzboot/gzimg, 
run:

    make  DESTDIR=/usr/src/obj/destdir.evbarm  MACHINE=evbarm

The output from make looks like this:

Populating gzimg_TS7200_wd0_flash_0x60e60000
rm -f gzimg_TS7200_wd0_flash_0x60e60000.kern.gz
gzip -9c /usr/src/sys/arch/evbarm/compile/obj/TS7200/netbsd-wd0.bin > 
gzimg_TS7200_wd0_flash_0x60e60000.kern.gz
/usr/src/obj/tooldir.NetBSD-5.0_STABLE-i386/bin/nbcat 
/usr/src/obj/destdir.evbarm/usr/mdec/gzboot_TS7200_0x60e60000.bin 
gzimg_TS7200_wd0_flash_0x60e60000.kern.gz > 
gzimg_TS7200_wd0_flash_0x60e60000
rm -f gzimg_TS7200_wd0_flash_0x60e60000.gz
gzip -9c gzimg_TS7200_wd0_flash_0x60e60000 > 
gzimg_TS7200_wd0_flash_0x60e60000.gz

Is this a problem with my version of gzip?

Thanks - Joel

--------------------------------------------------
From: "David Laight" <david <at> l8s.co.uk>
Sent: Tuesday, August 04, 2009 09:54
Cc: <idatum <at> comcast.net>; <port-arm <at> netbsd.org>
Subject: Re: TS-7200 16mb kernel image

> On Tue, Aug 04, 2009 at 09:58:02AM +0200, Havard Eidnes wrote:
>> > Hi H?vard -- thanks for your help. I was able to create the kernel 
>> > image;
>> > however I'm now stuck on booting the kernel. Here are the messages 
>> > during
>> > boot:
>> >
>> > RedBoot> g 0x60E60000
>> > >> NetBSD/TS7200 Gzip Boot, Revision 1.2
>> > >> (root <at> ..., Mon Aug  3 17:32:57 PDT 2009)
>> > >> Load address: 0x200000
>> > Uncompressing image...FATAL: error -3 from zlib
>> >
>> > Does this indicate a checksum error?
>>
>> It does appear to do so -- looking at the zlib(3) man page seems
>> to indicate so:
>>
>>      #define Z_OK            0
>>      #define Z_STREAM_END    1
>>      #define Z_NEED_DICT     2
>>      #define Z_ERRNO        (-1)
>>      #define Z_STREAM_ERROR (-2)
>>      #define Z_DATA_ERROR   (-3)
>>      #define Z_MEM_ERROR    (-4)
>>      #define Z_BUF_ERROR    (-5)
>>      #define Z_VERSION_ERROR (-6)
>>      /* Return codes for the compression/decompression functions.
>>       * Negative values are errors,
>>       * positive values are used for special but normal events.
>>       */
>
> If this is a zlib fubar, it might be related to the 'cvs -z' lossage.
>
> David
>
> -- 
> David Laight: david <at> l8s.co.uk 

Re: Gumstix verdex patch

Hi! all,

From: KIYOHARA Takashi <kiyohara <at> kk.iij4u.or.jp>
Date: Wed, 05 Aug 2009 21:38:53 +0900 (JST)

> > 4. The peripheral device of pxa might not be able to do an appropriate
> >    match. It is necessary to confirm the address more.  We do not have
> >    the method of fixing the order of matching the device.
> >    pxaip_attach_critical() configure some peripheral devices.  However
> >    pxaohci and pxaudc and others can match.
> > 
> >      ftp://ftp.netbsd.org/pub/NetBSD/misc/kiyohara/gumstix/drivers-match-20090221.diff
> 
> I thought that the match by not the address but the name was better.
> In this case, the unknown address surrounding will be able to match.
> 
> ftp://ftp.netbsd.org/pub/NetBSD/misc/kiyohara/gumstix/drivers-match-20090804.diff

committed.
--
kiyohara

Gumstix

Hi! all,

verdex and verdex-pro supported.
Also you use audiostix or USB HOST(console-LCD etc.) require more patches.

audiostix
---------
ftp://ftp.netbsd.org/pub/NetBSD/misc/kiyohara/gumstix/XXXX-audiostix-20060625.diff

USB HOST
--------
ftp://ftp.netbsd.org/pub/NetBSD/misc/kiyohara/gumstix/XXXX-ohci-20090808.diff

Thanks,
--
kiyohara
  However, I have not planned for porting yet though I bought an Overo Earth
  and a Summit.  ;-<

Digital DNARD "Shark" network computer for sale

At the risk of being in bad form because this is not a technical
topic--though perhaps still of interest to the NetBSD arm developer
community because these are uncommon systems--I want to mention that
I'm selling my Shark computer.  It's been stuck neglected in a dark
corner of a closet for the past several years. Certainly someone else
can put it to much better and more productive use.

  http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=220464726146

B.