Results 1 to 7 of 7

Thread: Upgrading from 2.0.8-3 to 2.2 failed.

  1. #1
    kissas Guest

    Default Upgrading from 2.0.8-3 to 2.2 failed.

    I'have a pika at my office, i'see new image, so i want to upgrade.

    Code:
    ## Booting image at 02000000 ...
       Image Name:   Linux-2.6.26.5-pika
       Image Type:   PowerPC Linux Kernel Image (gzip compressed)
       Data Size:    1526467 Bytes =  1.5 MB
       Load Address: 00400000
       Entry Point:  00400684
       Verifying Checksum ... OK
       Uncompressing Kernel Image ... OK
    ## Loading RAMDisk Image at 02200000 ...
       Image Name:   PIKA Warp 2.0.8-3
       Image Type:   PowerPC Linux RAMDisk Image (gzip compressed)
       Data Size:    18325036 Bytes = 17.5 MB
       Load Address: 00000000
       Entry Point:  00000000
       Verifying Checksum ...
    the sd part its working good:

    Code:
    mmc0: new SD card at address a50d
    mmcblk0: mmc0:a50d SD02G 1985024KiB
    mmcblk0: p1
    uname result:
    Code:
    Linux warp 2.6.26.5-pika #16 Fri Aug 14 10:46:35 EDT 2009 ppc unknown
    but the fail.
    Code:
    AUTORUN: YES
    AUTORUN: persistent file system mounted successfully
    AUTORUN: Checking upgrade status.
    AUTORUN: Starting upgrade to version 2.2.1-1
    AUTORUN: Warploader utility from PADS version 2.1 or greater not found.
    AUTORUN: You must copy the file warploader from <Your PADS path>/images
    AUTORUN: to the upgrade directory /mnt/sd
    AUTORUN: Upgrade failed. Check the file upgrade-2.2.1-1.log for more information.
    and i'put the files under windows xp, to the sd, in windows i'see correct filenames, but under pika i see this:

    Code:
    /persistent/root # cd /mnt/sd/
    /mnt/sd # ls
    autorun       kernel~1.wrp  persis~2.wrp  ramdis~1.wrp  upgrade-.2
    fpga3011.wrp  persis~1.wrp  persis~3.wrp  u-boot~1.wrp  warplo~1
    how can solve this?
    best regards.

  2. #2
    kissas Guest

    Default

    i'dont know if this its correct but.
    if i do this :

    mv kernel~1.wrp 1234567890

    i get a new file with this name 12345678, there are some limitation with the long names? :S

  3. #3
    kissas Guest

    Default

    Ok, now i'have all done, i'used a netbook with ubuntu to transfer the files to the sd card, in ext2 format filesystem and its working.

    But now, i'not have FXS ports, only the 1, and i'have 4 more ...
    i'have 2 modules, 1 fxo and 1 fxs, but the phone ports are not working, y need to do some config to get working?

    Code:
    warp*CLI> pika show channels
    >>>>> Group: 0, type FXO: channels: 1 to 4
    PIKA Channel Asterisk Group: 0, type FXO: channels: 1 to 4
    Channel number: 1, asterisk group: 0 type: FXO, state = CHANNEL IS DOWN
    Channel number: 2, asterisk group: 0 type: FXO, state = CHANNEL IS DOWN
    Channel number: 3, asterisk group: 0 type: FXO, state = CHANNEL IS DOWN
    Channel number: 4, asterisk group: 0 type: FXO, state = CHANNEL IS DOWN
    >>>>> Group: 1, type FXS: channels: 1 to 1
    PIKA Channel Asterisk Group: 1, type FXS: channels: 1 to 1
    Channel number: 1, asterisk group: 1 type: FXS, state = CHANNEL IS READY
    >>>>> Group: 3, type AUDIO: channels: 1 to 1
    PIKA Channel Asterisk Group: 3, type AUDIO: channels: 1 to 1
    Channel number: 1, asterisk group: 0 type: AUDIO, state = CHANNEL IS READY

  4. #4
    kissas Guest

    Default

    i'see this in dmesg.

    Code:
    [   91.206575] 1.02: Spurious power alarm!
    [   91.210478] 1.03: Spurious power alarm!
    [   91.214340] 1.04: Spurious power alarm!
    [   91.218203] 1.05: Spurious power alarm!
    [   91.536477] 1: FXS 2 Reg b value 0 != 33 expected.
    [   91.541408] Revision of phone 2 Si3215 is 0.
    [   91.545748] 1: FXS 3 Reg 40 value ff != 0 expected.
    [   91.550698] 1: FXS 4 Reg b value ff != 33 expected.
    [   91.555655] Revision of phone 4 Si3215 is 0.
    [   91.560088] 1: FXS 5 Reg 40 value ff != 0 expected.
    [   91.778015] pkdummy: init() finished
    [  121.792491] 1: FXS 2 Reg b value ff != 33 expected.
    [  121.797479] Revision of phone 2 Si3215 is 0.
    [  121.801825] 1: FXS 3 Reg 40 value ff != 0 expected.
    [  121.806775] 1: FXS 4 Reg b value ff != 33 expected.
    [  121.811733] Revision of phone 4 Si3215 is 0.
    [  121.816074] 1: FXS 5 Reg 40 value ff != 0 expected.
    [  122.333486] 1: FXS 2 Reg b value ff != 33 expected.
    [  122.338501] Revision of phone 2 Si3215 is 0.
    [  122.342853] 1: FXS 3 Reg 40 value ff != 0 expected.
    [  122.347803] 1: FXS 4 Reg b value ff != 33 expected.
    [  122.352758] Revision of phone 4 Si3215 is 0.
    [  122.357094] 1: FXS 5 Reg 40 value ff != 0 expected.

  5. #5
    Join Date
    Jul 2008
    Posts
    268

    Default

    The problems seem to be only affecting the fxs module ports and not the on-board port. As a start, I would note the module revision as I believe module revisions of A.00, A.01 and A.02 could exhibit some of the symptoms that you are seeing. You can find the module revision on a sticker on the module.

    It could that you were previously using a older FPGA revision that did not exhibit the problem until you upgrade the FPGA software. A module rev of A.03/B.00 or greater is now required with newer FPGA versions. There is a bulletin on the subject here: http://forum.pikatechnologies.com/showthread.php?t=178

    Secondly, I would ensure the module is screwed down into the motherboard to provide proper grounding.

  6. #6
    kissas Guest

    Default

    ok, i'have rev a02, so i need a newer module, can buy the new module and then send the old one to repair?
    if that its correct to who i need to speak to buy the new one and send the old one later to repair/change?

    Best regards.

  7. #7
    Join Date
    Jul 2008
    Posts
    268

    Default

    I would recommend just sending a request to pika support and I am sure they would be happy to exchange the module for you.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •