Choppy Sound; The Mp01 Is Flashed With Ap51 - ATCOM MP01 Administrator's Manual

-- Called 4000@10.130.1.142
-- event_onhook
-- default: hangup sound_on = 1
== Spawn extension (default, 142, 1) exited non-zero on 'MP/1'
-- start mp_hangup
4.3

Choppy sound

This is most likely caused by a poor wireless link. Check that you have line of
sight to other MP01. It is also possible to install another MP01 on a nearby
building or tower to relay the signals.
4.4

The MP01 is flashed with AP51

The AP51 flash tool re-arranges the disk lay-out. If the MP01 has been updated
with the AP51, you CAN NOT upgrade it remotely through wireless. Then you
need to do a MP01 Disaster Recovery BEFORE deploying it in the field to be able
to remotely upgrade it in the future.
CORRECT FORMAT:
root@OpenWrt:~# cat /proc/mtd
dev: size erasesize name
mtd0: 00030000 00010000 "RedBoot"
mtd1: 000b0000 00010000 "vmlinux.bin.l7"
mtd2: 006f0000 00010000 "rootfs"
mtd3: 00410000 00010000 "rootfs_data"
mtd4: 0000f000 00010000 "FIS directory"
mtd5: 00001000 00010000 "RedBoot config"
mtd6: 00020000 00010000 "boardconfig"
root@OpenWrt:~#
The ap51-utility swaps the position of kernel and rootfs. The kernel needs to be
in the second logical block and the rootfs in the third. After flashing with
ap51-flash this order is reversed and any flashing attempt from OpenWRT will
fail.
Before flashing with ap51-flash:
root@OpenWrt:/# cat /proc/mtd
dev: size erasesize name
mtd0: 00030000 00010000 "RedBoot"
mtd1: 000b0000 00010000 "vmlinux.bin.l7"
mtd2: 006f0000 00010000 "rootfs"
mtd3: 00410000 00010000 "rootfs_data"
mtd4: 0000f000 00010000 "FIS directory"
mtd5: 00001000 00010000 "RedBoot config"
mtd6: 00020000 00010000 "boardconfig"
After flashing with ap51-flash:
RedBoot> fis list
Name FLASH addr Mem addr Length Entry point
38