Hi,
I've got a weird problem. I have written a firmware: https://github.com/nyholku/TOAD4 I have two versions 1.5.3 and 1.5.5 which both work fine for me. For one user the version 1.5.5 shows very strange symptoms. This is 100% repeatable, he program 1.5.3 and everything works, he programs 1.5.5 and strange things start to happen. We have identical setups starting from OS and the actual application. He is using binary (.hex) compiled by me with SDCC 3.4.0 so even the compiler version is out of the equation. What is different is that he is using PICKit 3 with mplab_ide and I'm using PICKIt 2 with pk2cmd. Now, I'm wondering if the CONFIG bits could be different, if I do not set them all, are the other left in the state they are? In SDCC? In the programming stage (PICKit 2/3 mplab_ide/pk2cmc)? I know, I know, clutching at straws but hey, I'm desperately out of ideas and things to try... Some more possibly related info. 1.5.3 was the first version (according to my version control notes) that used SDCC 3.4.0 before that I was stuck with 2.8.9. Moving from the old SDCC to the new necessitated the change of the CONFIG words syntax. Previously I set them all, now I'm don't set every bit in the source code, only those that I think are necessary. But this does not explain why 1.5.3 and 1.5.5 work for me abd not for him because they both are compiled with the same SDCC version by me. Unless the after the compiler version change some CONFIG bits are left 'undefined' and are not programmed in which case his PIC18F4550 chip could have some CONFIG bits differently than mine. To complicate matters I tried to compile 1.5.3 again (after 7 months) and the resulting .hex is not identical to what archived back then. So maybe, just maybe, the 1.5.3 was originally compiled with SDCC 2.8.9 and my version control is screwed. So any thoughts and ideas are welcome at this point! br Kusti This e-mail may contain confidential or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. We will not be liable for direct, indirect, special or consequential damages arising from alteration of the contents of this message by a third party or as a result of any virus being passed on or as of transmission of this e-mail in general. ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user
