Increase the RAM size

I don't see config.h in the post. Only image_cfg.h file is present.

Hi,

In img_cfg.h file change IMAGE_WINCE_CODE_SIZE to 8200000 if your current NK size is 72 MB.

Add config.bib also to make it clear.

Hi Seetharam, thanks for your note on making the change in image_cfg.h file to increase the size for NK.bin....

Here, I attached the missed config.bib for your reference to modify for the same issue....Please share once got changed.

Regards,

Karthick2476.config.zip

Hi,

There is no changes in config.bib as they are importing image_cfg.h file and using those macros. 

Did you try modifying size value that I mentioned?

I think that is enough to build the debug image.

Regards,

Seetharam

Thanks Seetharam.! I could able to modify the image_cfg.h file (for 130MB size of NK.bin) and build in debug mode. Then successfully able to generate the NK.bin and other output files. But the generated output file size is about 133MB....I don't know the exact reason how it's got build without any errors.!!!

Anyway, I just flashed it to the EVM through ethernet connectivity and file download is happened until it was showing 4sec left and got out of it without completing the download. So, I thought it would be the size error again and increased the size to 135MB and continuing the test. Am I right on this?

Also, I wondered is n't possible to write to flash and able to run OS image on each power on reset cycles...Because, in release mode I setup the IMGNAND variable by disabling the KITL and kernel debugger options and flashed the NK.bin through ethernet connectivity. Download is done, and OS image was running perfect, but once power on reset is done, the OS image disappears and never ran again...!! Am I making anything wrong here? Then, what's right option to flash the NK.bin into NAND flash memory permanently and run each time on power cycle.

I appreciate your thoughts on this.

Thank you,
Karthick

Ok, using Ethernet only you can download this big size OS image.

And for second question, are you doing flash update after the ethernet download is done? Is it getting written to the NAND?

It would ask for flash update and that time you need to give yes. Check this option after the download is done. Else it is getting download directly to RAM and from there its booting. Or else you have not selected the Boot device in Bootloader menu.

Regards,
Seetharam

Thanks for that.
Even if I increase the size of the IMAGE_WINCE_CODE_SIZE to 0x8700000 (ie 135MB), I am getting the same error that when 4sec left for OS image to flash, it's failed....Is that true that more than 130MB of NK.bin size can not be flashed? If it's true then, I have to reduce the code size some how by disabling some of the drivers?? or is there any other way to do it without disabling any of the drivers?

I did n't see the flash update option yet (where can I findout)? Even in release mode I didn't see such option popped up when download is complete..

Yes, I did configured the boot option to [3] NK from NAND and now I am able to boot the image out of the box!!

Regards,
Karthick

You can correct it, in my case it was 130MB around so I referred that value. You can reduce and check. It may be losing the connection with the board or something, or it may be due to the 130+ MB NK. Please check this by reducing the NK size.

So it will directly go into NAND, when the download is complete. In my case I had to update the flash with separate command. So now you are able to boot from NAND.

Regards,
Seetharam

Okay. Thank you for the clarifications..
Finally, is XLDR, EBOOT sections vary if we operate in Debug or Release mode by enabling or disabling the Kernel Debugger and KITL options. Becuase I don't want to change the XLDR and EBOOT for each time when I change the options that I mentioned.

Regards,
Karthick

You can use the same eboot and xldr to boot release mode OS images.

It sounds like I should change the XLDR and EBOOT for debug mode then.

Thank you,

Karthick

Hi, In debug mode do I need to flash the EBOOTND.bin into NAND flash...Earlier it was flashed with release mode omap35x-raw.bin......and there was no XLDRND.bin is present in debug mode....?

Regards,
Karthick

The previously flashed binaries should be present in NAND.

Regards,

Seetharam

Thank you. Actually in Release mode, In Download status is shown as green that indicated NK.bin Download is complete and Transport is green that indicated KITL connection established over ethernet successfully and on Debugger part some of the .dll files had been loaded and progressed so on......

But Now, I am working in Debug mode, In Download status is shown as green that indicated NK.bin download is complet...but on Transport is shown as Last communication XX.XX timing..And on Debugger status shown as nothing than half green and yellow color.

Do I need to erase the complete NAND flash (which was stored with NK.bin generated in Release mode earlier to boot)....and download the NK.bin image in debug mode to establish successfuly debugging capability. I am struggling to debug the OS. Please note that NK.bin image size is now 131MB and successfully able to download.

