Compile error using KDS - Interrupt/Exception

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Compile error using KDS - Interrupt/Exception

Jump to solution
1,974 Views
Donsnook
Contributor II

15:26:38 **** Incremental Build of configuration Debug for project Peak ****

make -k pre-build main-build

make: Interrupt/Exception caught (code = 0xc0000005, addr = 0x00411244)

 

15:26:39 Build Finished (took 170ms)

Labels (1)
1 Solution
1,671 Views
BlackNight
NXP Employee
NXP Employee

Hi Don,

can you check if you have any breakpoints or expressions/watchpoints set?

See http://mcuoneclipse.com/2014/10/11/failed-to-debug-with-gdb-breakpoints-or-expressions-on-non-existi...

I hope this helps,

Erich

View solution in original post

8 Replies
1,671 Views
Alice_Yang
NXP TechSupport
NXP TechSupport

Hello Don,

Please tell us your project in detailed ,  which chip ?  And  bareboard ? with PE ? SDK?

Then we can help you as soon as possible .

Best Regards

Alice

0 Kudos
Reply
1,671 Views
Donsnook
Contributor II

I'm using K22 freedom board, I have the USB setup as a CDC device, RTC enabled I'm working on setting up the SPI with DMA when I started seeing this. The first time I close SDK restarted was ok for a while. It starting happen again rebooted PC still had issues close out some other programs that I run on PC and was able to compile.

0 Kudos
Reply
1,671 Views
Alice_Yang
NXP TechSupport
NXP TechSupport

Hi Don,

Under the SDK, there is a "dspi_edma_demo" (C:\Freescale\KSDK_1.0.0\demos\dspi_edma_demo\kds), you can refer to this .

First run this demo on you board , then compare it with  your project .

Wish it helps you!
If you still have question, please contact me!

Alice

0 Kudos
Reply
1,671 Views
Donsnook
Contributor II

another strange issue unable to debug k22 freedom board or CDI hardware board base on K22 freedom

loading programming algorithm ...

  1. Done.

CMD>PM

  1. Programming.

Processing Object File Data ...

                               

.

  1. Programmed.

CMD>VC

Verifying object file CRC-16 to device ranges ...

   block 00000000-0000040F ...

  1. Ok.

   block 00000420-00019B0F ...

  1. Ok.

   Checksum Verification Successful. (Cumulative CRC-16=$AD31)

CMD>RE

  1. Initializing.

Target has been RESET and is active.

Disconnected from "127.0.0.1" via 127.0.0.1

Terminating Gracefully...

Target Disconnected.

0 Kudos
Reply
1,672 Views
BlackNight
NXP Employee
NXP Employee

Hi Don,

can you check if you have any breakpoints or expressions/watchpoints set?

See http://mcuoneclipse.com/2014/10/11/failed-to-debug-with-gdb-breakpoints-or-expressions-on-non-existi...

I hope this helps,

Erich

1,671 Views
Donsnook
Contributor II

Erich,

I had break points but all were uncheck what I had to do is delete all break points

thanks

0 Kudos
Reply
1,671 Views
BlackNight
NXP Employee
NXP Employee

Yes, you have to delete them. Unchecking seems not be enough.

Erich

1,671 Views
Alice_Yang
NXP TechSupport
NXP TechSupport

Hi Don,

Do you debug refer to the "kds_user_guide.pdf"-> 4.2 Debugging with the Kinetis Design Studio IDE   ? (C:\Freescale\KDS_1.1.1\doc\pdf)

If you still have question, please contact us!

Best Regards

Alice

0 Kudos
Reply