LabVIEW Embedded

cancel
Showing results for 
Search instead for 
Did you mean: 

Using peek/poke memory VI's using ARM Embedded module - how to work?!

Hi David,

 

Thank you for your reply.

 

You said "After copying over the new peek/poke xml file (Memory Access) I found that the peek/poke option did not work. I had never tried it on my computer with the previous xml file; it had been performed on a colleagues computer previous. After copying back the old xml file to see if it worked I still get the same error."

 

This leads me to think that the problem is not with the peek/poke VIs itself. I have not heard any issues with the VIs after they have been replaced with the new XML file. This partially because you get the same error irrespective of which XML file it is.

 

You said "I went back the the previous computer where the peek/poke vi's created no trouble (although they didn't generate any output) only to find that they do not work as before. Replacing with the new xml file did not work also."

 

Does this mean that the peek/poke VIs don't work anymore irrespective of where you are using it at? Have you tried reinstalled LabVIEW for ARM?

 

You said "We think we may have the addressing wrong. We are using the internal memory to store our information and may, as a result be overwritting a part of the OS. We are not sure and have, due to other pressures, pushed this down a notch in our priority list; but we will need it in the future."

 

I would agree with that conclusion. To confirm this, if you could send me your VI itself. The reason I ask for it vs. using the screen shot is that I would like to use the exact same/project/build spec/VI for testing. I want to eliminate all variables in terms of different settings while configuring the target.

 

Please post back with your VI so that we can test it here.

Warm regards,
Karunya R
National Instruments
Applications Engineer
0 Kudos
Message 11 of 21
(5,019 Views)

 

Hi David,

 

When you get a chance, please try to answer my questions. No pressure if you have other things that came up!

 

Just want to make sure that you are successful with your application.

 

Warm regards,
Karunya R
National Instruments
Applications Engineer
0 Kudos
Message 12 of 21
(4,990 Views)

David,

 

          I will be taking over this service request from Karunya. If you would give me an update on your progress, I would appreciate it. Please don't hesitate to ask any questions if you have any. Thanks!!

 

Grant H.

AE-NIC

0 Kudos
Message 13 of 21
(4,963 Views)

ok ok ok...here is the main vi and the project file. I hope it helps. Welcome aboard Grant!

 

we haven't spent too much time on this since the initial post as we have re-directed our resources onto some other major developments in LVE.

 

I hope that helps.

Download All
0 Kudos
Message 14 of 21
(4,959 Views)

David,

 

        This error comes up when accessing a memory address that is restricted or incorrect. If you look at the memory map (pg 17 of 52) for the MCB2300 (LPC2378), I don't see the address 7000 on the list. You might need to add some more characters to your address to get this to work. Also, the project file that you uploaded wasn't everything. You also need some other configuration files that the project creates. It is easier just to zip up all of the dependent files together. Let me know if changing the address helps. 

0 Kudos
Message 15 of 21
(4,935 Views)

Hi David,

 

I took at a look at your VI, and while you have provided a valid address (albeit currently occupied by other data), using the poke VI on flash is not a valid operation.  I would suggest using RAM if you want to modify memory during runtime, and specify any data in your VIs that you would like to be programmed into flash at the initial download.  

 

If you must write to flash at runtime, then please refer to another post I made on this issue:

http://forums.ni.com/ni/board/message?board.id=420&thread.id=1121&page=2

 

btw, if you want to get an idea of what memory is not being used by your program, you can bring up the map file by opening microvision (by right clicking on target) after building and double clicking on the target (LabVIEW) in the project workspace on the left.

 

Thanks

Message Edited by Gmg on 05-06-2009 11:01 AM
0 Kudos
Message 16 of 21
(4,917 Views)

I realized it might be a bit confusing in the other thread I linked, as I'm referring to external flash on a different chip...

 

So what I would recommend is to use C nodes and look at the microvision project C:\Keil\ARM\Flash\LPC_IAP2_512.  This is the source code that is used when microvision first downloads the project and you should be able to use this as a good example to modify flash.

0 Kudos
Message 17 of 21
(4,906 Views)

Hi all,

 

Is there any update about this issure?

 

We have the same problem these days. And do not know how to solve...

0 Kudos
Message 18 of 21
(4,486 Views)

This was resolved by concluding that peek/poke memory VI's were not meant to write/read flash.  They only support write/read to RAM.

 

If you are trying to write to flash, I suggest you refer to Gmg's posts above.

0 Kudos
Message 19 of 21
(4,476 Views)

HI All,

 

This is a different but similar topic in regards to memory on the ARM.  Can I use the peek/poke to see memory usage to determine if memory leaks occur in my application?   Is memory leak a concern for the ARM embedded environment.

 

 

Rupert F.

0 Kudos
Message 20 of 21
(3,816 Views)