{"id":854,"date":"2009-01-09T23:54:30","date_gmt":"2009-01-10T07:54:30","guid":{"rendered":"http:\/\/multimedia.cx\/eggs\/?p=854"},"modified":"2020-07-25T23:39:57","modified_gmt":"2020-07-26T06:39:57","slug":"adventures-in-mips-tools","status":"publish","type":"post","link":"https:\/\/multimedia.cx\/eggs\/adventures-in-mips-tools\/","title":{"rendered":"Adventures In MIPS Tools"},"content":{"rendered":"

I’m trying to compile a program that will run on my new MIPS-based subnotebook<\/a>. I finally got a cross-compiling toolchain built and building a super-simple C program. But the program failed to run. When I tried to run my sample program, the shell complained about not knowing what to do with a ‘(‘ character. Puzzling.<\/p>\n

This is the ‘file’ type of my compiled program:<\/p>\n

\nELF 32-bit MSB<\/strong> executable, MIPS, MIPS-I version 1 (SYSV), statically linked, not stripped<\/p><\/blockquote>\n

I finally thought to extract a binary from the MIPS machine and check its file type:<\/p>\n

ELF 32-bit LSB<\/strong> executable, MIPS, version 1 (SYSV), dynamically linked (uses shared libs), stripped<\/p><\/blockquote>\n

Okay, I think I’m getting wise to the discrepancy already. It turns out that I want a target called “mipsel” rather than just plain “mips” as the former specifies little endian (and because a MIPS CPU can be wired to run either endian — that’s how simple and reduced this reduced instruction set is).<\/p>\n

So I rebuilt the toolchain using the ‘mipsel’ target (building the toolchain is surprisingly quick when you know how). Now the test program segfaults when I try to run it. That’s unfortunate, though I still perceive it to be a step up from the last position. This is the new type reported by ‘file’:<\/p>\n

\nELF 32-bit LSB executable, MIPS, MIPS-I version 1 (SYSV), statically linked, not stripped\n<\/p><\/blockquote>\n

It’s MIPS-I version 1, vs. simply MIPS version 1, which is what the existing binaries are. I wonder if that’s the problem? I’m also struggling with a linker warning about the start location. That’s more likely to be the issue.<\/p>\n

BTW, this is the C code I am testing with:<\/p>\n

\r\nint main()\r\n{\r\n  return 77;\r\n}\r\n<\/pre>\n
My thinking here is that I should be able to run the program followed by “echo $?” to get the last command’s exit status– 77 in this case.<\/p>\n","protected":false},"excerpt":{"rendered":"
Trying to get my first MIPS program cross-compiled<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[28],"tags":[111,125,126],"class_list":["post-854","post","type-post","status-publish","format-standard","hentry","category-programming","tag-mips","tag-netbook","tag-subnotebook"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t