@ Gus, I think it would be really great if we could get this merged into the codeplex source. That way the community does not have to jump through additional hoops to get the Cerberus family firmware building with GCC and GCC bits will remain current as the code base evolves.
@ patc - Are you using the 4.2 or 4.3 porting kit? I checked the repository and I see that 4.2 has lwip\lwip_1_3_2 while 4.3 has lwip\lwip. I did not check the actual 4.3 porting kit, I just checked the 4.3 code base which is similar.
Anyone else getting an issue where ToString(“F2”) on a double is not formatting, is something being stubbed out from corlib, FormatNative perhaps, seems to do it on the 4.3 build as well.
@ Aron - It is not exactly the same as for hydra, the scatterfile for cerberus doesn’t have “RELOC_RAM”, and memory constraints aren’t the same.
Someone got a scatterfile working for gcc 4.6.2 and ethernet activated ?
with the standard scatterfile provided by the patch I got :
C:\GCC_4_6_3\bin…\arm-none-eabi\bin\ld.exe: C:\MicroFrameworkPK_v4_2\BuildOutput\THUMB2\GCC4.6\le\FLASH\release\FEZCerberus\bin\tinyclr.axf section .bss' will not fit in regionRAM’
C:\GCC_4_6_3\bin…\arm-none-eabi\bin\ld.exe: region `RAM’ overflowed by 12708 bytes
What I was referring to what was the same on Hydra was only the project file to activate the Ethernet firmware vs. Non Ethernet firmware. Yes, you are correct that the memory constraints are indeed different on the Cerberus vs Hydra.