Hi there

I have also run in to the same problem, you can sometimes
sneak around this issue by creating a ultra tiny downloader
application (almost only autoupdate enabled) and do a two-step
download by sending the 'downloader' before the main app, Thus
giving you the maximum ram available for the update process.

(Problem being that the current app and the new download image
must co-exist in ram for the update to occur).

This failing, I have also used a memory card, ie: FTP your
app to the card and then have your code do an update from
the .S19 file on the card if it exists during reboot.

Personally I would store the compressed .exo file in an an
external memory device (ie: serial flash, eeprom, reserved
flash segment, etc..) and decompress/program it from there.

Regards
Steve

--- In netburner_group@yahoogroups.com, "Shahabuddin Inamdar" <shahab47@...>
wrote:
>
> Hello there.
>
> I am using MOD5234 along with xilinx FPGA XC3S1600E-400FCC.
>
> Here are the pinouts for netburner connector J2 which I am using to program
the FPGA using NB.
>
> Pin-38 : Program
> pin-22 : init
> Pin-33 : done
> Pin-32 : Din
> Pin-29 : cclk
>
> I am sucesfully able to program the FPGA by including the .exo filie generated
by FPGA Tool, as a .h file in the NB code.
>
> But the thing is:
>
> When .exo fpga file is included in the nb code, it becomes very huge and NB
AUTOUPDATE utility cant see the NB. So I had to download the code using TTY
terminal.
>
> Is there any way, I can still download the nb code using autoupdate utility
inspite of the NB code being very huge? (the .exo file is about 3MB in size)
>
> Any help in this aspect will be appreciated.
> Thanks.
>