LPCXpressor NHS3100SENSORADK Heap

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

LPCXpressor NHS3100SENSORADK Heap

7,765 Views
stevekuh
Contributor III

Hello,

Below is the current error message:

07:04:36 **** Build of configuration Debug for project app_demo_dp_blinky ****

make -r -j4 all

Building file: ../src/crp.c

Building file: ../src/mainblinky.c

Invoking: MCU C Compiler

arm-none-eabi-gcc -std=c99 -DDEBUG -D__CODE_RED -DCORE_M0PLUS -D__REDLIB__ -I"C:\Users\Appa2\Documents\LPCXpresso_8.2.2_650\workspace\lib_chip_nss" -I"C:\Users\Appa2\Documents\LPCXpresso_8.2.2_650\workspace\lib_board_dp" -I"C:\Users\Appa2\Documents\LPCXpresso_8.2.2_650\workspace\lib_board_dp\inc" -I"C:\Users\Appa2\Documents\LPCXpresso_8.2.2_650\workspace\lib_chip_nss\inc" -I"C:\Users\Appa2\Documents\LPCXpresso_8.2.2_650\workspace\mods" -I"C:\Users\Appa2\Documents\LPCXpresso_8.2.2_650\workspace\app_demo_dp_blinky\mods" -I"C:\Users\Appa2\Documents\LPCXpresso_8.2.2_650\workspace\lib_board_dp\mods" -I"C:\Users\Appa2\Documents\LPCXpresso_8.2.2_650\workspace\lib_chip_nss\mods" -include"C:\Users\Appa2\Documents\LPCXpresso_8.2.2_650\workspace\lib_chip_nss\mods\chip_sel.h" -include"C:\Users\Appa2\Documents\LPCXpresso_8.2.2_650\workspace\lib_board_dp\mods\board_sel.h" -include"C:\Users\Appa2\Documents\LPCXpresso_8.2.2_650\workspace\app_demo_dp_blinky\mods\app_sel.h" -Og -g3 -pedantic -Wall -Wextra -Wconversion -c -fmessage-length=0 -fno-builtin -ffunction-sections -fdata-sections -mcpu=cortex-m0 -mthumb -D__REDLIB__ -specs=redlib.specs -MMD -MP -MF"src/crp.d" -MT"src/crp.o" -MT"src/crp.d" -o "src/crp.o" "../src/crp.c"

Invoking: MCU C Compiler

arm-none-eabi-gcc -std=c99 -DDEBUG -D__CODE_RED -DCORE_M0PLUS -D__REDLIB__ -I"C:\Users\Appa2\Documents\LPCXpresso_8.2.2_650\workspace\lib_chip_nss" -I"C:\Users\Appa2\Documents\LPCXpresso_8.2.2_650\workspace\lib_board_dp" -I"C:\Users\Appa2\Documents\LPCXpresso_8.2.2_650\workspace\lib_board_dp\inc" -I"C:\Users\Appa2\Documents\LPCXpresso_8.2.2_650\workspace\lib_chip_nss\inc" -I"C:\Users\Appa2\Documents\LPCXpresso_8.2.2_650\workspace\mods" -I"C:\Users\Appa2\Documents\LPCXpresso_8.2.2_650\workspace\app_demo_dp_blinky\mods" -I"C:\Users\Appa2\Documents\LPCXpresso_8.2.2_650\workspace\lib_board_dp\mods" -I"C:\Users\Appa2\Documents\LPCXpresso_8.2.2_650\workspace\lib_chip_nss\mods" -include"C:\Users\Appa2\Documents\LPCXpresso_8.2.2_650\workspace\lib_chip_nss\mods\chip_sel.h" -include"C:\Users\Appa2\Documents\LPCXpresso_8.2.2_650\workspace\lib_board_dp\mods\board_sel.h" -include"C:\Users\Appa2\Documents\LPCXpresso_8.2.2_650\workspace\app_demo_dp_blinky\mods\app_sel.h" -Og -g3 -pedantic -Wall -Wextra -Wconversion -c -fmessage-length=0 -fno-builtin -ffunction-sections -fdata-sections -mcpu=cortex-m0 -mthumb -D__REDLIB__ -specs=redlib.specs -MMD -MP -MF"src/mainblinky.d" -MT"src/mainblinky.o" -MT"src/mainblinky.d" -o "src/mainblinky.o" "../src/mainblinky.c"

