New SDK is online, with RLP and tons of other features

Thanks Gus :smiley:

I am going to implement a RLP driver for a DOG 132x32 LCD display. It use an ā€œSPI likeā€ interface that Iā€™m going to bit-bang instead of using up an SPI port.

Iā€™ll probably wait for the SDK release since I have many other things to do.

Regards,
Synapsys

@ Gus, Iā€™m trying to follow the tutorial by ā€œDelegateVoidā€ that you mention in the first post of this thread ([url]http://www.itcrowd.be/getting-started-with-ghi-rlp[/url] ). I get to the point of editing the rlp.h file ā€“ what is RLP_ADDRESS and RLP_SIZE for Panda? Itā€™s populated and commented out for ChipworkX EMX but not for others that are now rlp-enabled. How would I go about getting this information short of asking the forum/you?

Iā€™m assuming others will need this info for domino, mini, rhino.

You should use the example we provide. There is 2 examples specifically made fro USBizi. At the end of the docs, there is a link to a zip file with the examples.

Not seeing it.

Iā€™m looking at http://www.ghielectronics.com/downloads/NETMF/Library%20Documentation/html/f608e398-6573-8adc-5d59-b904dfa3fcee.htm

At the bottom of the docs there is indeed a link to a zip file (itā€™s where I go the rlp.h file I mentioned). rlp.h from the zip file contains the code:

// !!! The user must set these settings according to used platform !!!
// ChipworkX
//#define RLP_ADDRESS 0xA0000000
//#define RLP_SIZE 0x001FB3FC

// EMX
//#define RLP_ADDRESS 0xA0F00000
//#define RLP_SIZE 0x000FFFFC
// !!!

It (the zip) also has lots of directory and other clues centered around ChipworkX and EMX.

To my understanding, neither of these is USBiziā€¦

Where should I be looking?

Looking forward to thisā€¦

Sounds great

for reference, the zip file which includes panda is at [url]http://www.ghielectronics.com/beta_01979/Library%20Documentation/RLP_User.zip[/url] . Look in rlp.h for USBizi-related address/size.

get to it from the beta documentation >> native namespace >> RLP class >> examples at the bottom of the page.

ā€¦so Iā€™ve worked my way through the example/tuturial. Lots of gotchaā€™s. When I run now I get a OOM message when the ELF file tries to load. The file is 35kB by itself, for just the ā€œadd two numbersā€ C example code.

a) is the file size appropriate? should I do something else to make it smaller?

b) has anybody got RLP to work on Panda?

hereā€™s the screen dump:

GC: 1msec 18696 bytes used, 35436 bytes available
Type 0F (STRING ): 96 bytes
Type 11 (CLASS ): 720 bytes
Type 12 (VALUETYPE ): 72 bytes
Type 13 (SZARRAY ): 372 bytes
Type 15 (FREEBLOCK ): 35436 bytes
Type 17 (ASSEMBLY ): 8928 bytes
Type 18 (WEAKCLASS ): 48 bytes
Type 19 (REFLECTION ): 48 bytes
Type 1B (DELEGATE_HEAD ): 180 bytes
Type 1D (OBJECT_TO_EVENT ): 48 bytes
Type 1E (BINARY_BLOB_HEAD ): 5700 bytes
Type 1F (THREAD ): 384 bytes
Type 20 (SUBTHREAD ): 48 bytes
Type 21 (STACK_FRAME ): 1056 bytes
Type 27 (FINALIZER_HEAD ): 48 bytes
Type 31 (IO_PORT ): 72 bytes
Type 34 (APPDOMAIN_HEAD ): 72 bytes
Type 36 (APPDOMAIN_ASSEMBLY ): 804 bytes
Failed allocation for 2843 blocks, 34116 bytes

#### Exception System.OutOfMemoryException - CLR_E_OUT_OF_MEMORY (1) ####
#### Message: 
#### System.Resources.ResourceManager::GetObjectInternal [IP: 0000] ####
#### System.Resources.ResourceManager::GetObjectFromId [IP: 0009] ####
#### Microsoft.SPOT.ResourceUtility::GetObject [IP: 0000] ####
#### RLP4.Resources::GetBytes [IP: 000b] ####
#### RLP4.Program::Main [IP: 001e] ####

A first chance exception of type ā€˜System.OutOfMemoryExceptionā€™ occurred in mscorlib.dll
An unhandled exception of type ā€˜System.OutOfMemoryExceptionā€™ occurred in mscorlib.dll

Please compile your project with the linker script and make file from the example provided by us. You have something off and this is why your elf file is large.

Before you do anything, compile the example we provide AS IS and try it please.

Is it still possible to implement different bootloader region size,
previously discussed some time ago?
Thank you

[quote]
Is it still possible to implement different bootloader region size,
previously discussed some time ago?
Thank you[/quote]

No you canā€™t but I do not remember why you needed that. We are talking managed boot loader, right?

Yes,my bootloader code has 25K and application is about to reach maximum of 96KB.
23KB potentially moved from boot to app is a gold mine for me.

Using 96K already? I like that! Must be some cool application. Is it all code or you have resources?

No resources,only for code.
Iā€™m using almost all features of your library

Would you be able to tell us how much free RAM and Flash are available to us with this new beta on the Panda?

Same as before :slight_smile: Is this great or what? We add more features but not use more memory!

Sizes are showing here http://www.tinyclr.com/compare/

That is great Gus. How the heck you pull that off?

I was on vacation so i just see this new promising SDK.

This will be all I need to use Panda as I need.

Any news on when is it going to be released ?

Thanks for coming through with the goods.
I had asked about access to internal flash, and now we have the InternalFlashStorage method - nice work.

How can I drive a SPI interface from native code?

Why do you need that since SPI is already supported?

But you can make an RLP to do that. Read about RLP in documentation and see examples