On Wed, Dec 29, 2021 at 6:15 PM Davis Roman <[email protected]> wrote: > > On Wed, Dec 29, 2021 at 5:30 PM Khem Raj <[email protected]> wrote: > > > > > > > > On Wed, Dec 29, 2021 at 2:20 PM Davis Roman <[email protected]> wrote: > >> > >> On Wed, Dec 29, 2021 at 2:21 PM Anders Montonen <[email protected]> > >> wrote: > >> > > >> > Hi, > >> > > >> > > On 29 Dec 2021, at 9:53, davis roman <[email protected]> wrote: > >> > > > >> > > I generated an internal mips toolchain built against musl and I tried > >> > > to compile u-boot but unfortunately, I'm getting "opcode not > >> > > supported" error messages. https://pastebin.com/QdcLxy69 > >> > > If instead I use the realtek provided prebuilt toolchain then u-boot > >> > > compiles successfully. https://pastebin.com/zcQ5kc20 > >> > > > >> > > I'm thinking that Realtek's toolchain has patches specific to their > >> > > SoC that have not been pushed upstream. Could this be the reason I'm > >> > > unable to compile uboot? > >> > > >> > I’m guessing that your U-Boot config doesn’t set the correct MIPS > >> > architecture revision. The compiler error shows that you’re trying to > >> > assemble a MIPS32r1 instruction, but the compiler is targeting the > >> > original MIPS1 architecture. The Realtek toolchain may have set the > >> > default architecture to match the SoC, but the fix is to update the > >> > config to match the hardware. > >> > >> You're right. I didn't realize the RX5281 core on the RTS3916N only > >> supports mips1 or mips16 (https://pasteboard.co/IpsqN6GkBYAs.png). > >> > >> I happened to have a mips sourcery toolchain installed on my machine > >> (https://sourcery.sw.siemens.com/GNUToolchain/package12797/public/mips-linux-gnu/mips-2014.05-27-mips-linux-gnu-i686-pc-linux-gnu.tar.bz2) > >> so I pointed that to u-boot without modifying anything else and it was > >> able to compile u-boot successfully. Woot! > >> https://pastebin.com/ySPFae5u > >> > >> I suppose the next step would be to generate a mips1 yocto toolchain > >> however according to the available tune values it appears only mips32 > >> or mips64 is available > >> > >> Any suggestions on how to generate a mips1 yocto toolchain or if > >> that's even supported? > > > > > > Yes it’s supported although it’s not default for qemumips so the simple > > trick you can do is change the DEFAULTTUNE setting in the qemumips.conf > > away from mips32r2 > > Sorry Khem, I'm not quite following you. I tried the following patch > (https://pastebin.com/rkmQ3t6P) thinking perhaps this is what you > meant however my build configuration still shows the tune set to > mips32r2 https://pastebin.com/izP9thVW > > What am I missing? >
Nevermind, I scraped the last patch, recreated my BUILD_DIR, set MACHINE = "qemumips" and added DEFAULTTUNE = "mips" in my local.conf. Now the build configuration correct https://pastebin.com/pkkRVL58 and I'm now waiting for the toolchain to finish so I can attempt to build realtek's u-boot. > >> > >> > >> > >> > > >> > Regards, > >> > Anders Montonen
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#55692): https://lists.yoctoproject.org/g/yocto/message/55692 Mute This Topic: https://lists.yoctoproject.org/mt/88005049/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
