AP143 firmware spkg


I have the below device specs :slight_smile:

Version: WitUnit Boot 1.3.7-g54519cca-dirty (Dec 4 2017 - 16:59:14)
CPU: QCA953x - Honey Bee 2.0
Flash: 8 MB (Flash ID: ef4017 / Erase Size: 4k)
Frequency: CPU 650MHz / RAM 597MHz / AHB 216MHz
SBI Info: CPE2G-9531/terra@superwrt.com/2017-12-21
Device UID: 6000cdb938e66d552c303249b03ee06b
WLAN0 info: cal:0xff1000, mac:0xff1002 (84:40:00:00:17:0c)
MAC: 84:40:00:00:17:0c
Firmware: FW/link/1.5.28/qca/qca9k/2a7ab355b4
LIC_wlink/zl_master_9531 UID:6000cdb938e66d552c303249b03ee06b
0x00000000-0x0001c000[0x0001c000] uboot
0x0001c000-0x00020000[0x00004000] SBI
0x00020000-0x007a0000[0x00780000] firmware
0x007a0000-0x007b0000[0x00010000] elog
0x007b0000-0x007c0000[0x00010000] config
0x007c0000-0x007d0000[0x00010000] config2
0x007d0000-0x007e0000[0x00010000] custom
0x007e0000-0x007f0000[0x00010000] DTB
0x007f0000-0x00800000[0x00010000] CAL

I compile Atheros "AP143" reference platofmr

THe interface says " * Only support spkg, uimage firmware, TP-Link firmware type file."

How to convert the .bin into a SPKG file ?

Can you please identify your device on the Table of Hardware?


Doesn't seem to be original OpenWrt.

@tmomas no, it is not, and I am trying to replace the firware by openwrt

The current firmware is available on http://superwrt.com/download/

@lleachii not reall in the table.

On teh menuconfig of openwrt, the closest match is Qualcom AP143 platform

the problem is that the web interface to uplaod the firmware is asking for ".spkg" or ".ubin"

This device is not supported by OpenWrt, then.

"Closest" isn't good enough - the problem is that your device isn't supported.

maybe, but it it is not the issue. (actually, the qualcom AP143 will do)

THe issue is how to make a SPKG file from a .bin file (from compilation of openwrt)

  • you're not running OpenWrt
  • nor is your device supported

I'll try again. I think you should ask your question here: http://forum.superwrt.com/

@lleachii PLease just read my question

I did:

  • you have a device that you think is compatible to a AP143 reference board
  • you think it's safe to flash it
  • then your problem is, you need a BIN or SPKG file
  • you're on the wrong forum asking your question
  • I told you this 2 times, and offered you a link to the SuperWrt forum
  • you told me to read your question again

SO why do you keep on telling me that you think my device is not supported ?

Can you please focus on my question ?

I'm not telling you that I THINK your device is unsupported.

I'm telling you that your device is IN FACT unsupported.

I'm glad we cleared this up.

Your story is non-sense
PLease read my questin or just focus on something else

1 Like

The platform (QCA953x SoC) is supported, but your device is not supported in OpenWrt.

If the firmware of a device that is not appropriate is installed, the structure of the mtd partition may be destroyed and important data may be lost. Also, buttons and LEDs do not operate properly, which may cause erroneous operation.

1 Like

I don't care about led and button
I just want to know how to create a UBIN or SPKG file from the BIN file created at compile time

1 Like

It seems to be suitable for questioning with the SuperWrt Forum instead of the OpenWrt Forum.

1 Like

OK, I'm going to try again - I'll also TRY to focus ONLY on your question:

Since you have compiled a firmware for another [supported] device, we would be unable to tell you how to safely convert the output image into a BIN or SPKG for your [UNsupported] hardware. The manfacturer's support channels and their community forum would be best to answer that.

I hope this helps you.

I am not askng you if it is safe or not.

Just HOW TO CONVERT a .bin into .spkg !

1 Like

OK, I understand now!

That's impossible without information only the manufacturer knows. So their support channels and community forums remain where your answer lies.

If you have a serial cable, you may be able to figure it out; but it won't be a "conversion..." work will be involved by you alone to actually support the device.

If you're not worried about safety...have you tried re-naming the BIN file to SPKG?