Commands to upload firmware from tftpd on ap 330

[VictorFBR2025]

Hello, I have an AP330 with corrupted Firmware. I can log on to Uboot and execute commands to try to recover it, but I have had no success. 

I downloaded the archive AP350-6.5r16.img.S (20MB) and read about its compatibility. 

I executed these commands to try, to bring him back to life, and access the console. 

"tftpboot 0x80000000 AP350-6.5r16.img.S" (the firmware is successfully downloaded but not booted)

I have extracted the file vmlinux.bin.22101 (4.4MB)

tftpboot 0x80000000 vmlinux.bin.22101 (the firmware is successfully downloaded but not booted)

have renamed to vmlinux.bin and recovery.bin, also renamed the file AP350-6.5r16.img.S to AP350-6.5r16.img and recovery.bin

after all these tests and executed bootm command, the return is:

=> bootm
Machine check in kernel mode.
Caused by (from mcsr): mcsr = 0x00010008
Bus Read data bus error
****: 0FF57934 XER: 00000000 LR: 0FF57920 REGS: 0fe2fc40 TRAP: 0200 DAR: 00000000
MSR: 00029200 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 00

GPR00: 00000001 0FE2FD30 0FE2FF74 80000000 0FE2F920 001D06E0 0FFB0FBC 00000011
GPR08: 00000001 0FF84990 00000001 0FE2FD40 44022022 60A5A352 0FF88A00 00000000
GPR16: 00000000 0FF865E8 00000000 00000000 00000000 0FF477B0 0FFB181C 0FFB0110
GPR24: 0FFB0E90 0FF865E8 00000000 0FE90340 00000001 80000000 0FF87920 80000000
MCSR=0x00010008 MCSRR0=0x0ff57934
MCSRR1=0x00029200 MCAR=0x80000000
Call backtrace:
00000000 0FF46F9C 0FF475B0 0FF56970 0FF56F78 0FF5713C 0FF5983C
0FF34628 0FF31630
Returning back to 0x0ff57934
Machine check in kernel mode.
Caused by (from mcsr): mcsr = 0x00010008
Bus Read data bus error
****: 0FF57934 XER: 00000000 LR: 0FF57920 REGS: 0fe2fc40 TRAP: 0200 DAR: 00000000
MSR: 00029200 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 00

GPR00: 00000001 0FE2FD30 0FE2FF74 80000000 0FE2F920 001D06E0 0FFB0FBC 00000011
GPR08: 00000001 0FF84990 00000001 0FE2FD40 44022022 60A5A352 0FF88A00 00000000
GPR16: 00000000 0FF865E8 00000000 00000000 00000000 0FF477B0 0FFB181C 0FFB0110
GPR24: 0FFB0E90 0FF865E8 00000000 0FE90340 00000001 80000000 0FF87920 80000000
MCSR=0x00010008 MCSRR0=0x0ff57934
MCSRR1=0x00029200 MCAR=0x80000000
Call backtrace:
00000000 0FF46F9C 0FF475B0 0FF56970 0FF56F78 0FF5713C 0FF5983C
0FF34628 0FF31630
machine check count too high

Skipping current instr, Returning to 0x0ff57938
Machine check in kernel mode.
Caused by (from mcsr): mcsr = 0x00010008
Bus Read data bus error
****: 0FF5E6EC XER: 00000000 LR: 0FF5794C REGS: 0fe2fc40 TRAP: 0200 DAR: 00000000
MSR: 00029200 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 00

GPR00: 00000001 0FE2FD30 0FE2FF74 80000000 0FE2F920 001D06E0 0FFB0FBC 00000011
GPR08: 00000001 28E7FD40 00000001 0FE2FD40 44022022 60A5A352 0FF88A00 00000000
GPR16: 00000000 0FF865E8 00000000 00000000 00000000 0FF477B0 0FFB181C 0FFB0110
GPR24: 0FFB0E90 0FF865E8 00000000 0FE90340 00000001 80000000 0FF8A0F4 80000000
MCSR=0x00010008 MCSRR0=0x0ff5e6ec
MCSRR1=0x00029200 MCAR=0x80000000
Call backtrace:
00000000 0FF46F9C 0FF475B0 0FF56970 0FF56F78 0FF5713C 0FF5983C
0FF34628 0FF31630
machine check count too high

Skipping current instr, Returning to 0x0ff5e6f0
Wrong Image Format for bootm command
ERROR: can't get kernel image!
=>

U-Boot 2009.11 (Aug 08 2018 - 03:20:47), Build: jenkins-HiveOS-Honolulu_StdBuild_Rel-1302

CPU0: P1020E, Version: 1.1, (0x80ec0011)
Core: E500, Version: 5.1, (0x80212051)
Clock Configuration:
CPU0:533.333 MHz, CPU1:533.333 MHz,
CCB:266.667 MHz,
DDR:266.667 MHz (533.333 MT/s data rate) (Asynchronous), LBC:16.667 MHz
L1: D-cache 32 kB enabled
I-cache 32 kB enabled
I2C: ready
SPI: ready
DRAM: Configuring DDR for 533.333 MT/s data rate
DDR: 256 MB
FLASH: 64 MB
L2: 256 KB enabled
MMC:

PCIE2 connected to Slot 1 as Root Complex (base addr ffe09000)
Scanning PCI bus 01
01 00 168c 0030 0280 ff
PCIE2 on bus 00 - 01

PCIE1 connected to Slot 2 as Root Complex (base addr ffe0a000)
Scanning PCI bus 03
03 00 168c 0030 0280 ff
PCIE1 on bus 02 - 03

In: serial
Out: serial
Err: serial
Net: eth0, eth1
current temperature is 44

I have tried to contact support to understand the right commands to apply to the device. but they recommended to me: this is too old, buy a new one.  

the device was working properly, and after a network policy update with firmware upgrade, resulted this.

can someone show me the path to solve this problem, please?

[VictorFBR2025]

To add Information, this is the result for trying boot directly from uboot system 

=> bootm
Wrong Image Format for bootm command
ERROR: can't get kernel image!
=>