Appreciate your thoughts.

Regards,
Karthick

Hi,

So you are able to download the image. You didn't mention if you booted the image. 

What happens when you boot the image, whether its booting completely with debug prints ? 

Let know these things.

Regards.
Seetharam

Hi Seetharam, thanks for joining again.

I did the changes to increase the memory size to 130MB to hold the NK.bin image in the image_cfg.h file.  And removed some of the software components to restrict the image size also.  Then, I am able to download the image into the target dive through ethernet....These are works fine.  But, after download is complete, then there is no progress afterwards, debugger mode is not activated at all showing half green and yellow color only in the right side bullet box.  

To confirm that this error because of the change made in image_cfg.h file, I build the os design in Release mode and enabled the kitl and kernel debugger options, to download the image and establish the kitl connection over transport and debugger support over Debugger options...But it failed as we seen in Debug mode.

Then, I revert back the changes made in image_cfg.h file (to 72MB) and did sysgen command to build system files and verified it works...!! mean I am able to establish the kitl and debugger support.

So finally the rootcause is image_cfg.h file that should be mapped properly.!!!  I am working out the changes should be done with careful way by referring AM/DM37x TRM. Also I had seen that if We change directly IMAGE_WINCE_CODE_SIZE to 130MB then it overlapped with IMAGE_WINCE_RAM_CA memory so it's not the way should make the change...The way the file looks is as below.

#define IMAGE_WINCE_CODE_CA 0x88000000 //
#define IMAGE_WINCE_CODE_SIZE 0x047FF000 // CODE 72 MB

#define IMAGE_WINCE_RAM_CA 0x8C7FE000 //
#define IMAGE_WINCE_RAM_SIZE 0x03801000 // RAM 56 MB

#define HEX_VALUE(a) 0x##a
#define IMAGE_WINCE_RAM_DISK_CA_HEX 80002000 //
#define IMAGE_WINCE_RAM_DISK_SIZE_HEX 27FE000 // RAMDISK 40 MB

#define IMAGE_WINCE_RAM_DISK_CA HEX_VALUE(IMAGE_WINCE_RAM_DISK_CA_HEX) //
#define IMAGE_WINCE_RAM_DISK_SIZE HEX_VALUE(IMAGE_WINCE_RAM_DISK_SIZE_HEX) // RAMDISK 48 MB

#define IMAGE_WINCE_DISPLAY_CA 0x82800000 //
#define IMAGE_WINCE_DISPLAY_SIZE 0x01000000 // Display 16 MB

#define IMAGE_WINCE_DISPLAY_720p_CA 0x83800000 //
#define IMAGE_WINCE_DISPLAY_720p_SIZE 0x01000000 // Display 16 MB - extra needed for 720p video playback; should be contiguous with IMAGE_WINCE_DISPLAY_CA

#define IMAGE_CMEM_CA 0x84800000 //CMEM ; this is always needed if DVSDK is enabled
#define IMAGE_CMEM_SIZE 0x01000000 //16 MB

#define IMAGE_DSP_720P_CA 0x85800000 //DSP (2)
#define IMAGE_DSP_720P_SIZE 0x01A00000 //26MB ; extra DSP region if using 720p codecs and SDRAM bank1

#define IMAGE_DSP_CA 0x87200000 //DSP 4456.config.zip
#define IMAGE_DSP_SIZE 0x00E00000 // 14MB ; this is always used if DVSDK is enabled

 If you think there would be an error in image_cfg.h file then please make a change in the attached file and post to me back.  I don't see any TI guy has supported this. Please help.

Thank you,

Karthick

Karthick,

Actually when you change the mode of building, you should give the SYSGEN command first upfront.

Next thing, you have to revert back the size to build in release mode. So this will make your image_cfg.h file as original.

I actually had the doubt in that file since I don't use this file for the image building. Mean to say these values are mentioned in config.bib in my case (Not TI BSP). I will study this and let you know the changes.

You didn't tell me what happens when you boot the board after downloading the debug image.

Regards,
Seetharam

Hi Seetharam, thank you for your support.

Successfully able to operate the device under debug mode.  It will be helpful to note the following;

1. In debug mode OS image size should not exceed 128MB.

2. No need to do changes in config.bib and image_cfg.h files to increase the size of the NK.bin....Just enable the 'Optimize run-time image size and speed' under build options.

3. I am able to customize the BSP and restrict the image size as desired.

Regards,

Karthick