2089726_en-US

Type Fixup overflow in adc_int, to ix.2 type 1, at offset 0x10B C/C++ Problem

Hi, I am porting old code from the Cosmic compiler for MC9S08DZ60ACLH to Code Warrior 11.1, which is the last version that supports this processor. I am getting a bunch of errors that I don't understand:

Fixup overflow in adc_int, to ix.2 type 1, at offset 0x1D (filename)C/C++ Problem

Can anyone tell me what this means? I'll post a screenshot of the whole list of errors.

Lloyd

Re: Type Fixup overflow in adc_int, to ix.2 type 1, at offset 0x10B C/C++ Problem

I'm glad to hear that you managed to replicate the outcome on your side.

Thank you for bringing this to our attention, I will notify the internal team about this matter.

Best Regards,
Pablo

Re: Type Fixup overflow in adc_int, to ix.2 type 1, at offset 0x10B C/C++ Problem

Yes @Pablo_Ramos it worked and I very much appreciate you finding this out. But there never was a warning message from the compiler that @tiny was not supported. So I have wasted about 6 weeks because the compiler doesn't flag an error for this declaration. How can I report this so it will be fixed for the next person who has to port Cosmic code to NXP?

Thanks,

Lloyd

Re: Type Fixup overflow in adc_int, to ix.2 type 1, at offset 0x10B C/C++ Problem

I noticed that some variables still use the @tiny keyword, which is not supported in CodeWarrior.

After removing the @tiny keyword, I was able to successfully compile the project.

Could you please help verify if you can replicate this behavior by removing the @tiny keyword on your end?

Best regards,
Pablo

Re: Type Fixup overflow in adc_int, to ix.2 type 1, at offset 0x10B C/C++ Problem

Thanks @Pablo_Ramos , can't wait to put this error behind me so I can start working on the operation of the product.

Lloyd

Re: Type Fixup overflow in adc_int, to ix.2 type 1, at offset 0x10B C/C++ Problem

Hi,

Thanks, I have received your private message with the files. I'm running some tests and will let you know of any progress.

Best Regards,
Pablo

Re: Type Fixup overflow in adc_int, to ix.2 type 1, at offset 0x10B C/C++ Problem

Hi @Pablo_Ramos , I sent you a private message with the projects attached.

Thanks,

Lloyd

Re: Type Fixup overflow in adc_int, to ix.2 type 1, at offset 0x10B C/C++ Problem

Yes @Pablo_Ramos I can send you the whole project. Can you tell me how to send it directly to you without posting it in public?

Thanks,

Lloyd

Re: Type Fixup overflow in adc_int, to ix.2 type 1, at offset 0x10B C/C++ Problem

Apologies for the delay in getting back to you.

I’ve tried to replicate the issue on my end but haven’t been able to reproduce it. If you could share the project with me, that would be very helpful in identifying the problem more accurately.

Looking forward to your response.

Best regards,
Pablo

Re: Type Fixup overflow in adc_int, to ix.2 type 1, at offset 0x10B C/C++ Problem

Hi @ZhangJennie ,

You were able to help me with another problem, can you take a look at this one? The error messages are a complete mystery to me.

Thanks,

Lloyd Slonim

Re: Type Fixup overflow in adc_int, to ix.2 type 1, at offset 0x10B C/C++ Problem

Hi @Pablo_Ramos I'm back on this project after time away. I still can't figure out anything that is causing these 14 errors. Can I send you the whole project zipped up for you to look at? This is a totally normal C function with no modifiers and no special linker commands. This is preventing me from doing any work on the project.

Thanks,

Lloyd

Re: Type Fixup overflow in adc_int, to ix.2 type 1, at offset 0x10B C/C++ Problem

The function is very simple. There are no special linker commands, and no special memory directives, it's just the default that the IDE uses. Can you tell me exactly what the error message means?

void adc_init(void) /* init adc */
{
ADCCFG = ADCCFG_VAL;
APCTL1 = 0x08;
APCTL2 = 0x00;
APCTL3 = 0xE0;
// analog input conversion sequence initiated by 1ms timer interrupt
}

Re: Type Fixup overflow in adc_int, to ix.2 type 1, at offset 0x10B C/C++ Problem

Could you help me with further explanation on your settings?

Are you using noncontiguous memory areas?

How are you declaring adc_init function?

Could you share with me the section of code where the error is happening?