Finished building: ../src/crp.c

 

Finished building: ../src/mainblinky.c

 

Building target: app_demo_dp_blinky.axf

Invoking: MCU Linker

arm-none-eabi-gcc -nostdlib -L"C:\Users\Appa2\Documents\LPCXpresso_8.2.2_650\workspace\lib_board_dp\Debug" -L"C:\Users\Appa2\Documents\LPCXpresso_8.2.2_650\workspace\lib_chip_nss\Debug" -Xlinker -Map="app_demo_dp_blinky.map" -Xlinker --gc-sections -mcpu=cortex-m0 -mthumb -T "app_demo_dp_blinky_Debug.ld" &Heap:Default;Post Data;Default&Stack:Default;End;Default -o "app_demo_dp_blinky.axf"  ./src/crp.o ./src/mainblinky.o   -llib_board_dp -llib_chip_nss

/bin/sh: Heap:Default: command not found

/bin/sh: Post: command not found

/bin/sh: Default: command not found

/bin/sh: Stack:Default: command not found

/bin/sh: End: command not found

/bin/sh: Default: command not found

make: *** [app_demo_dp_blinky.axf] Error 127

c:/nxp/lpcxpresso_8.2.2_650/lpcxpresso/tools/bin/../lib/gcc/arm-none-eabi/5.4.1/../../../../arm-none-eabi/bin/ld.exe: Linker CRP Enabled, but no CRP_WORD provided within application

c:/nxp/lpcxpresso_8.2.2_650/lpcxpresso/tools/bin/../lib/gcc/arm-none-eabi/5.4.1/../../../../arm-none-eabi/bin/ld.exe: warning: cannot find entry symbol ResetISR; defaulting to 00000000

collect2.exe: error: ld returned 1 exit status

 

07:04:36 Build Finished (took 802ms)

 

It seems to be having an issue with "Invoking: MCU Linker" and the common commands are not found. How do you resolve this issue? 

Thank you.

 

0 Kudos
24 Replies

4,347 Views
patrickgeens
NXP Apps Support
NXP Apps Support

Hi Stevekuh,

 

The newer releases of the SDK are not supported in LPCXpresso.

The MCUXpresso IDE v11.7 or higher up is now the only supported IDE.

 

https://www.nxp.com/webapp/sps/download/license.jsp?colCode=release_mra2_nhs3100&appType=file1&DOWNL...

 

Release 12.6 - 2023-03-31

NOTE: THIS IS THE STABLE RELEASE IN THE SDK 12.X SERIES.
UPGRADING FROM OLDER SDKS IS RECOMMENDED FOR ALL USERS.

1.1 NEW FEATURES
• Setup of the development environment has been simplified. From the MCUXpresso IDE v11.7 onward, the NHS31xx ICs are fully supported by a fresh installation of the IDE, without the need for an extra plugin.

1.2 INCOMPATIBILITIES
• Support for the MCUXpresso IDE v10.2.1 is now fully dropped. The MCUXpresso IDE v11.7 or higher up is now the only supported IDE. Project files of all applications are updated. Output from external processes that is used to predefine macros, are now invoked differently.

 

Kind regards,

Patrick

0 Kudos

4,358 Views
stevekuh
Contributor III

Where can I download the source code to the Android App "SensorBoard App" that reads the temperature from the NHS3100 board?

0 Kudos

4,349 Views
patrickgeens
NXP Apps Support
NXP Apps Support

Hi Stevekuh,

 

Source code of the SensorBoardMonitor app is in:

patrickgeens_0-1683189265767.png

Kind regards,

Patrick

0 Kudos

4,198 Views
stevekuh
Contributor III

Hi,

Our PCB is exhibiting only 5 ft of range when RFID is being read by FX9500 Zebra RFID Reader. We suspect that the PCB layer thickness spec is not correct. Could you let me know what are the PCB layer thickness spec for the RFID antenna portion of the NHS3100 Sensor Board?

0 Kudos

4,190 Views
patrickgeens
NXP Apps Support
NXP Apps Support

