Search

Technical Discussion Group Forum

This forum is provided for user discussion. While Logic PD support staff and engineers participate, Logic PD does not guarantee the accuracy of all information within in the Technical Discussion Group (TDG).

The "Articles" forums provide brief Articles written by Logic PD engineers that address the most frequently asked technical questions.

To receive email notifications when updates are posted for a Logic PD product download, please subscribe to the TDG Forum of interest.

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 09 Jan 2008 09:20 AM by  GG1
MPC8360-RDK Appears dead after Ramdisk Deployment
 17 Replies
Sort:
You are not authorized to post a reply.
Author Messages
GG1
New Member
New Member
Posts:


--
17 Dec 2007 07:29 AM

    Can I get some guidance on my situation.

    I managed to make my MPC8360-RDK console go quite and I currently get no console output after I performed the following:

    I configured UBOOT with the ipaddr,serverip, gatewayip,ethaddr,netmask,loadaddr,bootfile,ftdfile,ftdfile, ramdiskfile,ramdiskaddr,ramboot,bootcmd and saved the environment and successfully loaded it as per Linux BSP User Manual 1085444 Rev.2. 12/2007.

    The images loaded were successfully built uImage, dtb and ramdisk images from my build and tftp server with the ISO distribution posted Dec 12/07 using the tlib tool.

    I cycled the power and get no U-Boot Console.

    Here is the last U-boot console record:

    => reset
    Resetting the board.


    U-Boot 1.1.3 R6 (Oct 2 2007 - 16:13:46) MPC83XX

    Clock configuration:
    Coherent System Bus: 330 MHz
    Core: 660 MHz
    QE: 495 MHz
    Local Bus Controller: 330 MHz
    Local Bus: 41 MHz
    DDR: 330 MHz
    DDR Secondary: 330 MHz
    SEC: 110 MHz
    I2C1: 330 MHz
    I2C2: 330 MHz
    CPU: MPC8360E, Rev: 21 at 660 MHz
    RCW: 0xA0600004 0x0A04008F
    Board: Freescale MPC8360 Com Express - Pilot
    I2C: ready
    DRAM: DDR 256 MB
    FLASH: 8 MB
    Read production data: done
    Part Number: 1008393
    Model Name : COMMPC8360E-10-2752FCR
    Model Rev : A
    Serial # : 4007M02112
    board_get_nth_enetaddr:1093 which 1 1:ad:95
    board_get_nth_enetaddr:1093 which 2 1:ad:96
    board_get_nth_enetaddr:1093 which 3 1:ad:97
    Using external PCI clock
    PCI 32bit
    In: serial
    Out: serial
    Err: serial
    NAND: 64 MB
    Net: FSL GETH0
    Hit any key to stop autoboot: 0
    geth: PHY is Broadcom 5481 (143bca2)
    FSL GETH0: Full Duplex
    switching to rgmii 100
    FSL GETH0: Speed 100BT
    FSL GETH0: Link is up
    Using FSL GETH0 device
    TFTP from server 10.33.88.87; our IP address is 192.168.0.103; sending through gateway 192.168.0.1
    Filename '/simdir/grayg/cxi_ppc-linux/ltib-mpc8360-com-express-20071211/images/uImage'.
    Load address: 0x200000
    Loading: #################################################################
    #################################################################
    #################################################################
    #################################################################
    #############################
    done
    Bytes transferred = 1475199 (16827f hex)
    Using FSL GETH0 device
    TFTP from server 10.33.88.87; our IP address is 192.168.0.103; sending through gateway 192.168.0.1
    Filename '/simdir/grayg/cxi_ppc-linux/ltib-mpc8360-com-express-20071211/images/rootfs.ext2.gz.uboot'.
    Load address: 0x1000000
    Loading: #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #####################################
    done
    Bytes transferred = 5844317 (592d5d hex)
    Using FSL GETH0 device
    TFTP from server 10.33.88.87; our IP address is 192.168.0.103; sending through gateway 192.168.0.1
    Filename '/simdir/grayg/cxi_ppc-linux/ltib-mpc8360-com-express-20071211/images/mpc8360ece.dtb'.
    Load address: 0x400000
    Loading: ##
    done
    Bytes transferred = 9798 (2646 hex)
    ## Booting image at 00200000 ...
    Image Name: Linux-2.6.19
    Image Type: PowerPC Linux Kernel Image (gzip compressed)
    Data Size: 1475135 Bytes = 1.4 MB
    Load Address: 00000000
    Entry Point: 00000000
    Verifying Checksum ... OK
    Uncompressing Kernel Image ... OK
    ## Loading RAMDisk Image at 01000000 ...
    Image Name: uboot ext2 ramdisk rootfs
    Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
    Data Size: 5844253 Bytes = 5.6 MB
    Load Address: 00000000
    Entry Point: 00000000
    Verifying Checksum ... OK
    Loading Ramdisk to 0fa11000, end 0ffa3d1d ... OK
    peter.barada@logicpd.com
    New Member
    New Member
    Posts:72


    --
    17 Dec 2007 08:43 AM
    Are you saying that after trying to boot hte kernel, and then power-cycle the board, there's no output on the serial line(i.e. no U-boot banner)?

    Do the LEDs blink at all after reset?
    GG1
    New Member
    New Member
    Posts:


    --
    17 Dec 2007 08:58 AM
    Quote:
    Are you saying that after trying to boot hte kernel, and then power-cycle the board, there's no output on the serial line(i.e. no U-boot banner)?

    Do the LEDs blink at all after reset?


    Yes and No Blinking LEDs. I just have Green PWR and Red 5VSB LEDs
    peter.barada@logicpd.com
    New Member
    New Member
    Posts:72


    --
    18 Dec 2007 11:01 AM
    Weird - totally weird...

    I'd expect the kernel to not come up since the 2.6.19 kernel requires u-boot-1.1.6 or newer, not a dead board.

    Do you have a JTAG debugger you can use to reprogram u-boot on the board?
    GG1
    New Member
    New Member
    Posts:


    --
    18 Dec 2007 11:25 AM
    Quote:
    Weird - totally weird...

    I'd expect the kernel to not come up since the 2.6.19 kernel requires u-boot-1.1.6 or newer, not a dead board.

    Do you have a JTAG debugger you can use to reprogram u-boot on the board?


    I agree, totally weird!

    You know I should of taken the document's recomendation as indicated in
    MPC8360E-RDK Linux BSP User Manual 5.2 Flashing U-Boot

    We Recommed you flash the U-Boot located on your CD in ...

    Too late now!

    I have a Code Warrior USB TAP, which came with my MPC8360E-RDK box. I'm now looking into software and licenses to use it. I see documentation supporting a BDI-2000 by Abatron.

    Can you get me instructions on programming U-Boot using the USB TAP?
    peter.barada@logicpd.com
    New Member
    New Member
    Posts:72


    --
    18 Dec 2007 12:18 PM
    Yah, I kinda wish that reccomendation was more of a "severe" hint - I'll update the documentation to indicate the first step is to update u-boot.

    I've never used a USB TAP before(I'm an Abatron fan). The TAP should have documentation on how to use it, hopefully enough directions to allow you to reflash the first two sectors(256KB) of NOR flash...
    GG1
    New Member
    New Member
    Posts:


    --
    18 Dec 2007 03:10 PM
    <!-- s:o -->:o<!-- s:o --> I have access to a BDI-2000 for ARM, can I use this to flash the u-boot.bin on the MPC8360E-RDK NOR device and would I need licensing to use it for this task?
    peter.barada@logicpd.com
    New Member
    New Member
    Posts:72


    --
    18 Dec 2007 07:37 PM
    Unfortunately no.

    You'd need the Abatron PPC firmware to do that. The JTAG stream is quite different between the ARM and PPC cores...
    mikee@logicpd.com
    New Member
    New Member
    Posts:


    --
    19 Dec 2007 01:45 PM
    GG1,

    Where are you located? Are you in the continental USA?

    Please contact me, Michael Erickson via:

    (612) 436-5118 - desk
    mailto:mikee@logicpd.com

    I will see if we can't just take care of this for you.

    --mikee
    GG1
    New Member
    New Member
    Posts:


    --
    20 Dec 2007 08:26 AM
    While I was blocked waiting for CW tools to re-flash U-boot I did some browsing of the ltib logfiles. I think my UBOOT, linux kernel, filesystem and DTB builds didn't have all the patches correctly installed for Release tag: ltib-mpc8360-com-express-20071211. I also had to de-select microwindows support in-order to get the build to complete successfully.

    Here what the RELEASE_INFO and RELEASE_COPY_CONTEXT logs:

    release_logs [184]> more RELEASE_INFO
    Release date = Tue Dec 11 19:20:35 2007 UTC
    Release user = peter
    Release host = blackhole
    Release dir = /home/peter/work/logic/mpc8360-ltib/ltib-mpc8360epb-20070717
    CVS wtag = none
    CVS tag = localdir_nobuild
    Release tag = ltib-mpc8360-com-express-20071211
    App version = 7.2.1
    CVS version = 1.283
    grayg@rndlx018 release_logs [185]> more RELEASE_COPY_CONTENT
    find_all_selectable toolchain: mtwk-lnx-powerpc-gcc-3.4.3-glibc-2.3.3-0.28-1.i686.rpm
    find_all_selectable toolchain: tc-fsl-x86lnx-ppc-uclibc-3.4.3-1.i386.rpm
    find_all_selectable toolchain: tc-fsl-x86lnx-ppc-nptl-4.0.2-3.i386.rpm
    find_all_selectable toolchain: freescale-powerpc-linux-gnu-4.1-69.i686.rpm
    find_all_selectable bootloaders: u-boot-1.1.3-mpc8360e-com-express
    find_all_selectable bootloaders: u-boot-1.1.6-mpc8360e-com-express
    find_all_selectable kernels: kernel-2.6.11-mpc8360e-com-express
    find_all_selectable kernels: kernel-2.6.19-mpc8360e-com-express
    find_all_selectable kernels: kernel26-dir-build



    Checking licensing and external availabity of sources
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    The following constraints/checks are enforced:

    1/ All source/patches in the default configuration must be distributable.

    2/ Any sources/patches not in the default configuration that are not
    distributable are not be copied to the ISO image.

    3/ Any content copied to the ISO image has it's md5 checksum verified by
    downloading a fresh copy of the md5sum file and using it to verify the
    content it checksums.

    4/ Files already present on local disk in the LPP will be used. Any
    missing files will be downloaded from either the GPP staging area
    or the CPP (Clickthru) staging area.

    ------------------------


    Copying content from default configuration (mandatory)
    ---------------------------------------------------------

    checking: toolchain
    ====================
    Testing network connectivity
    OK GPP_STAGE:
    FAILED CPP_STAGE: : 500 Can't connect to auslxsc02.mtwk.freescale.net:80 (Bad hostname 'auslxsc02.mtwk.freescale.net')
    OK LPP_STAGE:

    OK GPP_STAGE: mtwk-lnx-powerpc-gcc-3.4.3-glibc-2.3.3-0.28-1.i686.rpm

    checking: fake-provides
    =========================
    License: GPL

    checking: u-boot-1.1.6-mpc8360e-com-express
    =============================================
    License: GPL
    OK GPP_STAGE: u-boot-1.1.6.tar.bz2
    OK GPP_STAGE: u-boot-1.1.6-fsl-1-mpc83xx-20061206.patch
    FAILED GPP_STAGE: u-boot-1.1.6-mpc8360ece-1.patch: 404 Not Found
    FAILED CPP_STAGE: u-boot-1.1.6-mpc8360ece-1.patch: 500 Can't connect to auslxsc02.mtwk.freescale.net:80 (Bad hostname 'auslxsc02.mtwk.frees
    cale.net')
    OK LPP_STAGE: u-boot-1.1.6-mpc8360ece-1.patch
    FAILED GPP_STAGE: u-boot-1.1.6-mpc8360ece-2.patch: 404 Not Found
    FAILED CPP_STAGE: u-boot-1.1.6-mpc8360ece-2.patch: 500 Can't connect to auslxsc02.mtwk.freescale.net:80 (Bad hostname 'auslxsc02.mtwk.frees
    cale.net')
    OK LPP_STAGE: u-boot-1.1.6-mpc8360ece-2.patch
    FAILED GPP_STAGE: u-boot-1.1.6-mpc8360ece-3.patch: 404 Not Found

    ...
    GG1
    New Member
    New Member
    Posts:


    --
    21 Dec 2007 11:24 AM
    I've got CodeWarrior USB TAP and software going today. I was about to break into the CORE with available initialization files. I managed to erase the first two sectors of U6 NOR FLASH, but now I can't break into the CORE because the debugger can't stop the CORE after I reset it.


    Is there a way to set a default configuration to allow a JTAG debugger to work when the H/W configuration in FLASH is lost for the MPC8360-RDK board?
    nathank
    New Member
    New Member
    Posts:11


    --
    21 Dec 2007 12:19 PM
    GG1,

    You need to set up your USB TAP to override the Reset Configuration Words (RCW). Please see the help/documentation for the USB TAP for how to do this.
    The MPC8360-RDK is setup to automatically load the RCW from the first few bytes in NOR Flash. Since you have erased this, the processor reads in all 0xFF's for the RCW and does not setup the clocks properly. The following is how the words should be setup:
    RCWH = 0xA0600004 RCWL = 0x0A04008F

    Hope this helps.
    GG1
    New Member
    New Member
    Posts:


    --
    21 Dec 2007 02:14 PM
    nathank

    Thanks!


    I was able to configure the CodeWarrior USB TAP with your values and successfully connected with an erased NOR FLASH.

    I had to create an Initialization file under the jtag_chains tree with:

    # HRCW for low boot
    E300 (1 1) (2 0x0A04008F) (3 0xa0600004)

    I then performed the following from CodeWarrior IDE

    Edit
    Debug Version Setttings
    Remote Debugging
    Connection: CodeWarrior USB TAP
    Edit Connection
    Use JTAG Configuration file

    It on to trying to FLASH it with U-Boot.bin
    mikee@logicpd.com
    New Member
    New Member
    Posts:


    --
    02 Jan 2008 10:12 AM
    Gordon,

    I just wanted to follow up on your concerns regarding the patch-errors you reported.

    LTIB uses three different "pools" of patches; global (GPP), local (LPP), and private (CPP).

    You won't ever be able to get patches out of the private pool as it is only accessible from within Freescale's network. Hence this error that you reported below:

    Posted By GG1 on 31 Dec 1969 6:0 PM
    ...
    checking: toolchain
    ====================
    Testing network connectivity
    OK GPP_STAGE:
    FAILED CPP_STAGE: : 500 Can''t connect to auslxsc02.mtwk.freescale.net:80 (Bad hostname ''auslxsc02.mtwk.freescale.net'')
    OK LPP_STAGE:




    As you can see, the error is letting you know that it cannot connect to a machine named auslxsc02.mtwk.freescale.net - again, because you aren't inside Freescale's private network.

    The other errors you reported are LTIB telling you that it was looking for patches but instead of finding them in the global or private patch pools (GPP and CPP), it found them in the local patch pool (LPP).

    Posted By GG1 on 20 Dec 2007 8:26 AM

    FAILED GPP_STAGE: u-boot-1.1.6-mpc8360ece-1.patch: 404 Not Found
    FAILED CPP_STAGE: u-boot-1.1.6-mpc8360ece-1.patch: 500 Can''t connect to auslxsc02.mtwk.freescale.net:80 (Bad hostname ''auslxsc02.mtwk.frees
    cale.net'')
    OK LPP_STAGE: u-boot-1.1.6-mpc8360ece-1.patch




    In that error, LTIB was looking for a patch named u-boot-1.1.6-mpc8360ece-1.patch. It first looked in the global patch pool (GPP) and didn't find it there. Then it looked for the patch in the private patch pool (CPP) - but couldn't connect. Finally, it found the patch in the local patch pool (LPP).

    So, errors like that should be fine and not indicative of any problems with your install.

    However, I am concerned about your statement regarding it being necessary for you to disable microwindows. Can you please confirm that that truly is the case? Or, perhaps you could simply send the entire build log output from trying to do a microwindows enabled build?

    Thanks,
    --mikee
    GG1
    New Member
    New Member
    Posts:


    --
    02 Jan 2008 03:25 PM
    Thanks Mike for explaination on the "pools" of patches.

    I'll post more information on the mircowindows build problem I having shortly.

    Gord
    GG1
    New Member
    New Member
    Posts:


    --
    07 Jan 2008 06:05 PM
    Mike:

    I'm still having trouble getting my MPC8360E-RDK to come up wilth Linux using the default images. I need some more ideas.

    I've managed to re-flash my evaluation board with CW and USB TAP. I'm using the u-boot.bin provided with:

    -rwxr--r-- 1 grayg mantis 686483456 Dec 13 08:40 ltib-mpc8360-com-express-20071211.iso

    And I'm also setting up my uboot environment to use the following other default iimages:

    -r--r--r-- 1 root root 9798 Dec 11 14:26 mpc8360ece.dtb
    -r--r--r-- 1 root root 5844317 Dec 11 14:26 rootfs.ext2.gz.uboot
    -r-xr-xr-x 1 root root 203836 Dec 11 14:26 u-boot.bin
    -r--r--r-- 1 root root 1475199 Dec 11 14:26 uImage

    Here what my uboot console shows:
    U-Boot 1.1.6r1 (Dec 6 2007 - 14:27:57) MPC83XX

    Clock configuration:
    Coherent System Bus: 330 MHz
    Core: 660 MHz
    QE: 495 MHz
    Local Bus Controller: 330 MHz
    Local Bus: 82 MHz
    DDR: 330 MHz
    DDR Secondary: 330 MHz
    SEC: 110 MHz
    I2C1: 330 MHz
    I2C2: 330 MHz
    CPU: MPC8360E, Rev: 21 at 660 MHz
    RCW: 0xB0600004 0x0A04000F
    Board: Freescale MPC8360E Com Express - Pilot
    I2C: ready
    DRAM: DDR 256 MB
    FLASH: 8 MB
    NAND: 64 MB
    Read production data: done
    Part Number: 1008393
    Model Name : COMMPC8360E-10-2752FCR
    Model Rev : A
    Serial # : 4007M02112
    PCI clock is 33MHz
    PCI 32bit bus
    In: serial
    Out: serial
    Err: serial
    U-Boot relocated to 0ffc7000
    Net: UEC0: PHY is Broadcom 5481 (143bca2)
    UEC0: Full Duplex
    switching to rgmii 100
    UEC0: Speed 100BT
    UEC0: Link is up
    UEC0
    Hit any key to stop autoboot: 0
    Using UEC0 device
    TFTP from server 10.33.88.87; our IP address is 192.168.0.103; sending through gateway 192.168.0.1
    Filename '/simdir/grayg/cxi_ppc-linux/MPC8360E-RDK_Eval/Dec_13_07/ltib-mpc8360-com-express-20071211/images/uImage'.
    Load address: 0x200000
    Loading: #####################T ############################################
    ###############################################T ##################T
    #####################T #####################T #######################
    ########T #########################################################T
    #############################
    done
    Bytes transferred = 1475199 (16827f hex)
    Using UEC0 device
    TFTP from server 10.33.88.87; our IP address is 192.168.0.103; sending through gateway 192.168.0.1
    Filename '/simdir/grayg/cxi_ppc-linux/MPC8360E-RDK_Eval/Dec_13_07/ltib-mpc8360-com-express-20071211/images/rootfs.ext2.gz.uboot'.
    Load address: 0x1000000
    Loading: #################################################################
    ##################################T #############################T ##
    ##########################T ###################################T ####
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    ############################T ###########T ################T ##########
    #################################################################
    #################################################################
    ##########################################T ##############T #########
    ###############T ##################################################
    #################################################################
    ################################################T #################
    #T ################################################################
    ########T #########################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #######################T ##########################################
    #################################################################
    ###########################T ######################################
    #################################################################
    #####################################
    done
    Bytes transferred = 5844317 (592d5d hex)
    Using UEC0 device
    TFTP from server 10.33.88.87; our IP address is 192.168.0.103; sending through gateway 192.168.0.1
    Filename '/simdir/grayg/cxi_ppc-linux/MPC8360E-RDK_Eval/Dec_13_07/ltib-mpc8360-com-express-20071211/images/mpc8360ece.dtb'.
    Load address: 0x400000
    Loading: ##
    done
    Bytes transferred = 9798 (2646 hex)
    ## Booting image at 00200000 ...
    Image Name: Linux-2.6.19
    Image Type: PowerPC Linux Kernel Image (gzip compressed)
    Data Size: 1475135 Bytes = 1.4 MB
    Load Address: 00000000
    Entry Point: 00000000
    Verifying Checksum ... OK
    Uncompressing Kernel Image ... OK
    ## Loading RAMDisk Image at 01000000 ...
    Image Name: uboot ext2 ramdisk rootfs
    Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
    Data Size: 5844253 Bytes = 5.6 MB
    Load Address: 00000000
    Entry Point: 00000000
    Verifying Checksum ... OK
    Loading Ramdisk to 0fa11000, end 0ffa3d1d ... OK
    GG1
    New Member
    New Member
    Posts:


    --
    07 Jan 2008 07:48 PM
    Mike,

    Below is the microwindow build error. sorry for the delay.

    Gord

    Processing: microwindows
    ==========================
    rpmbuild --dbpath /simdir/grayg/cxi_ppc-linux/ltib-mpc8360-com-express-20071211/rpmdb --define '_unpackage
    d_files_terminate_build 0' --define '_target_cpu ppc' --define '__strip strip' --define '_topdir /simdir/g
    rayg/cxi_ppc-linux/ltib-mpc8360-com-express-20071211/rpm' --define '_prefix /usr' --define '_tmppath /simd
    ir/grayg/cxi_ppc-linux/ltib-mpc8360-com-express-20071211/tmp' --define '_mandir /usr/share/man' --define '
    _sysconfdir /etc' --define '_localstatedir /var' -bc --short-circuit /simdir/grayg/cxi_ppc-linux/ltib-mpc
    8360-com-express-20071211/dist/lfs-5.1/microwindows/microwindows.spec
    Executing(%build): /bin/sh -e /simdir/grayg/cxi_ppc-linux/ltib-mpc8360-com-express-20071211/tmp/rpm-tmp.22
    642
    + umask 022
    + cd /simdir/grayg/cxi_ppc-linux/ltib-mpc8360-com-express-20071211/rpm/BUILD
    + cd microwindows-0.90
    + cd src
    + make -j1 'HOSTCC=/usr/bin/gcc -B/usr/bin//'
    make -C drivers
    make[1]: Entering directory `/simdir/grayg/cxi_ppc-linux/ltib-mpc8360-com-express-20071211/rpm/BUILD/micro
    windows-0.90/src/drivers'
    make[1]: Leaving directory `/simdir/grayg/cxi_ppc-linux/ltib-mpc8360-com-express-20071211/rpm/BUILD/microw
    indows-0.90/src/drivers'
    make -C mwin
    make[1]: Entering directory `/simdir/grayg/cxi_ppc-linux/ltib-mpc8360-com-express-20071211/rpm/BUILD/micro
    windows-0.90/src/mwin'
    make -C bmp
    make[2]: Entering directory `/simdir/grayg/cxi_ppc-linux/ltib-mpc8360-com-express-20071211/rpm/BUILD/micro
    windows-0.90/src/mwin/bmp'
    echo "Generating min4.c from bitmap file ..."
    Generating min4.c from bitmap file ...
    /simdir/grayg/cxi_ppc-linux/ltib-mpc8360-com-express-20071211/rpm/BUILD/microwindows-0.90/src/bin/convbmp
    -o min4.c min4.bmp
    make[2]: *** [min4.c] Segmentation fault (core dumped)
    make[2]: *** Deleting file `min4.c'
    make[2]: Leaving directory `/simdir/grayg/cxi_ppc-linux/ltib-mpc8360-com-express-20071211/rpm/BUILD/microw
    indows-0.90/src/mwin/bmp'
    make[1]: *** [subdir-bmp] Error 2
    make[1]: Leaving directory `/simdir/grayg/cxi_ppc-linux/ltib-mpc8360-com-express-20071211/rpm/BUILD/microw
    indows-0.90/src/mwin'
    make: *** [subdir-mwin] Error 2
    error: Bad exit status from /simdir/grayg/cxi_ppc-linux/ltib-mpc8360-com-express-20071211/tmp/rpm-tmp.2264
    2 (%build)


    RPM build errors:
    Bad exit status from /simdir/grayg/cxi_ppc-linux/ltib-mpc8360-com-express-20071211/tmp/rpm-tmp.22642 (
    %build)
    Build time for microwindows: 0 seconds

    Failed building microwindows


    f_buildrpms() returned an error, exiting

    Started: Mon Jan 7 21:05:43 2008
    Ended: Mon Jan 7 21:22:19 2008
    Elapsed: 996 seconds

    These packages failed to build:
    microwindows
    Build Failed

    Exiting on error or interrupt
    GG1
    New Member
    New Member
    Posts:


    --
    09 Jan 2008 09:20 AM
    Quote:
    Mike:

    I'm still having trouble getting my MPC8360E-RDK to come up wilth Linux using the default images. I need some more ideas.


    Mike,

    I got linux to come up!

    I found I need to burn the Device Table Binary into flash and set the third bootm parameters to the flash address. Using it from RAM with the third bootm parameter for RAM will not work.

    I see the NFS deployment instructions doesn't indicate Device Table Binary to be burned in flash. Is this a problem for this deployment? I got this deployment to start linux if I used the burned DTB.

    I received a Email on Jan 4/08 of an updated MPC8260E-RDK Linux BSP User Manual. The Email indicates:
    The "MPC8360E-RDK Linux BSP User Manual" document has been updated. You
    can download this document at:
    http://www.logicpd.com/do...44Rev2_MPC8360E-RDK_
    Linux_BSP_UM.pdf

    This is the same document I have been using from the Dec 11/07 release. I manage to find 1008544, REV A, 1/2008 MPC8360E-RDK Linux BSP User Manual through http://www.logicpd.com.

    The same Email indicates a new LTIB Linux BSP image has been released. This also indicates the same iso image that I am currently using. The email indicates:

    An updated LTIB Linux BSP image has been released for the MPC8360E COM
    Express SOM and posted to the downloads page. The .zip file can be
    downloaded at:
    http://www.logicpd.com/do...mpc8360-com-express-
    20071211.iso

    Question: Is there a new ISO release and do I need it to successfully make a 2.6.19 kernel that will work for me?

    I am still unable get linux to come up with the uImage I build with microwindows disabled. I still need help here.

    Thanks,
    Gord
    You are not authorized to post a reply.