altech6983 Posted September 20, 2015 Report Posted September 20, 2015 (edited) I am trying to compile the pedalbox code but I keep getting the following output. To get this output I started up msys and cd'd into the folder where pedalbox was downloaded and ran make../bin/mios-gpasm modifies _output/main.asm, result in _output/main__mios-gpasm-tmp.asm gplink -s ./etc/lkr/p18f4620.lkr -m -o project.hex ./lib/libsdcc.lib ./lib/pic18f4620.lib _output/mios_wrapper.o _output/app_lcd.o _output/main.o warning: processor mismatch in "divuchar.o" warning: processor mismatch in "mulint.o" warning: processor mismatch in "divslong.o" warning: processor mismatch in "divulong.o" warning: unknown processor type (0xa462) in "pic18f4620.o" defaulted to pic18cxx warning: processor mismatch in "pic18f4620.o"I have done some poking around and searches but I haven't been able to fix this problem. I followed this page for the tool chain setup http://www.midibox.org/dokuwiki/windows_toolchain_quickstartWindows 10 64 bitSDCC 2.8.0gputils 0.14.3msys 1.0.11Compiling for a PIC18F4620http://midibox.org/forums/topic/13176-warnings-when-compiling-my-app-for-18f4620/ is the only thread that I have found where someone fixed the problem but I haven't been able to follow his directions as I can't find lib\libsdcc\sdcc_2.8.0 folder and I don't see any make files for me to change and rebuild libsdcc.libAny help will be greatly appreciated. Edited September 20, 2015 by altech6983
TK. Posted September 20, 2015 Report Posted September 20, 2015 Are the messages really problematic? I mean: these are warnings and no error messages, hence the .hex file should be generated, right?Best Regards, Thorsten.
altech6983 Posted September 20, 2015 Author Report Posted September 20, 2015 the only thing I was really worried about was the fact that it defaulted to pic18cxx. If this isn't a problem then I won't worry about it. I just thought it might hurt the pic to upload the generated hex file.
TK. Posted September 21, 2015 Report Posted September 21, 2015 This shouldn't cause a problem, the .o files should be compatible anyhow.Best Regards, Thorsten.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now