Compiling multicore examples in LPCXpresso v7

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

Compiling multicore examples in LPCXpresso v7

557 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by JohnR on Mon Mar 10 18:06:53 MST 2014
Hi All,

Using LPCXpresso v7.0.0, I am trying to run the multicore examples in lpcopen_2_04_lpcxpresso_nxp_lpclink2_4370.

Using the wizards in C:\nxp\LPCXpresso_7.0.0_92\lpcxpresso\Wizards\MemConfigs\NXP I can compile mc_sa_blinky_m4 using LPC4370_SPIFI_1MB.

But I cannot get mc_sa_blinky_m0app or LPC4370_SPIFI_1MB projects to accept LPC4370_M0APP or LPC4370_M0SUB using the External Memory configuration dialog boxes. The dialog boxes show the flash properly when it is first imported but not if the dialog box is reopened.

From app_multicore_cfg.h the expected address should be set to BASE_ADDRESS_M0APP     (SPIFI_BASE_ADDR + IMG_SZ_M4)

What am I missing here, I have read the latest user guide.

Thanks again in advance,

JohnR.
0 Kudos
7 Replies

507 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by JohnR on Wed Mar 12 12:27:29 MST 2014
Please ignore my last message - I had forgotten to replace the JP1 jumper. Now all seems to work.

John.
0 Kudos

507 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by JohnR on Wed Mar 12 07:23:05 MST 2014
Hi,

I downloaded LPCXpresso v7.0.2 and life is much better.

blinky_M0app and blinky_M0sub were recompiled for the suggested flash addresses and added to the flash.

blinky_M4 was added to the flash and now runs and the LED flashes as long as the debugger has started it and continues to run if the debugger shut down.

If I power off and on, blinky_M4 does not restart.

The only problem seems to be now that M4 is not self-starting but seems to need the debugger to be running??

Again - what am I doing wrong?

Thanks

John.







0 Kudos

507 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by JohnR on Tue Mar 11 11:05:55 MST 2014
Thanks _ I was starting to realise that I _was_ wasting my time.
0 Kudos

507 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Tue Mar 11 09:06:10 MST 2014
The fixed version should be released tomorrow, so you may want to wait for that instead of wasting your time.
0 Kudos

507 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by JohnR on Tue Mar 11 09:03:57 MST 2014
Hi,

It looks as if the problem is in the dialog box refresh as well as the definitions of the M0App and M0Sub xml files.

I copied/renamed the LPC4370_SPIFI_1MB to M0App_1 and loaded into the dialog box and modified the ORIGIN value

MEMORY
{
  /* Define each memory region */
  SPIFI_1024 (rx) : ORIGIN = 0x14010000, LENGTH = 0x100000 /* 1M bytes */

So far so good, now I will do the same for M0Sub and see if the whole thing works.

John
0 Kudos

507 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by JohnR on Tue Mar 11 05:03:12 MST 2014
Hi,

Thanks for reply.

Can I use the same sort of fix adding  prebuild steps as in Red Suite eg

rm -f M0bin/m0bin.o ; rm -f ../M0bin/CM0image.bin; cp "${workspace_loc:}/SGPIO_M0_1/Debug/SGPIO_M0_1.bin" ../M0bin/CM0image.bin

except that I should replace .bin with .o

John
0 Kudos

507 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Tue Mar 11 01:17:28 MST 2014
Hi,

This is due to a bug in the Memory Config Editor in v7.0.0. This is fixed in 7.0.2 which will be released very soon. Sorry for the inconvenience.
0 Kudos