I have been using Kamikaze 7.09 for our Atheros AR2315 SOC. Current redboot is configured to look for and run trx. I have many of these systems in the field and cannot modify redboot config.
How do I enable Kamikaze 8.09 to build a kernel in this format, as CONFIG_MTD_TRX is not an option?
Has this been changed from 7.09?

Thank you.

Hi,
There is a trick to configure the Kamikaze 8.09 by moving to the installation directory and search there. You will get the config.ini  file there, make the following changes "CONFIG_BLK_DEV_RAM_TRX=y and CONFIG_MTD_TRX=y ". I hope these may be helpful to you. Good Luck!!!

(Last edited by henrygrik on 11 Dec 2009, 09:55)

Thanks alot for the reply and info. I tried by adding the following to target/linux/atheros/config.default:

    CONFIG_BLK_DEV_RAM=y
    CONFIG_BLK_DEV_RAM_BLOCKSIZE=1024
    CONFIG_BLK_DEV_RAM_COUNT=1
    CONFIG_BLK_DEV_RAM_SIZE=4096
    CONFIG_BLK_DEV_RAM_TRX=y
   # CONFIG_MTD_SPLIT_ROOTFS is not set
    CONFIG_MTD_TRX=y

It looks like it tried, but the make complained, captured in my makeDump log:

    makeDump:.config:154:warning: trying to assign nonexistent symbol BLK_DEV_RAM_TRX
    makeDump:.config:1030:warning: trying to assign nonexistent symbol MTD_TRX
    makeDump:.config:154:warning: trying to assign nonexistent symbol BLK_DEV_RAM_TRX
    makeDump:.config:1030:warning: trying to assign nonexistent symbol MTD_TRX

How do I get around the 'nonexistent symbol'?
Has this function been totally removed from any platform default configuration?

I am really in need of figuring this one out as I cannot change my installed base redboot code, and its looking for a trx.

My memory device is configured like this:

    RedBoot> fis list                                             
    Name              FLASH addr  Mem addr    Length      Entry point
    RedBoot           0xA8000000  0xA8000000  0x00030000  0x00000000
    linux                 0xA8030000  0x80400000  0x00390000  0x80400000
    linux2               0xA83C0000  0x80400000  0x00390000  0x80400000
    jffs                    0xA8750000  0x80400000  0x000A0000  0x80400000
    FIS directory   0xA87F0000  0xA87F0000  0x00010000  0x00000000
    Atheros data  0xA87FE000  0xA87FE000  0x00001000  0x00000000

Below is redboot output from my functioning image, based on 7.09, finds the trx, decompresses and runs it:

    RedBoot(tm) bootstrap and debug environment [ROMRAM]
    Release, version V1.04 - built 09:09:04, Aug 15 2008

    Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.

    Board: Rev 2
    RAM: 0x80000000-0x80800000, [0x8003b3a0-0x807e1000] available
    FLASH: 0xa8000000 - 0xa8800000, 128 blocks of 0x00010000 bytes each.
    == Executing boot script in 0.100 seconds - enter ^C to abort
    RedBoot> exec 0xa8030000
    Now booting linux kernel:
     Base address 0x80030000 Entry 0xa8030000
     Cmdline :
    trx at a8030000.
    kernel at a8031e74.
    Decompressing...done.
    [sighandler]: No more events to be processed, quitting.
    [cleanup]: Waiting for children.
    [cleanup]: All children terminated.
    - preinit -
    - init -
    init started:  BusyBox v1.4.2 (2009-11-10 10:29:31 CST) multi-call binary
    Starting pid 368, console /dev/ttyS0: '/etc/init.d/rcS'
    Starting PQ serial app. I can be reached via ssh at 172.22.2.104.

However, after loading the 8.09 image, redboot always hangs, failing to execute/find the kernel. See redboot below:

    RedBoot(tm) bootstrap and debug environment [ROMRAM]
    Release, version V1.04 - built 09:09:04, Aug 15 2008

    Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.

    Board: Rev 2
    RAM: 0x80000000-0x80800000, [0x8003b3a0-0x807e1000] available
    FLASH: 0xa8000000 - 0xa8800000, 128 blocks of 0x00010000 bytes each.
    == Executing boot script in 0.100 seconds - enter ^C to abort
    RedBoot> exec 0xa8030000
    Now booting linux kernel:
    Base address 0x80030000 Entry 0xa8030000
    Cmdline :

And hangs.......

Any feedback is greatly appreciated.