Adding a binary file manually

For Developers
1

Hi we tried to add a binary file into openwrt package given by our vendor and when an image is built with this image the board hangs saying invalid vblock, signatures don't match how to overcome this and add a simple Hello world application to get a image???

2

That would be a question for your vendor, wouldn't it?

2 Likes
3

This sounds a lot like the classic cyber security do and don’t.
“Hey, I found a USB stick outside the door, let’s see what that contains?”

Usually when building open source firmware/software you never include binary files in the build, that is actually the whole point of the open source idea.
You build a complete binary file with all the source code directly.

4

Please post output of
ubus call system board
from your device.

5

still using the same unsupported hw from Port mt7621 to openwrt for linux 4.14.131, are we ?

1 Like
6

hi when a image is created with needed binary by openwrt way also image gives the same message

7

as @slh said, ask the people you got the image and the binary from, they're not from here.

8

hi here is the output of the ubus call system board
{
"kernel": "4.14.131",
"hostname": "TC100",
"system": "MediaTek MT7621 ver:1 eco:3",
"model":
"board_name":
}

9

as previously stated ...

It appears you are using firmware that is not from the official OpenWrt project.

When using forks/offshoots/vendor-specific builds that are "based on OpenWrt", there may be many differences compared to the official versions (hosted by OpenWrt.org). Some of these customizations may fundamentally change the way that OpenWrt works. You might need help from people with specific/specialized knowledge about the firmware you are using, so it is possible that advice you get here may not be useful.

You may find that the best options are:

  1. Install an official version of OpenWrt, if your device is supported (see https://firmware-selector.openwrt.org).
  2. Ask for help from the maintainer(s) or user community of the specific firmware that you are using.
  3. Provide the source code for the firmware so that users on this forum can understand how your firmware works (OpenWrt forum users are volunteers, so somebody might look at the code if they have time and are interested in your issue).

If you believe that this specific issue is common to generic/official OpenWrt and/or the maintainers of your build have indicated as such, please feel free to clarify.

3 Likes
10

hi addition of a binary image by package way to the image and uploading the image to target and making it come up is done have done option 1 and tftp to the board it came up and even the binary when called by its name ran without any issue , but when the same image is written to flash by option 2 am getting LZMA ERROR 1 now ..earlier this alone used to work

11

hi in mt7621 with kernel version 4.14.131 and uboot 2.0.0 version trying to bring up the generated image large than what was provided by the vendor am getting bleow message and the board hangs please nay suggestion to overcome this ???
had commented the do_reset so have come till here ...

3: System Boot system code via Flash.

Booting image at bc050000 ...

Image Name: CPE3_TC100_v1.0.0d.bin
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 10351668(0x9DF434) Bytes = 9.9 MB
Load Address: 80001000
Entry Point: 80001000
AES Decrypt cbc start
AES Decrypt cbc finish
Uncompressing Kernel Image ...
LZMA ERROR 1 - must RESET board to recover
No initrd

Transferring control to Linux (at address 80001000) ...

Giving linux memsize in MB, 256

Starting kernel ...

In same target an image with different lesser size works this image is built from vendor provided configuration.
Now when an image is uploaded to flash through sdram via tftp will any bytes be discarded or so ??