Print

[pnhicks]

Hi Hennadii and Markishka,


We have been going to see the grandchildren everyday since the quarantine was lifted (we are Phase 1, family visits up to 10 people!), so I understand completely!


I just received a PM yesterday from Degers (a forum moderator) letting me know that the 1.0.2 updater is NOT compatible with WindowsXPsp3.  I had to use the updater for version Life OS 1.1 (it works in Virtual Box WindowsXPsp3 32 bit on my windows 10 64 bit machine).


Cheers!


Peter

[pnhicks]

Hi Guys,


I have staid inside all day (away from sunshine and grandchildren) working on this ........argh!


Anyway,  first some points


Inspite of what I was told, the USB updater for 1.0.2 DID run on WindowsXP SP3 (go figure), BUT it was not easy, but neither was trying to install a windowsXP sp2 which I never did get installed due to the stupid serial number checker.


However even though I got the congratulations screen shot just like I did on 1.1, see attached photos, it LOOKS like it only updated the default personality?


https://1drv.ms/u/s!As6F3Yo9RNKWvFbJcLDdCJHG-X3Q?e=t2MVaV
https://1drv.ms/u/s!As6F3Yo9RNKWvFVVjpvpwmzfGXkG?e=D9oiFg


Build type: RELEASE
  Pleo main ARM version: 7444 - Nov 30 2007 08:40:26
  Pleo head ARM version: 7361 - Nov 15 2007 21:34:25
  Pleo PM (DF) version: 7685 - Jan 14 2008 23:31:30
  Bootloader version: 7361 - Nov 15 2007 21:34:31
  Compiled in:   Thumb mode

I give up,  for today!

Peter

[pnhicks]

HI Guys,


Today, success!  After a small cheat!  Yesterdays attempt to use the USB updater to 1.0.2 left poor pleo in sad state.  I had to resort to SD card POP demo to "clear" his file system.  I suppose that I could have done the same thing with Pleo monitor.


The assumption on my part was that the 1.0.2 update via usb would do the same thing that the SD version appears to do (that it clears out previous OS versions before the install of the new version).  It DOES NOT if you have corrupted files on dataflash directory this updater apparently will not remove them.


After pop demo, the update ran again and pleo ran perfectly.


Have you tried the pop demo on your pleo?


It takes some time before you hear a short chime indicating that it is complete (I got quite worried that nothing was happening!)


Cheers!


Peter

[markishka]

Hi Peter

Thanks for your help with the experiments.



We tried both firmware (1.0.2 and 1.1) via USB. The installation was successful. But Pleo still doesn't work.


CONFIG in dinomite: (version 1.1)

Build Configuration:
  Firmware built for: Pleo
  Build type: RELEASE
  Pleo main ARM version: 8128 - Mar 19 2008 06:24:52
  Pleo head ARM version: 8128 - Mar 19 2008 06:25:46
  Pleo PM (DF) version: 0 - Jan 01 1970 00:00:00    (in version 1.0.2 also had such data here)
  Bootloader version: 8250 - May 20 2008 11:07:11
  Compiled in: Thumb mode
  Resource folders: on

Pleo PM (DF) version: 0 ...  means that the firmware is not working? For some reason could not update the default personality.



Serial number also look very odd. Before reflashing Serial number was 110401048778

Pleo Hardware Configuration:
  Hardware ID: 08060F0F-332F1F27-0100240B-FFFFFAFF (0F332FFA)
  Serial Number: 123456789ABC
  Board Revision: 17-8
  Board Revision ADC: 530



But there is more news. Pleo sometimes reacts when we move the position sensor or board in the back of the torso (just where the SD card is connecting). Rarely, but at least gives a chance.
Our Pleo opened his eyes and bent his legs. The voltage appears and disappears itself 

I'm checking which contacts I can move, clean, reconnect ... I feel that there is a mechanical problem somewhere.


There is no POP demo in the USB Updaters for Ugobe "Classic" Pleo section. Can't try because Pleo doesn't see the SD card.

