Difference between revisions of "Psp2-updatelist.xml"

From Vita Dev Wiki
Jump to navigation Jump to search
Line 5: Line 5:
  
 
When this is read by the system the <code>region id</code> MUST match the system region.  
 
When this is read by the system the <code>region id</code> MUST match the system region.  
possible regions are: <code>jp</code>, <code>us</code>, <code>au</code>, <code>uk</code>, <code>eu</code>, <code>kr</code>, <code>sa</code>, <code>tw</code>, <code>ru</code>, <code>mx</code>, <code>cn</code>, and on devkit you use the id <code>257</code> & <code>258</code> for testkit
+
possible regions are: <code>jp</code>, <code>us</code>, <code>au</code>, <code>uk</code>, <code>eu</code>, <code>kr</code>, <code>sa</code>, <code>tw</code>, <code>ru</code>, <code>mx</code>, <code>cn</code>
 +
and on devkit you must use the region id <code>257</code> and <code>258</code> for testkit's
  
 
The file must also be no larger than 65535 bytes,  
 
The file must also be no larger than 65535 bytes,  
Line 12: Line 13:
  
 
When selecting "Update via connecting to PC" the console instead connected to Content Mannager Assistant and then CMA downloads the updatelist file and the PUP files from PC side and sends it back to the vita,
 
When selecting "Update via connecting to PC" the console instead connected to Content Mannager Assistant and then CMA downloads the updatelist file and the PUP files from PC side and sends it back to the vita,
because of this using a custom Content Mannager Assistant such as QCMA you can just send whatever psp2-updatelist you want to the vita. this is also what happens with "update via connecting to PS3"  
+
because of this using a custom Content Mannager Assistant such as QCMA you can just send whatever psp2-updatelist you want to the vita. this is also what happens with "Update via connecting to PS3"  
  
 
On devkit&testkit you can configure your own URL for the psp2-updatelist.xml file. in <code>Debug Settings > System Update</code>
 
On devkit&testkit you can configure your own URL for the psp2-updatelist.xml file. in <code>Debug Settings > System Update</code>
Line 81: Line 82:
 
== Notes ==
 
== Notes ==
 
# This is untested, please report back!
 
# This is untested, please report back!
# Possible values are: <code>jp</code>, <code>us</code>, <code>au</code>, <code>uk</code>, <code>eu</code>, <code>kr</code>, <code>sa</code>, <code>tw</code>, <code>ru</code>, <code>mx</code>, <code>cn</code>;
+
# Possible values are: <code>jp</code>, <code>us</code>, <code>au</code>, <code>uk</code>, <code>eu</code>, <code>kr</code>, <code>sa</code>, <code>tw</code>, <code>ru</code>, <code>mx</code>, <code>cn</code>, <code>257</code> and <code>258</code>;

Revision as of 11:26, 19 November 2019

psp2-updatelist.xml

On retail (CEX) consoles- when you check for updates via WiFi in seettings the console will download an XML file based on the console's region code. for example on PSVita's sold within the United States the URL for the XML file will be http://fus01.psp2.update.playstation.net/update/psp2/list/us/psp2-updatelist.xml

When this is read by the system the region id MUST match the system region. possible regions are: jp, us, au, uk, eu, kr, sa, tw, ru, mx, cn and on devkit you must use the region id 257 and 258 for testkit's

The file must also be no larger than 65535 bytes, And the URL's specifying where to download the .PUP from can be no longer than 1024 characters, it also must be a direct URL to the content *including "http://" prototcal*

When selecting "Update via connecting to PC" the console instead connected to Content Mannager Assistant and then CMA downloads the updatelist file and the PUP files from PC side and sends it back to the vita, because of this using a custom Content Mannager Assistant such as QCMA you can just send whatever psp2-updatelist you want to the vita. this is also what happens with "Update via connecting to PS3"

On devkit&testkit you can configure your own URL for the psp2-updatelist.xml file. in Debug Settings > System Update

PS4 Update list

<?xml version="1.0" encoding="UTF-8"?>
<update_data_list>
  <region id="au">
    <np level0_system_version="01.600.000" level1_system_version="03.610.000" level2_system_version="03.610.000" map="03.610.000"/>
    <np_d level0_system_version="01.600.000" level1_system_version="03.610.000" level2_system_version="03.610.000" map="03.610.000"/>
      <version system_version="03.610.000" label="3.61">
        <update_data update_type="full">
          <image size="133676544">http://dau01.psp2.update.playstation.net/update/psp2/image/2016_0804/rel_99d9ab3e57a677b38e42cc6409b95e3b/PSP2UPDAT.PUP?dest=au</image>
        </update_data>
      </version>
      <recovery spkg_type="systemdata">
        <image spkg_version="01.000.010" size="56768512">http://dau01.psp2.update.playstation.net/update/psp2/image/2016_0804/sd_80cefcda06707796a040648aea38da0f/PSP2UPDAT.PUP?dest=au</image>
      </recovery>
      <recovery spkg_type="preinst">
        <image spkg_version="01.000.000" size="128788480">http://dau01.psp2.update.playstation.net/update/psp2/image/2016_0804/pre_f5e6da7d1213101482300ccaeda35c3c/PSP2UPDAT.PUP?dest=au</image>
      </recovery>
  </region>
</update_data_list>

PSVita Playstation Update Packages links use the same structure as the PS4 and PS3:

http://d<TLD>01.ps4.update.playstation.net/update/ps4/image/<YYYY_MMDD>/<TYPE>_<MD5>/PS4UPDATE.PUP?dest=<TLD>
  • <TLD>=2 letter region abbreviation (jp,us,..)
  • <YYYY_MMDD> is build date
  • TYPE is PUP type (rel, pre, sd,...)
  • MD5 is 22-digits long HASH

Running your own local updateserver

Using a webserver (apache, lighttpd, nginx, etc. whatever your preference is) and proxy/firewall to catch "http://f**01.psp2.update.playstation.net/update/psp2/list/**/psp2-updatelist.xml" and point it to your local server you could[1] have more control over the updates/bandwith. Ofcourse you need to have every PSP2UPDATE.PUP file you reference to, otherwise it errors out.

In this example the webserver is configured at http://192.168.0.254 , region is set to eu[2] change it to your own need.

<update_data_list>
  <region id="au">
    <np level0_system_version="01.600.000" level1_system_version="03.600.000" level2_system_version="03.600.000" map="03.600.000"/>
    <np_d level0_system_version="01.600.000" level1_system_version="03.600.000" level2_system_version="03.600.000" map="03.600.000"/>
      <version system_version="03.600.000" label="3.60">
        <update_data update_type="full">
          <image size="133676544">http://192.168.0.254/psp2/update/3_600_00/rel/PSP2UPDAT.PUP</image>
        </update_data>
      </version>
      <recovery spkg_type="systemdata">
        <image spkg_version="01.000.010" size="56768512">http://192.168.0.254/psp2/update/3_600_00/sd/PSP2UPDAT.PUP</image>
      </recovery>
      <recovery spkg_type="preinst">
        <image spkg_version="01.000.000" size="128788480">http://192.168.0.254/psp2/update/3_600_00/pre/PSP2UPDAT.PUP</image>
      </recovery>
      <version system_version="03.610.000" label="3.61">
        <update_data update_type="full">
          <image size="133676544">http://192.168.0.254/psp2/update/3_600_00/rel/PSP2UPDAT.PUP</image>
        </update_data>
      </version>
      <recovery spkg_type="systemdata">
        <image spkg_version="01.000.010" size="56768512">http://192.168.0.254/psp2/update/3_600_00/sd/PSP2UPDAT.PUP</image>
      </recovery>
      <recovery spkg_type="preinst">
        <image spkg_version="01.000.000" size="128788480">http://192.168.0.254/psp2/update/3_600_00/pre/PSP2UPDAT.PUP</image>
      </recovery>
  </region>
</update_data_list>

Notes

  1. This is untested, please report back!
  2. Possible values are: jp, us, au, uk, eu, kr, sa, tw, ru, mx, cn, 257 and 258;