New board based on MT7628NN

Hi,

We are working on a new hardware design, based on MT7628NN,
the device was designed with 8MB flash and 64MB Mem,

there was another device from another vendor, so I just dumped the SPI FLASH and write it to a new one,
the other device specs are almost the same as ours, also it is flashed by openwrt,

u-boot is booting successfully, but at DATA check it is getting BAD Data Checksum,

first boot log:

U-Boot 1.1.3 (May 20 2018 - 05:24:52)

Board: Ralink APSoC DRAM:  64 MB
relocate_code Pointer at: 83fb8000
******************************
Software System Reset Occurred
******************************
flash manufacture id: ef, device id 40 17
find flash: W25Q64BV
*** Warning - bad CRC, using default environment

?===========================================
Ralink UBoot Version: 4.3.0.0
--------------------------------------------
ASIC 7628_MP ?Port5<->None)
DRAM component: 512 Mbits DDR, width 16
DRAM bus: 16 bit
Total memory: 64 MBytes
Flash component: SPI Flash
Date:May 20 2018  Time:05:24:52
?===========================================
icache: sets:512, ways:4, linesz:32 ,total:65536
dcache: sets:256, ways:4, linesz:32 ,total:32768

 ##### The CPU freq = 575 MHZ ####
 estimate memory size =64 Mbytes
RESET MT7628 PHY!!!!!!
Please choose the operation:
   1: Load system code to SDRAM via TFTP.
   2: Load system code then write to Flash via TFTP.
   3: Boot system code via Flash (default).
   4: Entr boot command line interface.
   7: Load Boot Loader code then write to Flash via Serial.
   9: Load Boot Loader code then write to Flash via TFTP.                                                                                                             0

3: System Boot system code via Flash.
## Booting image at bc050000 ...
   Image Name:   MIPS test Linux-5.4.106
   Image Type:   MIPS Linux Kernel Image (lzma compressed)
   Data Size:    1996431 Bytes =  1.9 MB
   Load Address: 80000000
   Entry Point:  80000000
   Verifying Checksum ... Bad Data CRC

next try by using tftp img into the flash spi:

U-Boot 1.1.3 (May 20 2018 - 05:24:52)

Board: Ralink APSoC DRAM:  64 MB
relocate_code Pointer at: 83fb8000
flash manufacture id: ef, device id 40 17
find flash: W25Q64BV
*** Warning - bad CRC, using default environment

?===========================================
Ralink UBoot Version: 4.3.0.0
--------------------------------------------
ASIC 7628_MP (Port5<->None)
DRAM component: 512 Mbits DDR, width 16
DRAM bus: 16 bit
Total memory: 64 MBytes
Flash component: SPI Flash
Date:May 20 2018  Time:05:24:52
?===========================================
icache: sets:512, ways:4, linesz:32 ,total:65536
dcache: sets:256, ways:4, linesz:32 ,total:32768

 ##### The CPU freq = 575 MHZ ####
 estimate memory size =64 Mbytes
RESET MT7628 PHY!!!!!!
Please choose the operation:
   1: Load system code to SDRAM via TFTP.
   2: Load system code then write to Flash via TFTP.
   3: Boot system code via Flash (default).
   4: Entr boot command line interface.
   7: Load Boot Loader code then write to Flash via Serial.
   9: Load Boot Loader code then write to Flash via TFTP.

You choosed 2
                                                                                                                                                                      0


2: System Load Linux Kernel then write to Flash via TFTP.
 Warning!! Erase Linux in Flash then burn new one. Are you sure?(Y/N)
 Please Input new ones /or Ctrl-C to discard
        Input device IP (10.10.10.123) ==:10.10.10.123
        Input server IP (10.10.10.3) ==:10.10.10.3
        Input Linux Kernel filename () ==:img.bin

 netboot_common, argc= 3

 NetTxPacket = 0x83FE5900

 KSEG1ADDR(NetTxPacket) = 0xA3FE5900

 NetLoop,call eth_halt !

 NetLoop,call eth_init !
Trying Eth0 (10/100-M)

 Waitting for RX_DMA_BUSY status Start... done


 ETH_STATE_ACTIVE!!
TFTP from server 10.10.10.3; our IP address is 10.10.10.123
Filename 'img.bin'.

 TIMEOUT_COUNT=10,Load address: 0x80100000
Loading: Got ARP REQUEST, return our IP
Got ARP REQUEST, return our IP
Got ARP REQUEST, return our IP
Got ARP REQUEST, return our IP
Got ARP REQUEST, return our IP
?hecksum bad
?hecksum bad
Got ARP REQUEST, return our IP
?hecksum bad
?hecksum bad
Got ARP REPLY, set server/gtwy eth addr (e0:d5:5e:d4:4a:3a)
Got it
#################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #######################################################
done
Bytes transferred = 5269381 (506785 hex)
NetBootFileXferSize= 00506785
## Booting image at bc050000 ...
   Image Name:   MIPS test Linux-5.4.106
   Image Type:   MIPS Linux Kernel Image (lzma compressed)
   Data Size:    1996431 Bytes =  1.9 MB
   Load Address: 80000000
   Entry Point:  80000000
   Verifying Checksum ... Bad Data CRC
                                      [04050C0B][04050C0C]
DDR Calibration DQS reg = 00008888

any suggestion?

This is a uboot issue, not related to openwrt.

To me it looks like the uboot isn’t compiled / configured correctly for the flash. That will happen if you use a uboot from another device.

Create your own uboot based on the correct config for your exact board.