Help me with U-boot 1.1.3 and 1.1.4

Hardware Questions and Recommendations
1

hi i cant load new fermwar to me router by serial becouz the u-boot cant show load options

.........
U-Boot 1.1.3 (Feb 13 2018 - 10:29:24)

Board: Ralink APSoC DRAM: 256 MB

The CPU freq = 880 MHZ

Boot act = 1

MCR Image Checksum OK

Booting image at bc140000 ...

Image Name: Linux Kernel Image
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 4161034 Bytes = 4 MB
Load Address: 80001000
Entry Point: 80722aa0

Starting kernel ...

2

we can't help your with anonymous hardware ...

5

can help me please

6

i dont understand what info you want

7

So far you've provided none, whatever you throw us will be an improvement.

8

Probably the make, model and version of your router/ap/switch or the output of command
ubus call system board

9

its GIGA WIFI WAVE 2 KM08-708H reles 2020

10

its GIGA WIFI WAVE 2 KM08-708H reles 2020 is that ok

11

It needs to be currently supported by OpenWrt and easy to find in the Table of Hardware:

I did not find a match based on your info.

12

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.

13

You could however try to reach out to @eisa

14

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.