This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SG135 C2000 BUG

Hello, I recently bought a used SG135 rev.1 which has AVR54 bug (I found out about this bug after I buy it).

For others vendors I found a possible fix, but not for Sophos.

There are two (as far as I know) fixes:

1. Replace a atom c2xxx with C0 revision

2. external pull-up resistor (18.2k to 10k), from LPC_CLKOUT0 or LPC_CLKOUT1, tied to 3.3V

Did someone tried to fix this bug? (I use home license, so I don't have any agreement with Sophos).

 

Best regards,

  Robert

 

 

 



This thread was automatically locked due to age.
Parents
  • I tried it myself this weekend and I have mixed results....

     

    Yes my Sophos Boots up again and is able to install an operating system.

    But, reboots are a big issue.

    After a reboot the box does not come up again, you have to plug out the power supply and/or pull the cmos battery that it comes back on after a simple reboot... 

    The clockgenerator 'fix' (it is not a fix its a cheap workaround around the problem itself)  does not really work well with my device, though its able to boot again...

     

    HM

     

Reply
  • I tried it myself this weekend and I have mixed results....

     

    Yes my Sophos Boots up again and is able to install an operating system.

    But, reboots are a big issue.

    After a reboot the box does not come up again, you have to plug out the power supply and/or pull the cmos battery that it comes back on after a simple reboot... 

    The clockgenerator 'fix' (it is not a fix its a cheap workaround around the problem itself)  does not really work well with my device, though its able to boot again...

     

    HM

     

Children
No Data