Failed to execute when boot MT7688

Hi, I'm having a problem with my module (AI7688 from ACSip) using MT7688 and OpenWrt. Sometimes, when I turn on the module, it goes into "Failed to execute" state, and cannot run the console or any programs.
Now, I have to fix it by using soft reset factory in safe mode. But it happened again and again.
Can any know why and how to fix this error?

What module?

I'm using module AI7688 from AcSip

More information. What are you installing, etc.?

Are you running official firmware on a supported device?

If so, what device?

My device is a IoT product we design by ourselves. Module AI7688 installed with Openwrt

After enter failsafe mode, I see no file in jffs2 filesystem

BusyBox v1.23.2 (2015-11-18 16:34:33 CET) built-in shell (ash)

ash: can't access tty; job control turned off
  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 CHAOS CALMER (15.05+linkit, r47501)
  * 1 1/2 oz Gin            Shake with a glassful
  * 1/4 oz Triple Sec       of broken ice and pour
  * 3/4 oz Lime Juice       unstrained into a goblet.
  * 1 1/2 oz Orange Juice
  * 1 tsp. Grenadine Syrup
================= FAILSAFE MODE active ================
special commands:
* firstboot          reset settings to factory defaults
* mount_root     mount root-partition with config files

after mount_root:
* passwd                         change root's password
* /etc/config               directory with config files

for more help see:

root@(none):/# [    9.230000] rt305x-esw 10110000.esw: link changed 0x01
df -h
Filesystem                Size      Used Available Use% Mounted on
rootfs                   19.8M     19.8M         0 100% /
/dev/root                19.8M     19.8M         0 100% /
tmpfs                   512.0K         0    512.0K   0% /dev
tmpfs                    61.8M     16.0K     61.7M   0% /tmp
ash: root_mount: not found
root@(none):/# mount_root
[   44.450000] jffs2: notice: (389) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
[   44.500000] mount_root: switching to jffs2 overlay
root@(none):/# ls
root@(none):/# df -h
root@(none):/# ls
root@(none):/# df -h
root@(none):/# ls
root@(none):/# ls
root@(none):/# ls
root@(none):/# ls
root@(none):/# [   77.300000] random: nonblocking pool is initialized
root@(none):/# ls
root@(none):/# ls
root@(none):/# mount_root
[  172.020000] mount_root: rootfs_data:/dev/mtdblock6 is already mounted as /overlay
root@(none):/# df -h
root@(none):/# ls

2015 called, wanted the release back ...

upgrade to something that isn't 7+ years old, or ask your vendor.

1 Like

My sentiment match @frollic.

Feel free to design on a current, supported version and we'd be more readily able to assist.

It is quite sad some chip vendors bundle an old SDK with the products they provide OEMs.

Do you have any experience with this error

might have, if we had a time machine, but we don't :confused:

cli snipped does however say failsafe mode, could be related.

you're asking us to fix a black box OS, running on black box hardware for you,
that's not going to happen any time, well, ever..

1 Like

I'm desperate with this error :frowning:

then ask your vendor, I'm sure they'll be happy to assist you (for a fee) ....

1 Like

RE why old SDKs from chip vendors:

If you mean the error on a device you haven't distributed yet, with a proprietary firmware based on an old unsupported version - nope. I would also probally surmise only you and others with those chips and software may be able to help yourselves.

A web search shows results related to other OSes, not sure how helpful it is."is%20already%20mounted%20as%20%2Foverlay"

In quotes: One result seem to be seems to be written in Chinese...

1 Like