Hi Stevekuh,

 

The demo pcb is standard 1.6mm FR4 material.

Proximity to metal parts can de-tune the antenna. A test could be to remove all metal parts from your pcb and test the UHF part standalone.

 

Kind regards,

Patrick

 

0 Kudos

4,188 Views
stevekuh
Contributor III

Do you have a specification for the PCB stack? The thickness of the dielectric material would also have effect on the performance of the antenna.

0 Kudos

7,623 Views
stevekuh
Contributor III

Could you send instructions on how to install the plugin?

0 Kudos

7,614 Views
danielchen
NXP TechSupport
NXP TechSupport

Hi @stevekuh 

Please refer to below picture.

danielchen_0-1673076790633.png

 

0 Kudos

7,609 Views
stevekuh
Contributor III

Successfully installed NHS3100. Compiled good with NHS3100 selected as MCU. Upon programming the error msg shown as attached. 

0 Kudos

7,598 Views
danielchen
NXP TechSupport
NXP TechSupport

HI,

The error is "can not connect to core", I would suggest you check the debug probe you are using, update the firmware in it.   or try another debug probe

 

Regards

Daniel

0 Kudos

7,595 Views
stevekuh
Contributor III

- Installed LPC Link2 USB driver package (Rev 2.0.2 May 11 2014)

==> didn't help

- closed JP2 on LPC Link2 PCB (apparently supplies 3.3v power to the target)

- produced different error msg as attached

0 Kudos

7,581 Views
stevekuh
Contributor III

JP2 power to J7.JPGErr after JP2 closed.JPG

 

I am using LPC-Link2 to program the NHS3100SENSORADK.

After closing the JP2 jumper on the LPC-Link2 PCB, I now have a different error message as shown above. How do I resolve this issue?

Tags (1)
0 Kudos

7,570 Views
danielchen
NXP TechSupport
NXP TechSupport

I would suggest you check the memory details in your project.

For example, the app_demo_dp_blinky , 

danielchen_0-1673620233944.png

 

Please refer to UM11153 (NHS31XX getting started ) for more details.

 

Regards

Daniel

0 Kudos

7,565 Views
stevekuh
Contributor III

- after fixing the memory and setting the flash driver to NSS_30k_8k_IAP.cfx, the blinky example compiled and flashed with no error.

- had to modify the led pin to PIO_8 (we are using NHS3100SENSORADK) since the default LED was set for Pin 7.

- now, I would like to compile and flash the default demo program that NHS3100SENSORADK shipped with and interfaced with an Android App (SensorBoard Monitor). Could you send us the demo code for this?

Tags (1)
0 Kudos

7,545 Views
patrickgeens
NXP Apps Support
NXP Apps Support

Hi Stevekuh,

 

The source code for the SensorBoard firmware is in the NHS3100 SDK that can be downloaded at:

https://www.nxp.com/webapp/Download?colCode=release_mra2_nhs3100&appType=license

 

The "release_mra2_12_5_nhs3100\sw\nss\app_demo_dpahu_sensormonitor" project is the one you need.

patrickgeens_0-1673864445391.png

 

Kind regards,

Patrick

7,474 Views
stevekuh
Contributor III

- compiled app_demo_dpahu_sensormonitor 

- error generated as below:

- the issue is that the compiler is unable to find part support for NXP NHS3100 in project app_demo_dpahu_sensormonitor. It reset to a generic part. But, the project MCU Setting is set to NHS3100 with proper memory config.

 

Error after Build ddahu sensormonitor.JPG

0 Kudos

7,471 Views
stevekuh
Contributor III

Actually, I am not sure if the Error msg is accurate. I flashed the ADK and received the following:

Executing flash operation 'Program' (Program file into flash: app_demo_dpahu_sensormonitor.axf) - Thu Jan 19 06:39:20 PST 2023
Checking MCU info...
Scanning for targets...
Executing flash action...
MCUXpresso IDE RedlinkMulti Driver v10.2 (Jul 25 2018 11:25:37 - crt_emu_cm_redlink.exe build 555)
( 0) Reading remote configuration
Wc(03). No cache support.
( 5) Remote configuration complete
Reconnected to existing link server
Connecting to probe 1 core 0:0 (using server started externally) gave 'OK'
Probe Firmware: LPC-LINK2 CMSIS-DAP V5.183 (NXP Semiconductors)
Serial Number: FTCSH0GS
VID:PID: 1FC9:0090
USB Path: \\?\hid#vid_1fc9&pid_0090&mi_00#7&39129f89&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Using memory from core 0:0 after searching for a good core
( 30) Emulator Connected


