We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I managed to get this far but the kernel won't boot because it is trying to read from 0xbc050000 and qemu returns 0x00000
U-Boot 1.1.3 Board: Ralink APSoC DRAM: 128 MB relocate_code Pointer at: 87fb4000 flash manufacture id: 0, device id 0 0 Warning: un-recognized chip ID, please update bootloader! ============================================ Ralink UBoot Version: 4.3.0.0 -------------------------------------------- ASIC 7628_MP (Port5<->None) DRAM component: 1024 Mbits DDR, width 16 DRAM bus: 16 bit Total memory: 128 MBytes Flash component: SPI Flash ============================================ icache: sets:64, ways:2, linesz:16 ,total:2048 dcache: sets:64, ways:2, linesz:16 ,total:2048 ##### The CPU freq = 575 MHZ #### estimate memory size =128 Mbytes RESET MT7628 PHY!!!!!! Signature: DCS-5030L A1 Release 1.01 (2015-03-09) RT2880_AGPIOCFG_REG = 0 RT2880_GPIOMODE_REG = 0 RT2880_GPIOMODE_REG+0x04 = 0 RT2880_REG_PIODIR = 0 RT2880_REG_6332PIODIR = 0 RT2880_REG_6332PIODATA = 0 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 ... Bad Magic Number,00000000
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I managed to get this far but the kernel won't boot because it is trying to read from 0xbc050000 and qemu returns 0x00000
The text was updated successfully, but these errors were encountered: