Keywords: Intellon, Atheros, Qualcomm, HomePlug, powerline, communications, INT6000, INT6300, INT6400, AR7400, AR7420

Upgrading PIB Only
Prev | Chapter 5. Procedures | Next

## Upgrading PIB Only

When flashing a PIB to the local device, the PIB DAK must match that of the local device or you will get a “DAK Not Zero” error message. This message is incorrect and should probably read “DAK Mismatch”. The following two toolkit commands should prevent this error from occuring on Linux. The first command reads the actual MAC (`-A`) and DAK (`-D`) from the device using program int6kid and inserts them on the command lise as modpib arguments using options `-M` and `-D`. We need not include the station MAC address on the int6k command line because the device is local, but we could include it.

Example 5.16. Upgrade local device PIB

     # modpib abc.pib -ieth1 -M $(int6kid -ieth1 -A) -D $(int6kid -ieth1 -D)
     # int6k -P abc.pib -C pib

When flashing a PIB to a remote device, the PIB DAK must be all zeros or you will get a “DAK Not Zero” error message. This message occurs because the HomePlug™ AV Specification does not permit a DAK to be transmitted over powerline in any form. The following two toolkit commands should prevent this error on Linux. We must include the device MAC on the command line when invoking each program because the device is remote. Notice that symbol `none` can be used as shorthand `00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00` when specifying the DAK.

Example 5.17. Upgrade remote PIB

     # modpib abc.pib -ieth1 -M $(int6kid -ieth1 -A 00B052BEEF03) -D none
     # int6k -P abc.pib -C2 00B052BEEF03

The MAC address stored in the PIB can have any value but it is good practice to preserve the original value. This avoids the common mistake of flashing multiple network stations with the same MAC address because the PIB was not updated.

Prev | Up | Next
Upgrading Firmware and PIB | Home | Starting a Device