Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revisionBoth sides next revision
toh:d-link:d-link_dap_series_of_business_access_points [2021/01/20 20:46] – add notes on further unsupported models s_2toh:d-link:d-link_dap_series_of_business_access_points [2022/07/17 17:58] – [Model Overview] Add further devices by Alpha Networks s_2
Line 6: Line 6:
 ==== Model Overview ==== ==== Model Overview ====
  
-^ Model                                               ^ Wireless        ^ SoC / WiFi          ^ Flash   ^ RAM   ^ Case                                                ^ +^ Model                                               ^ Wireless        ^ SoC / WiFi                     ^ Flash   ^ RAM   ^ Case                                                ^ 
-| [[toh:d-link:d-link_dap-2230_a1|DAP-2230]]          | N300            | QCA9533             | 16      | 64    | Wall-Mount Plastic                                  | +| [[toh:d-link:d-link_dap-2230_a1|DAP-2230]]          | N300            | QCA9533                        | 16      | 64    | Wall-Mount Plastic                                  | 
-| [[toh:d-link:d-link_dap-2610|DAP-2610]]             | AC1200 Wave 2   | IPQ4018             | 16      | 256   | Wall-Mount Plastic                                  | +| [[toh:d-link:dap-2610|DAP-2610]]                    | AC1200 Wave 2   | IPQ4018                        | 16      | 256   | Wall-Mount Plastic                                  | 
-| [[toh:d-link:d-link_dap-2660|DAP-2660]]             | AC1200          | QCA9557 + QCA9882   | 16      | 128   | Wall-Mount Plastic                                  | +| [[toh:d-link:d-link_dap-2660|DAP-2660 A1]]          | AC1200          | QCA9557 + QCA9882              | 16      | 128   | Wall-Mount Plastic                                  | 
-| [[toh:hwdata:d-link:d-link_dap-2680_a1|DAP-2680]]   | AC1750 Wave 2   | QCA9558 + QCA9984   | 16      | 256   | Wall-Mount Plastic                                  | +| [[toh:d-link:dap-2660_a2|DAP-2660 A2]]              | AC1200          | QCA9558 + QCA9882              | 16      | 128   | Wall-Mount Plastic                                  | 
-| [[toh:d-link:dap-2695|DAP-2695]]                    | AC1750          | QCA9558 + QCA9880   | 16      | 256   | Plenum-Rated Metal, 6 detachable Antennas, 2x LAN   | +| [[toh:hwdata:d-link:d-link_dap-2680_a1|DAP-2680]]   | AC1750 Wave 2   | QCA9558 + QCA9984              | 16      | 256   | Wall-Mount Plastic                                  | 
-| [[toh:hwdata:d-link:d-link_dap-3320_a1|DAP-3320]]   | N300            | QCA9533             | 16      | 64    | Outdoor Pole-Mount Plastic                          | +| DAP-2682*                                           | AC2300 Wave 2   | QCN5502 + QCA9984              | 16      | ?     | Wall-Mount Plastic                                  | 
-| DAP-3662                                            | AC1200          | QCA9557 + QCA9882   | 16      | 128   | Outdoor Pole-Mount IP68 Plastic, 2x LAN             |+| [[toh:d-link:dap-2695|DAP-2695]]                    | AC1750          | QCA9558 + QCA9880              | 16      | 256   | Plenum-Rated Metal, 6 detachable Antennas, 2x LAN   | 
 +| [[toh:hwdata:d-link:d-link_dap-3320_a1|DAP-3320]]   | N300            | QCA9533                        | 16      | 64    | Outdoor Pole-Mount Plastic                          | 
 +| [[toh:d-link:d-link_dap-3662_a1|DAP-3662]]          | AC1200          | QCA9557 + QCA9882              | 16      | 128   | Outdoor Pole-Mount IP68 Plastic, 2x LAN             
 +| DAP-X2810*                                       | AX1800 | IPQ8000 + QCN5022 + QCN5052 | ?    | ?    | Wall-Mount Plastic                                  | 
 +| DAP-X2850*                                       | AX3600 | IPQ8072 + QCN5024 + QCN5054 | ?    | ?    | Wall-Mount Plastic                                  |
  
-DAP-2553 and DAP-2360 are currently unsupported due to [[https://forum.openwrt.org/t/ar8021-phy-not-working-in-gigabit-mode-how-to-configure-pll-data-cells/67207/2|issues with GMAC configuration on AR72xx]] when using an external Gigabit PHY (they only work when 100BASE-T is forced by the link partner).+*not yet supported 
 + 
 +[[toh:d-link:dap-2553|DAP-2553]] and DAP-2360 are currently unsupported due to [[https://forum.openwrt.org/t/ar8021-phy-not-working-in-gigabit-mode-how-to-configure-pll-data-cells/67207/2|issues with GMAC configuration on AR72xx]] when using an external Gigabit PHY (they only work when 100BASE-T is forced by the link partner).
  
 DAP-2590 is based on the Cavium Octeon platform, there is [[https://forum.openwrt.org/t/got-dap-2590-working/4515|experimental support here]], which also includes support for setting an additional flag during wrgg03 image header generation, which is also required by DAP-2553 and DAP-2360.  DAP-2590 is based on the Cavium Octeon platform, there is [[https://forum.openwrt.org/t/got-dap-2590-working/4515|experimental support here]], which also includes support for setting an additional flag during wrgg03 image header generation, which is also required by DAP-2553 and DAP-2360. 
Line 22: Line 28:
 ==== Power Supply ==== ==== Power Supply ====
  
-All devices can be supplied via 802.11af PoE (.at for DAP-2680 and DAP-2695).+All devices can be supplied via 802.3af PoE (.3at for DAP-2680 and DAP-2695).
  
-Alternatively, DAP-2230, DAP-2660 and DAP-2880 can be powered from a 12V supply, using a 3.5 x 1.35mm plug.+Alternatively, DAP-2230, DAP-2610, DAP-2660 and DAP-2680 can be powered from a 12V supply, using a 3.5 x 1.35mm plug.
  
 DAP-2695 can be powered from a 48V supply, using a special plug with center pin, the same as the PSU that comes with the DPE-101GI injector. DAP-2695 can be powered from a 48V supply, using a special plug with center pin, the same as the PSU that comes with the DPE-101GI injector.
Line 58: Line 64:
 Factory image can be flashed via the regular update procedure from the 'maintenance' menu. Factory image can be flashed via the regular update procedure from the 'maintenance' menu.
  
-After initially flashing the device to OpenWRT, flash a sysupgrade image again. This is not required, but allows you to use more space from the flash. See the next section for more technical details.+After initially flashing the device to OpenWrt, flash a sysupgrade image again. This is not required, but allows you to use more space from the flash. See the next section for more technical details.
  
 ==== Factory Images ==== ==== Factory Images ====
Line 69: Line 75:
 Thus, the factory image contains the kernel padded to 6 MiB + squashfs, so that jffs2 will always be outside of the memory region covered by the wrgg checksum. Thus, the factory image contains the kernel padded to 6 MiB + squashfs, so that jffs2 will always be outside of the memory region covered by the wrgg checksum.
  
-As soon as the device is running OpenWRT already, there is no more minimum size of 6 MiB, so we can put just the kernel in the wrgg partition, which will not cause the problem of a changing checksum.+As soon as the device is running OpenWrt already, there is no more minimum size of 6 MiB, so we can put just the kernel in the wrgg partition, which will not cause the problem of a changing checksum.
  
 So, when more flash space is required, a sysupgrade image can be flashed right after factory, to allow for using of all the available flash memory. So, when more flash space is required, a sysupgrade image can be flashed right after factory, to allow for using of all the available flash memory.
  
 The recovery also does not have the minimum size requirement, however we shall prefer not to have three separate images (factory padded for web-flashing, factory unpadded for recovery, sysupgrade) when the padded factory image is also accepted by the recovery (but requires double flashing to use all of the available flash space). The recovery also does not have the minimum size requirement, however we shall prefer not to have three separate images (factory padded for web-flashing, factory unpadded for recovery, sysupgrade) when the padded factory image is also accepted by the recovery (but requires double flashing to use all of the available flash space).
 +
 +
 +=== Image header format ===
 +<code>
 +struct wrgg03_header {
 + char signature[32];
 + uint32_t magic1;
 + uint32_t magic2;
 + char version[16];
 + char model[16];
 + uint32_t flag[2];
 + uint32_t reserve[2];
 + char buildno[16];
 + uint32_t size;
 + uint32_t offset;
 + char devname[32];
 + char digest[16];
 +}
 +</code>
 +In the wrgg03 image header, there is a 32 bit field called flags at 0x48, which is currently not set (i.e. remains zero) by mkwrggimg. For most devices, this is zero, however few older devices (DAP-2360, DAP-2553, DAP-2590) have the value set to 1.
 +This field can be used by the manufacturer to release firmware updates that would introduce changes which do not allow for downgrading back to previous versions: While checking the header, the web-based updater will verify the value of this field to be the same or higher than the firmware that is currently installed. If any of the forementioned devices shall be supported, the option to set this flag to 1 needs to be introduced to mkwrggimg, [[https://github.com/skids/source/commit/815f1f01df4f8fe778980a1a7a71052de267350f|e.g. as implemented in this commit]].
  • Last modified: 2022/07/17 18:14
  • by s_2