( 40) Debug Halt
( 50) CPU ID
debug interface type = Cortex-M0+ (DAP DP ID 0BC11477) over SWD TAP 0
processor type = Cortex-M0+ (CPU ID 00000C60) on DAP AP 0
number of h/w breakpoints = 4
number of flash patches = 0
number of h/w watchpoints = 2
Probe(0): Connected&Reset. DpID: 0BC11477. CpuID: 00000C60. Info: <None>
Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.
Content of CoreSight Debug ROM(s):
RBASE E00FF000: CID B105100D PID 04000BB4C0 ROM dev (type 0x1)
ROM 1 E000E000: CID B105E00D PID 04000BB008 ChipIP dev SCS (type 0x0)
ROM 1 E0001000: CID B105E00D PID 04000BB00A ChipIP dev DWT (type 0x0)
ROM 1 E0002000: CID B105E00D PID 04000BB00B ChipIP dev FPB (type 0x0)
Inspected v.1 On-chip Flash Memory NSS_30k_8k_IAP.cfx
Image 'NSS @ 0x1fff1ff1 (May 18 2015 11:15:32)'
NXP: NHS3100
( 65) Chip Setup Complete
Connected: was_reset=true. was_stopped=false
( 70) License Check Complete
Loading 'app_demo_dpahu_sensormonitor.axf' ELF 0x00000000 len 0x75A0
Opening flash driver NSS_30k_8k_IAP.cfx
Sending VECTRESET to run flash driver
Writing 30112 bytes to address 0x00000000 in Flash
( 0) Mass erasing Flash
Mass erased flash in 304msec
1 of 1 ( 0) Writing pages 0-29 at 0x00000000 with 30112 bytes
( 0) at 00000000: 0 bytes - 0/30112
verify offset 0x0/0x75A0[0x400/0x400]
( 3) at 00000000: 1024 bytes - 1024/30112
verify offset 0x400/0x75A0[0x400/0x400]
( 6) at 00000400: 1024 bytes - 2048/30112
verify offset 0x800/0x75A0[0x400/0x400]
( 10) at 00000800: 1024 bytes - 3072/30112
verify offset 0xC00/0x75A0[0x400/0x400]
( 13) at 00000C00: 1024 bytes - 4096/30112
verify offset 0x1000/0x75A0[0x400/0x400]
( 17) at 00001000: 1024 bytes - 5120/30112
verify offset 0x1400/0x75A0[0x400/0x400]
( 20) at 00001400: 1024 bytes - 6144/30112
verify offset 0x1800/0x75A0[0x400/0x400]
( 23) at 00001800: 1024 bytes - 7168/30112
verify offset 0x1C00/0x75A0[0x400/0x400]
( 27) at 00001C00: 1024 bytes - 8192/30112
verify offset 0x2000/0x75A0[0x400/0x400]
( 30) at 00002000: 1024 bytes - 9216/30112
verify offset 0x2400/0x75A0[0x400/0x400]
( 34) at 00002400: 1024 bytes - 10240/30112
verify offset 0x2800/0x75A0[0x400/0x400]
( 37) at 00002800: 1024 bytes - 11264/30112
verify offset 0x2C00/0x75A0[0x400/0x400]
( 40) at 00002C00: 1024 bytes - 12288/30112
verify offset 0x3000/0x75A0[0x400/0x400]
( 44) at 00003000: 1024 bytes - 13312/30112
verify offset 0x3400/0x75A0[0x400/0x400]
( 47) at 00003400: 1024 bytes - 14336/30112
verify offset 0x3800/0x75A0[0x400/0x400]
( 51) at 00003800: 1024 bytes - 15360/30112
verify offset 0x3C00/0x75A0[0x400/0x400]
( 54) at 00003C00: 1024 bytes - 16384/30112
verify offset 0x4000/0x75A0[0x400/0x400]
( 57) at 00004000: 1024 bytes - 17408/30112
verify offset 0x4400/0x75A0[0x400/0x400]
( 61) at 00004400: 1024 bytes - 18432/30112
verify offset 0x4800/0x75A0[0x400/0x400]
( 64) at 00004800: 1024 bytes - 19456/30112
verify offset 0x4C00/0x75A0[0x400/0x400]
( 68) at 00004C00: 1024 bytes - 20480/30112
verify offset 0x5000/0x75A0[0x400/0x400]
( 71) at 00005000: 1024 bytes - 21504/30112
verify offset 0x5400/0x75A0[0x400/0x400]
( 74) at 00005400: 1024 bytes - 22528/30112
verify offset 0x5800/0x75A0[0x400/0x400]
( 78) at 00005800: 1024 bytes - 23552/30112
verify offset 0x5C00/0x75A0[0x400/0x400]
( 81) at 00005C00: 1024 bytes - 24576/30112
verify offset 0x6000/0x75A0[0x400/0x400]
( 85) at 00006000: 1024 bytes - 25600/30112
verify offset 0x6400/0x75A0[0x400/0x400]
( 88) at 00006400: 1024 bytes - 26624/30112
verify offset 0x6800/0x75A0[0x400/0x400]
( 91) at 00006800: 1024 bytes - 27648/30112
verify offset 0x6C00/0x75A0[0x400/0x400]
( 95) at 00006C00: 1024 bytes - 28672/30112
verify offset 0x7000/0x75A0[0x400/0x400]
( 98) at 00007000: 1024 bytes - 29696/30112
verify offset 0x7400/0x75A0[0x1A0/0x400]
(100) at 00007400: 1024 bytes - 30720/30112
Wrote page 0-29 with 30112 bytes in 3631msec
Closing flash driver NSS_30k_8k_IAP.cfx
(100) Finished writing Flash successfully.
Flash Write Done
Loaded 0x75A0 bytes in 4375ms (about 6kB/s)
Reset target (system)
Starting execution using system reset

