Compiling-linking errors on ChipKit Uno32 with MPIDE 0023

[olikraus]

Originally reported on Google Code with ID 318

What steps will reproduce the problem?

1. Start MPIDE and open "GraphicsTest" (or any other example)from the example folder
for u8glib and check Board = chipKIT UNO32 under the Tools->Board->chipKIT menu.

2. Uncomment constructor call "U8GLIB_SSD1306_128X64 u8g(4, 5, 6, 7);   // SW SPI Com:
SCK = 4, MOSI = 5, CS = 6, A0 = 7 (new white HalTec OLED)" in the GraphicsTest.ino
sourcefile.

3. Compile/verify the code and you get lots of linker errors like: "GraphicsTest.cpp.elf
section `.sbss' is not within region `kseg1_data_mem'"

What is the expected output?
* A succeful compile and link

What do you see instead?
* Lots of linker errors about .sbss not fitting in region kseg1_data_mem. I've attached
the compile/link log with error messages as a textfile.

What version of the product are you using? On what operating system?
* MPIDE 0023 and u8glib_arduino_v1.17.


Please provide any additional information below.

* The compiling and linking works perfectly if you choose board = chipKIT MAX32.

* I can compile and link with board= UNO32 if i delete unneeded device files in "utility"
folder in u8glib.

My conclusion is that the linker for some reason tries to include *all* code in the
utility section into the RAM bank when you compile as UNO32.

Probably some define or ifdef maybe somewhere that is missing? Unfortunatly I'm new
to u8glib and how it's working internally so i wonät fix it. But i think the problem
must be trivial to fix (i hope). :)

Thanks!

Reported by mog.pettersson on 2015-02-05 17:49:42

---

- _Attachment: [compile-link-log.txt](https://storage.googleapis.com/google-code-attachments/u8glib/issue-318/comment-0/compile-link-log.txt)_

[olikraus]

Forgot to write that i'm using Windows 7 Home Premium as OS.

Reported by mog.pettersson on 2015-02-05 17:56:32

[olikraus]

I have not used and checked chipkit for a long time.
I try to fix this for the next release, but currently i have not much time to deal
with this problem

Reported by olikraus on 2015-02-05 21:26:39

[gromgsxr]

Is there any update on this?