Communication and loading issues with v2.3

hidish
Posts: 9
Joined: Wed Jun 08, 2011 9:51 am

Communication and loading issues with v2.3

Post by hidish » Tue Oct 15, 2013 10:57 am

I had recently updated Configuration Studio to 2.3.20006. When trying to load using the ethernet adapter, the application stated that I needed to have the new bootloader. I updated the bootloader that is in the forum (2.3.20019). The bootloader shows up fine, but I cannot load any configurations to my PV450 that I use for development. The communications will not work over the ethernet adapter. When I try to load a non-full install from a usb drive, I get the 404 error. When I try to load a full-install from a usb drive, it looks like it takes, but then reboots back to the bootloader screen. I can test my software using another device with an older bootloader, but only by copying to usb and loading that way. Can you give me some advice?

-Andrew
hidish
Posts: 9
Joined: Wed Jun 08, 2011 9:51 am

Re: Communication and loading issues with v2.3

Post by hidish » Tue Oct 15, 2013 1:18 pm

UPDATE:

I tried a different display and followed the steps for updating and it looks to be working now. I don't know if there is something with the one particular unit that I tried initially, but it seems to work now with a different one.
ecarmen
Murphy Representative
Murphy Representative
Posts: 8
Joined: Mon Sep 13, 2010 10:47 am

Re: Communication and loading issues with v2.3

Post by ecarmen » Wed Oct 16, 2013 5:16 pm

To update a display to the latest version the process should be as follows:
1) Update Powervision 2.3 or 2.6 with the latest patch
2) Create a full install of your configuration and copy it to a thumb drive
3) Copy the new loader to the thumb drive
4) Install the new loader first then install the full config

Error code 404 indicates the file you are loading is not of the new file system type with Error Correction Code (ECC)
The first time programing a display you need to load a full install via the thumb drive so all the necessary OS components are included for the ECC file system.

Here is a list of the loader error codes:
- 300 – Password flag read error
- 301 – Invalid file: password flag
- 302 – Security error: Unsecured file on a secured unit
- 303 – Part Number Match failed
- 304 – Corrupted tar file
- 305 – Load for different display type (.tar)
- 306 – Load for different display type (.gciBin)
- 307 – Unknown file extension
- 308 – Not a post ECC corrected load
- 309 – Password incorrect
- 401 – Corrupted tar file
- 402 – Unknown hardware family
- 403 - Corrupted load file - no scrip
- 404 – Not a post ECC corrected load