0 Kudos

7,469 Views
patrickgeens
NXP Apps Support
NXP Apps Support

Hi stevekuh,

 

I assume MCUXpresso 10.2.1 is used and the NHS31xx plugin is installed:

patrickgeens_2-1674142206806.png

 

To check if your IDE is working correctly I propose the following test:

- create a new empty folder on disk

- start MCUXpresso 10.2.1 (or select File -> Switch Workspace if already running) and select the empty directory created above to become the new workspace. A blank workspace is shown.

- in the Quickstart panel: select Import project(s) from filesystem and select the SDK release zip file as downloaded from the NXP website:

patrickgeens_1-1674141779272.png

 

Press Next>, press Finish: all projects are unzipped in the workspace directory and added in the IDE workspace panel

patrickgeens_0-1674141703071.png

 

After the IDE has finished importing the projects, check the sensormonitor project MCU setting to see if it shows the NHS3100 setting

patrickgeens_3-1674142456529.png

 

Build (and debug) the project to see if everything is working as expected. There should not be an error (actually more a warning) that a generic M0+ is selected.

 

Note: due to the code size the "release" build configuration is preferred, otherwise there is little flash left for storage. You will probably need to manually set the "release" build config on the "lib_board_dpahu" and "lib_chip_nss" projects, as the IDE not always propagates the setting automatically to the referenced projects. (if not done, there is a linker error stating "lib_chip_nss" and "lib_board_dpahu" is missing)

 

Kind regards,

Patrick

 

 

0 Kudos

7,440 Views
stevekuh
Contributor III

- upon following the instructions to start a new folder and brining the demo projects fresh, they all compile and debug correctly without errors.

- on Telnet, my setting doesn't work as shown:

Capture Tera Term Setting.JPGCapture Tera Term Err.JPGMCUXpresso Console.JPG

0 Kudos

7,400 Views
stevekuh
Contributor III

- I am writing to follow up. Could you send instructions on how to use the Telnet console? It seems that my connection is being refused as shown in the post above.

- I would also like to add an external EEPROM to be able to store the data for months at a time. Could you point me in the right direction to modify the EEPROM storage/recall data section of the code?

 

 

0 Kudos