HI Guys,
I've got an issue when i try to compile the attached software, the compiler boots and gets as far as
Employing 18F4455 errata work-arounds:
* Corrupted fast interrupt shadow registers
* No stopping on H/W breakpoints after NOP2
Doha MK2 Vb test.c:
136: #define MX_I2C_CAL_I2C1::STOPDEL_1 (1)
^ (111) redefining preprocessor macro "MX_I2C_CAL_I2C1" (Doha MK2 Vb test.c: 135) (warning)
137: #define MX_I2C_CAL_I2C1::CHANNEL_1 (1)
^ (111) redefining preprocessor macro "MX_I2C_CAL_I2C1" (Doha MK2 Vb test.c: 135) (warning)
At this point i get a popup windows with p1.exe has stopped responding, I know this is part of the XC8 toolchain, but I have no idea how to get round this.
Any help would be greatly appriciated as I really need to get this part flow in the next couple of days.
Cheers
Matt
XC8 crash on I2C RTC component ECIO40
Moderator: Benj
-
- Posts: 18
- Joined: Fri May 09, 2014 12:47 pm
- Has thanked: 1 time
- Been thanked: 6 times
- Contact:
XC8 crash on I2C RTC component ECIO40
- Attachments
-
- Doha MK2 Vb test.fcfx
- (183.37 KiB) Downloaded 267 times
- Benj
- Matrix Staff
- Posts: 15312
- Joined: Mon Oct 16, 2006 10:48 am
- Location: Matrix TS Ltd
- Has thanked: 4803 times
- Been thanked: 4314 times
- Contact:
Re: XC8 crash on I2C RTC component ECIO40
Hi Matt,
Just tried the program here and it's compiling correctly for me. Can you tell us exactly what version of Flowcode 7 you're using. You can find out by clicking on Help -> About Flowcode. If you're not using the latest release then it might be worth updating to ensure your using the latest components and bug fixes.
I'm not even getting the warnings you reported so something must be different.
Just tried the program here and it's compiling correctly for me. Can you tell us exactly what version of Flowcode 7 you're using. You can find out by clicking on Help -> About Flowcode. If you're not using the latest release then it might be worth updating to ensure your using the latest components and bug fixes.
I'm not even getting the warnings you reported so something must be different.
Before you do update it might be worth posting your generated .C file here and then I can compare it with my .C file and see what the differences are.Employing 18F4455 errata work-arounds:
* Corrupted fast interrupt shadow registers
* No stopping on H/W breakpoints after NOP2
Memory Summary:
Program space used 2B4Ah ( 11082) of 5800h bytes ( 49.2%)
Data space used 76h ( 118) of 800h bytes ( 5.8%)
Configuration bits used 7h ( 7) of 7h words (100.0%)
EEPROM space used 10h ( 16) of 100h bytes ( 6.2%)
ID Location space used 0h ( 0) of 8h bytes ( 0.0%)
Data stack space used 0h ( 0) of 779h bytes ( 0.0%)
Regards Ben Rowland - MatrixTSL
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
-
- Posts: 18
- Joined: Fri May 09, 2014 12:47 pm
- Has thanked: 1 time
- Been thanked: 6 times
- Contact:
Re: XC8 crash on I2C RTC component ECIO40
thats odd, he's the C
im running FC 7.2.1.4 with XC1.41
im running FC 7.2.1.4 with XC1.41
- Attachments
-
- Doha MK2 Vb test.c
- (176.42 KiB) Downloaded 274 times
Last edited by beanie on Thu May 11, 2017 1:24 pm, edited 1 time in total.
- Benj
- Matrix Staff
- Posts: 15312
- Joined: Mon Oct 16, 2006 10:48 am
- Location: Matrix TS Ltd
- Has thanked: 4803 times
- Been thanked: 4314 times
- Contact:
Re: XC8 crash on I2C RTC component ECIO40
Hi Matt,
Thanks for the file, I thought I was going a bit crazy then the files were so different.
Then I noticed that you C file is saying v6.1.2?
Thanks for the file, I thought I was going a bit crazy then the files were so different.
Then I noticed that you C file is saying v6.1.2?
Regards Ben Rowland - MatrixTSL
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
-
- Posts: 18
- Joined: Fri May 09, 2014 12:47 pm
- Has thanked: 1 time
- Been thanked: 6 times
- Contact:
Re: XC8 crash on I2C RTC component ECIO40
just checked an re-upladed the correct file, them two should be massively different, sorry pal
- Benj
- Matrix Staff
- Posts: 15312
- Joined: Mon Oct 16, 2006 10:48 am
- Location: Matrix TS Ltd
- Has thanked: 4803 times
- Been thanked: 4314 times
- Contact:
Re: XC8 crash on I2C RTC component ECIO40
Perfect thanks Matt,
Looks like the compilation error is coming from the defines of the RTC component. There is a slightly newer version of the component here that looks to have fixed the problem.
viewtopic.php?f=63&t=18876
Let me know how you get on and if this solves it for you then I'll add this to the main updates archive.
Looks like the compilation error is coming from the defines of the RTC component. There is a slightly newer version of the component here that looks to have fixed the problem.
viewtopic.php?f=63&t=18876
Let me know how you get on and if this solves it for you then I'll add this to the main updates archive.
Regards Ben Rowland - MatrixTSL
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
-
- Posts: 18
- Joined: Fri May 09, 2014 12:47 pm
- Has thanked: 1 time
- Been thanked: 6 times
- Contact:
Re: XC8 crash on I2C RTC component ECIO40
Hi Ben,
That sorted the compilation error cheers. However using an ECIO40 I2C channel with these routines (initialise(), GetDate(), time, etc) the code locks up after initialise and before the the first register value from the DS3231 is returned. I've scoped B0 and B1 and nothing looks to be coming out of the micro, both lines are held up with 4K7s and the clock is the only component on the bus.
Any thoughts?
That sorted the compilation error cheers. However using an ECIO40 I2C channel with these routines (initialise(), GetDate(), time, etc) the code locks up after initialise and before the the first register value from the DS3231 is returned. I've scoped B0 and B1 and nothing looks to be coming out of the micro, both lines are held up with 4K7s and the clock is the only component on the bus.
Any thoughts?
- Benj
- Matrix Staff
- Posts: 15312
- Joined: Mon Oct 16, 2006 10:48 am
- Location: Matrix TS Ltd
- Has thanked: 4803 times
- Been thanked: 4314 times
- Contact:
Re: XC8 crash on I2C RTC component ECIO40
Hmm, Have you tried the software I2C channel. That should work correctly.
I'll see if I can replicate this here and work out what's going wrong with the hardware I2C channel on the ECIO40P device.
I'll see if I can replicate this here and work out what's going wrong with the hardware I2C channel on the ECIO40P device.
Regards Ben Rowland - MatrixTSL
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
- Steve001
- Valued Contributor
- Posts: 1189
- Joined: Wed Dec 31, 2008 3:37 pm
- Has thanked: 460 times
- Been thanked: 523 times
- Contact:
Re: XC8 crash on I2C RTC component ECIO40
Hi Ben
Not sure if this is relevant or not. I have had problems have been playing with johns post with an ECIO40P
viewtopic.php?f=29&t=8607
Thought it was me doing something wrong
Steve
Not sure if this is relevant or not. I have had problems have been playing with johns post with an ECIO40P
viewtopic.php?f=29&t=8607
Thought it was me doing something wrong
Steve
Success always occurs in private and failure in full view.