RE: [microblaze-uclinux] PetaLinux and ML505, revisited

["Theidel Gerd" <gerd.theidel@xxxxxx>]

Hi Justin,

 

have you done the changes, I descibed in the Thread "PetaLinux on ML505"?

Inserting

 

#define CFG_FLASH_PROTECTION

 

in the file u-boot\include\configs\petalogix-microblaze-auto.h

solved the problem for me.

 

Regards,

Gerd

 

---

From: owner-microblaze-uclinux@xxxxxxxxxxxxxx [mailto:owner-microblaze-uclinux@xxxxxxxxxxxxxx] On Behalf Of jlmoon@xxxxxxxxxxxxxxxxxxx
Sent: Donnerstag, 2. August 2007 16:36
To: microblaze-uclinux@xxxxxxxxxxxxxx
Subject: Re: [microblaze-uclinux] PetaLinux and ML505, revisited

This didn't seem to change anything. 
 I tried setting the environment variable 'unlock' to yes or no, to see 
what that would do.  Set at yes, the ub.config.img script runs the same as 
before.  Set to no, the script says "## Executing script at 50000000", and 
nothing else. 

Any other ideas? 
 I'm stumped. 

Thanks, 

Justin 




Hi,

> Flash erase error at address XXXXXXXX
> 
Block Erase Error,
> Block locked.
>
> And it repeats that 
message for all blocks attempted.

you can try to turn on support for 
hardware flash protection. I think you 
have only software 
protection.
#define CFG_FLASH_PROTECTION /* hardware protection 
*/

Regards,
Michal Simek





> Hi 
all,
>
> I'm trying to revive efforts to get PetaLinux working on a 
Xilinx ML505
> board.  I've read all the posts from the last 3 months 
that are at all
> related, and have made some progress.  Things are 
still not working
> though.  My framework has been the PetaLinux 
Platform From Scratch
> tutorial found at
> 
http://developer.petalogix.com/wiki/BoardGuides/Custom/Tutorial. 
 I'm
> using petalinux-v0.2.0-rc3, ISE 9.1.03, and EDK 9.1.02 with 
all relevant
> updates.  I have made whatever tweaks and adjustments 
have been needed to
> get everything to compile and work to this point. 
 Some of those tweaks
> have been documented elsewhere, and others I 
made up on the fly.  If you
> have questions about what I've done, 
please ask, and I'll rack my brains
> to remember what I 
did.
>
> --As a side note, excellent work from the Petalogix group. 
 Thank you.
>
> In my current configuration, I can load the 
FPGA, and FS_Boot comes up
> looking for an image.  There is not an 
image in flash, so it waits for one
> to be sent.  I send the U-Boot 
image through kermit, and that works fine.
> The U-Boot prompt comes up, 
and I have access to all the commands it
> provides.  I can send the 
ub.config.img file just fine, but the problem
> I'm facing comes when I 
try to run that script.  Everything works until it
> tries to mess 
with the flash memory.  It says I have locked blocks in the
> flash. 
 The exact output is as follows:
>
> PetaLogix MicroBlaze-Auto 
Board Configuration
> 
-----------------------------------------------------------------------
> 
Network Configuration:
> MTD Configuration:
> Clobber DRAM 
Configuration:
> Bootloader Configuration:
> Kernel 
Configuration:
> Boot Configuration:
> Saving 
Configurations...
> Saving Environment to Flash...
> Un-Protected 1 
sectors
> Erasing Flash...
> Flash erase error at address 
4a040000
> Block Erase Error.
> Block locked.
> done
> 
Erased 1 sectors
> U-Boot>
>
>
> I have tried just 
about everything I can think of to test this flash
> memory from the 
U-Boot prompt.  I can use protect off and on, and flinfo
> shows me 
that protection turns on and off, but any time I try erase, it
> 
says:
>
> Flash erase error at address XXXXXXXX
> Block Erase 
Error,
> Block locked.
>
> And it repeats that message for all 
blocks attempted.
>
> I'd appreciate any suggestions on 
this.
>
> Thanks,
>
> Justin 
Moon