From: Iain Scott <ISCOTT@altera.com> - 2003-04-08 14:34:53
I believe your problem isn't with the line you changed, but is with the
version of objcopy that you are using. Older versions of objcopy can produce
invalid hex files when the size of the binary exceeds the block size. You'll
then see the wrap-around error when you try and program the files into the
The RedHat version of objcopy that came with your board includes the fix for
this. More recent builds of the tools should also include the patch (I can't
tell you off the top of my head what the relevant version numbers are).
> -----Original Message-----
> From: imateos [mailto:imateos@...]
> Sent: Tuesday, April 08, 2003 3:08 PM
> To: armboot-users@...
> Subject: [ARMboot-users] ARMboot and EPXA10db
> Hi all,
> I'm trying to use ARMboot in the EPXA10 development board, and when I
> intend to substitute the line of CONFIG_BOOTARGS in the
> "/include/configs/config_epxa10db.h" file:
> #define CONFIG_BOOTARGS "root=/dev/nfs mem=16M
> #define CONFIG_BOOTARGS "root=/dev/mtdblock0 rw mem=128M
> rootfstype=jffs2 console=ttyUA0,57600"
> the compilation runs, but when I try to load the ".hex" file to the
> flash (with exc_flash_programmer) it generates the next warning:
> Warning: One or more of the blocks exceeded the 64K limit
> The resultant wrap-around may have caused corruption and
> should be checked
> by running the application again, but with the verify only option set
> After this, the board doesn't reset. Does anyone know what
> the problem is?
> Thanks in advance,
> This SF.net email is sponsored by: ValueWeb:
> Dedicated Hosting for just $79/mo with 500 GB of bandwidth!
> No other company gives more support or power for your dedicated server
> ARMboot-users mailing list