LPC55S16-EVK and using BLHOST execute

[jpholme]

I'm trying to execute a function located at 0x3000 from BLHOST in my image downloaded to an LPC55S16-EVK mcu. I can easily get the mcu into ISP-mode and communicate with it from BLHOST. When I try to execute the function below, it will just execute from reset - as if a fault of some sort eventually resets the device:

BLHOST -p COM2 -- execute 0x3000 0x00 0x00021000

Getting property 0x11 is says that it is in SECURE mode. I suppose the bootloader is in the TrustZone secure context?

Also, if I change the argument (0x00 with underline) to nonzero, I get this the error 10006 as a reply. Why should it do this?

[Pavel_Hernandez]

Hello, could you elaborate further about what do you want to do? do you have security on your board? could you let me know more about your application? 

Best regards,
Pavel

[jpholme]

Hi Pavel,

I suppose it makes more sense to break it up:

1 - Execute command

No matter what firmware is inside the LPC55S16 on the EVK, the bootloader seems to reject the argument (underlined below) being different from 0:

BLHOST -p COM2 -- execute 0x3000 0x00 0x00021000

I suppose that this is not intended. Same behaviour on both LPC55S16-EVK's I have and same on the LPC5516 boards of our own design. The error code is 10006.

2 -SECURE State

Running following command, I'm told that the boards are in SECURE state:

BLHOST -p COM2 -- get-property 0x11

What does that mean? I can't find anywhere this is described.

3 - Execute call turns into reset

The list of questions came from the fact that the execute command from BLHOST doesn't seem to work for me. The device just resets even if I have functions mapped to say address 0x3000 (I can check in the disassembly) when running following command:

BLHOST -p COM2 -- execute 0x3000 0x00 0x00021000

Could that be because of question #2 that the MCU is in SECURE state? I tried instead to jump to 0x10003000, but same result.

[Pavel_Hernandez]

Hello, I afraid it was not clear if you are using security, if not maybe this is an unexpected behavior. I found this argument on the documentation, however if the device is secure the command that you can use only are the next.

Did you activate a security feature? 

Best regards,
Pavel

[Pavel_Hernandez]

Hello, my name is Pavel, and I will be supporting our case, let me get into your case, when I have more information, I will contact you.

Best regards,
Pavel