MCB2300 compile warnings

[RichardJennings]

Hello, I have the ARM 1.0 eval with LV 8.5.1 and uVision v3.80. I'm using the MCB2300 eval board and I've tested the board and tools with uVision's examples. I can't run LabVIEW's Blinky however. I get the following warning:

linking...
.\Obj\LabVIEW.sct(15): warning: L6314W: No section matches pattern LPC23_EMAC.o(ZI).
.\Obj\LabVIEW.sct(15): warning: L6314W: No section matches pattern LPC23_EMAC.o(RW).
Program Size: Code=47600 RO-data=9304 RW-data=1000 ZI-data=24056 
".\Obj\LabVIEW.axf" - 0 Error(s), 2 Warning(s).

Then the build fails. When I try to find the problem in uVision I'm pointed to line 15 of this file:

; *************************************************************
; *** Scatter-Loading Description File generated by uVision ***
; *************************************************************

LR_IROM1 0x00000000 0x00080000  {    ; load region size_region
  ER_IROM1 0x00000000 0x00080000  {  ; load address = execution address
   *.o (RESET, +First)
   *(InRoot$$Sections)
   .ANY (+RO)
  }
  RW_IRAM1 0x40000000 0x00008000  {  ; RW data
   .ANY (+RW +ZI)
  }
  RW_RAM1 0x7FE00000 0x00004000  {
    LPC23_EMAC.o (+ZI +RW)
  }
  RW_IRAM2 0x7FD00000 0x00002000  {
   .ANY (+RW +ZI)
  }
}

Any thoughts?

Richard 

[Gmg]

That is really strange that the build fails from warnings...

Surely it must be something else that is causing the failure, as I see these sort of warnings all the time on the MCB2300.

Anyway, this warning is because the LPC23_EMAC file is memory mapped to a region, but there is nothing in this file to map (as compiler removed these by optimization).

To fix this, you can actually open up uVision, right click on the LPC23_EMAC file and change the memory map options from a specific region to just "default".

[RichardJennings]

That was the first build that failed. Previously it would download, run and fail. Attached is the screenshot of when it fails.

I tried to modify the file as suggested, but uVision just over writes it with an identical file.

[LaRisa_M]

Hi Richard,

From your screenshot, it doesn't look like the program has failed in any way. Can you explain what you're showing in that picture? Is the example failing to build or failing to run? Had you made any changes to the example or the ARM module before running into problems with this example? Have you made any changes since? Have you had an opportunity to try this example in a newer version of ARM (1.1 or 2009)?

[RichardJennings]

When I run uVision's version of blinky, it actually runs. The LabVIEW version runs briefly and then the processor stops as you can see in the graphic. As far as I know I don't have a breakpoint set.

Richard

[G-Money]

Richard,

       I am working with our R&D Team to go over the error message because I couldn't find any references on it. I am not able to reproduce the error myself so that leds me to believe that it is strictly your board or software. You might double check that the stop button on Blinky isn't pressed down by default but I don't believe this is the case because you said it runs for a little bit (multiple blinks). Something just to try while I dig a little deeper on this for you. I promise you that I will try my best to get you back up and running in the shortest amount of time possible. Thanks for your patientce!!

[RichardJennings]

I don't get any blinks with the LV build. The development environment downloads, says running, the the red light comes on and the processors stops at the same location. I'm using uVision 3.8, LV 8.5.1 and Arm 1.0. I haven't been able to get any of the MCB2000 examples to run under LabVIEW.

[G-Money]

Richard,

       You're quick on the uptake I came back to post again and you had already posted. I was going to give you my copy of Blinky which I just verified works with ARM 1.0 and LV 8.5.1. Just put it on the desktop and try to run this one. If you still can't run it then that tells me that something is different in our boards or are Keil compilers. I also noticed immediately after I posted that your Stop button wasn't pressed down in your screenshot so forget I posted that before  Let me know if you are able to run this or not. Thanks!! 

[NicB]

As Gmg said already, those warnings appear because there is nothing to map in those regions – that happen for all application that does not use Ethernet. You cannot modify the file since it is generated automatically based on the settings from "Target" tab.
Just to feel better you can suppress warnings by filling "Extra linker flags" field from "Build Specification Properties"/"Advanced Compiler Options" of the project with:

--diag_suppress=L6314

(I would do this for all newer LabVIEW versions. A better solution would be adding the command in Misc Controls in the Linker tab of template, but LabVIEW overwrite the field.)

From the picture provided I see your program stopping in SWI_Handler (actually an invalid function). Since you are using LV8.5 and a newer version of  MDK-ARM, perhaps you RTX_Config.c is not properly configured. Here it is such a file that should go to "Targets\Keil\Embedded\RealView\MCB2300\Template\System"

You can backup the old file and then copy this one. Since you are in the Template folder go to the project (..\Project\LabVIEW.Uv2) open it in uVision and go to Device tab where you could select any other device (e.g. LPC2220) and then select again LPC2378. ... Verify if the "Parameters" from Debug tab are properly (cLPC237x and pLPC2378) ... Press OK

Just to be sure remove the Application folder from your project and rebuild it from LabVIEW.

Good Luck

[NicB]

Ooops,

I just noticed that Target settings is alterred when switching from a target to another.

Richard, I hope your template uVision project look like in this picture:

 

Grant, the linker "disable warnings" settings could go to the template for a good looking screen for all "non-Ethernet" applications (in any version).