[pnhicks]

Hi Guys,


I'm glad to help, sometimes silence makes me worried!


I really don't think the tilt sensor is a big player in the boot sequence (other than being on its side, pleo which forces pleo to look for an OS on the SD card).


My pleo booted fine with the tilt sensor removed!  It makes more sense (as you stated, that the mother board is not properly seated on the two daughter cards.


The motherboard connector for the tilt sensor is almost directly above the forward connection to the right hand daughter card.  The motherboard is secured to the chassis by two small screws with insulating washers.  One screw is very close to the tilt sensor connector.  Check to see if the screw is installed with the plastic washer and that it is not loose.


If the motherboard was forced down on to the daughtercards without the connectors being fully aligned, on or more on the pins on the daughtercard can be pushed down or bent over.


At the rear of the motherboard, there is a flat data cable that is pushed into a zero insertion force connection on the bottom of the motherboard.  The cable is clamped to rear of the forward chassis. 


It is very difficult to properly remove and reinstall without separating the pleo into front and rear halves.  Requires the removal of the ring at the bottom of the chassis. 


If this cable is damaged (the silver contacts on the bottom side of the cable peeling off from rough handling or inserted incorrectly, not inserted straight) then that might explain why the SD card doesn't work!

https://1drv.ms/u/s!As6F3Yo9RNKWvQS2wwUWpcKWGuk8?e=VO0kPs


It does look like you might be missing the OS on the dataflash, the firmware is there, but not the personality. If we get the SD working, the the POP demo should get us working!


Cheers!


Peter

[markishka]

Thanks, Piter.

I also think I need to look for why the SD card doesn't work.
I'm willing to take a risk and separate the pleo into front and rear halves.


I found another SD card (4GB) to try, loaded Static there.

The next connection to Dino-Mait have already show the correct Serial Number and
Pleo PM (DF) version: 8139 - Mar 24 2008 20:32:32


Please, help to decipher.

When turned on, Dynamite writes:

> INFO: nxp: 8128 - Mar 19 2008 06:25:46
INFO: nxp: Stack end:
INFO: nxp: 40001C1C
INFO: nxp: SRAM end:
INFO: nxp: 40001490
INFO: nxp: SRAM remaining:
INFO: nxp: 0000078C
INFO: low: Turning on head sensors.
INFO: low: object tx=1, speed=100
INFO: high: hl_init()
LL SHUTDOWN: TEMPERATURE = 62!
Shake sensor is active.
POWERING DOWN!
INFO: high: hl_unload(<cwd>,powerdown:0,downtime:0)
INFO: high: application: No App loaded.
WARN: high: No application loaded. Pointless unload request.
INFO: high:
INFO: low: motion: Initializing motion control subsystem
INFO: low: motion: MotorController 0 firmware version 28
INFO: low: motion: MotorController 0 comms test passed
INFO: low: motion: MotorController 0 A/D filter K=1 N=2
INFO: low: motion: MotorController 0 outputs set to P00=1, P01=0
INFO: low: motion: MotorController 1 firmware version 28
INFO: low: motion: MotorController 1 comms test passed
INFO: low: motion: MotorController 1 A/D filter K=1 N=2
INFO: low: motion: MotorController 1 outputs set to P00=1, P01=0
INFO: low: motion: MotorController 2 firmware version 28
INFO: low: motion: MotorController 2 comms test passed
INFO: low: motion: MotorController 2 A/D filter K=1 N=2
INFO: low: motion: MotorController 2 outputs set to P00=1, P01=0
INFO: low: motion: MotorController 3 firmware version 28
INFO: low: motion: MotorController 3 comms test passed
INFO: low: motion: MotorController 3 A/D filter K=1 N=2
INFO: low: motion: MotorController 3 outputs set to P00=1, P01=0
INFO: low: motion: Successfully loaded calibration data from dataflash.
INFO: low: motion: ident | calibration  |  PID constants    |
INFO: low: motion: joint  low zero upper kp ki kd kf kni kdb
INFO: low: motion:     0  63  122   228 70 35  0  0  16   4
INFO: low: motion:     1  61   63   170 50 20  0  0  16   4
INFO: low: motion:     2  61  122   228 70 35  0  0  16   4
INFO: low: motion:     3  61   63   174 50 20  0  0  16   4
INFO: low: motion:     4  43  118   202 50 100  0  0  12   4
INFO: low: motion:     5  72  178   178 70 20  0  0  10   4
INFO: low: motion:     6  46  123   201 50 100  0  0  12   4
INFO: low: motion:     7  69  182   182 70 20  0  0  10   4
INFO: low: motion:     8  96  123   141 80 40  0  0  10   4
INFO: low: motion:     9  23  122   227 40 90  0  0   8   4
INFO: low: motion:    10  19  131   226 75 50  0  0  24   4
INFO: low: motion:    11  23  124   222 80 50  0  0  32   4
INFO: low: motion:    12  18  142   227 60 30  0  0  32   4
INFO: low: motion:    13  67  125   224 40 35  0  0   8   4
INFO: low: motion: Acroname MotorControllers present and functioning.  Enabling motion control system.
WARN: low: res: stats: CRC failure... ignoring; calculated: 0x88AE, stored:


Maybe something important is reporting.  CRC failure... and  POWERING DOWN! 
But I do not understand what the problem is. At battery temperature? What is a CRC ?

[markishka]

Another 2 non-working Pleos appeared on sale at a ridiculously low price. It makes only a sound when turned on, maybe it has a better chance of starting up with our new battery. I`m thinking about a purchase.
I have two children, it would be great to repaired all Pleos 

[pnhicks]

Hi Guys,

Take care with the size of the SD card (did you hear the Pleo say "Dinomite- Static").  That's how you know its running the Skit on the SD card. The wav file is played, and the pleo goes into the "neutral pose" or "packing position" and should not move again.

The early firmware did not recognize large sd cards (I would stay with 1GB or less)  unless you are sure that the skit is running.

The low level warning (LL SHUTDOWN) is telling you that the low level part of the OS has detected a problem that is serious enough that the OS is directing a shutdown. 

In this case apparent, it was for a battery overheat detection.  There is a skit (if your sd card is working, to disable the battery heat detection) on the forum.

Cyclic redundancy check (CRC) is an error-detecting code commonly used in digital storage devices to detect accidental changes to raw data. Blocks of data entering these systems get a short check value attached, based on a mathematical calculation made on its contents.

On retrieval, the calculation is repeated and, in the event the check values do not match a error is generated. The Cyclic Redundancy Check (CRC) Error indicates data was changed in the process of being retrieved from storage.

The good news, in our case is that the OS happily ignored the error and produced a new check value and stored it:  "CRC failure... ignoring; calculated: 0x88AE, stored"

Hope this helps!

Peter

[pnhicks]

Hi Guys,


Here is an Image to help understand a little better where the messages are coming from during boot up:

https://1drv.ms/u/s!As6F3Yo9RNKWvQ1gJ5XqKSUS5yh0?e=DtKcw5


Cheers!

Peter

[markishka]

Hi Peter!

We bought 2 pleo. One of them is in very good condition, from the last classic pleo not RB (already produced by Innvo). The second has a very worn skin, but Pleo works. There is also a small breakdown on the neck. Also it will be necessary to do repairs.

We managed to reflash through the SD card without problems. I was not sure whether it was possible to lower the firmware immediately (the one that was newer had 2.0). Therefore, before this, we decided to resort to SD card POP demo.

Children are very happy!   I’m thinking up different options with batteries.

Now I will continue to repair our first Pleo. I will already be more bold to disassemble it, look for the reason why it does not accept the SD card, etc. I believe that it will work.

[pnhicks]

Hi Guys


Perhaps an expensive option, but at least the kids are happy!


Good luck on future repairs!


Peter