Switching form one CPU to another

[lpcware]

Content originally posted in LPCWare by chucks13 on Tue Mar 19 13:46:26 MST 2013
I have a project running on the 1769. I want to migrate it to the 1758.

So far, I have had no success. I have tried copying the workspace, and opening it as a different project, and setting the CPU type under project properties. The download fails, because it seems to still be looking for a 1768 (It seems 1769 wants to build as 1768), but it is finding a chip ID of 1758.  So I have missed something and not properly changed the chip type completely.

I have also tried making a new workspace under 1758, and importing my 1769 project into it. It builds, but when I try to debug, it wants me to create a new debug setup, and I am not setting something properly, because I get a problem with an error like "Error while launching command: gdb --version".

So, what is the magic Mojo I need to build and download the project to 1758?

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Thu Aug 29 08:00:53 MST 2013
The bootloader will not execute use code if:
- the ISP or RESET pins are held in the wrong state
- the flash checksum is incorrect

Have you read the FAQ at:
http://support.code-red-tech.com/CodeRedWiki/HardwareDebugConnections

[lpcware]

Content originally posted in LPCWare by jnewell on Thu Aug 29 07:07:33 MST 2013
Well, the issue of the processor only running in the bootROM.

" Thread [1] (Suspended: Signal 'SIGINT' received. Description: Interrupt.)   
    2 <symbol is not available> 0x1fff0ba4   
    1 <symbol is not available> 0x1fff0cbe   
"

I was able to replicate the issue on the eval board I have (RDB1768 v2) by holding down the ISP button while trying to upload code or while resetting.

The thing is, the ISP pin on my board (custom board) was originally floating (I knew that it wasn't supposed to be LOW). I have tried using a 10K pullup on the ISP with the same outcome.

-Josh

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Wed Aug 28 03:07:40 MST 2013
What specific error?

It would be really useful if you could explain what your problem is and what you have done to try to resolve it yourself.

[lpcware]

Content originally posted in LPCWare by jnewell on Tue Aug 27 13:37:34 MST 2013
Was a fix ever found for this specific error? I have run into the same situation and it's really got me stumped.

Any information would be great.

Thanks,
Josh

[lpcware]

Content originally posted in LPCWare by chucks13 on Tue Mar 19 14:48:13 MST 2013
Well, that's funny. I if I'm in the boot loader, I assume that the boot jumper on P2:10 is grounded, and sure enough, it seems to be. Now I need to get a bench tech to track it down.

Thanks, By the way, I'm really grateful that someone is reading these posts and helped me.

[lpcware]

Content originally posted in LPCWare by Ex-Zero on Tue Mar 19 14:37:35 MST 2013
Congratulation, you're in BOOT ROM :)

---

Quote:

Boot ROM 0x1FFF 0000 - 0x1FFF 1FFF 8 kB Boot ROM with flash services.

---

Switching to ISP is working fine with your new hardware :D

http://www.support.code-red-tech.com/CodeRedWiki/HardwareDebugConnections

[lpcware]

Content originally posted in LPCWare by chucks13 on Tue Mar 19 14:25:39 MST 2013
OK, I did it again and this time it worked and downloaded. I'm not sure what went wrong.
Now to figure out why I can't seem to set a working breakpoint on ResetISR. My build for the 1769 stops correctly, but this 1758 build doesn't and I get this in the stack when I pause:

Thread [1] (Suspended: Signal 'SIGINT' received. Description: Interrupt.)   
    2 <symbol is not available> 0x1fff0ba4   
    1 <symbol is not available> 0x1fff0cbe   

This is new hardware, so I suspect that something is causing an interrupt even before it gets to reset, which seems strange, because they should not be enabled yet. This has been holding me up for several days now, and I know it seems desperate, but if anyone out there has seen this kind of thing before, I could really use some insight.

[lpcware]

Content originally posted in LPCWare by Ex-Zero on Tue Mar 19 13:55:22 MST 2013
Changing MCU should be enough :)

http://www.support.code-red-tech.com/CodeRedWiki/InvalidPart