Alright, I tried the 2.4 kernel. Now
it freezes _before_ the klimit messages. I get "Verifying Checksum
... OK" and then another OK on the next line, and it hangs. I'd
really like to debug this but I have no idea how to start. Can anyone
help?
Thanks,
Justin
"Alberto Jiménez Hernández"
<albertojh@xxxxxxxxx> Sent by: owner-microblaze-uclinux@xxxxxxxxxxxxxx
08/16/2007 05:25 PM
Please respond to
microblaze-uclinux@xxxxxxxxxxxxxx
To
microblaze-uclinux@xxxxxxxxxxxxxx
cc
Subject
Re: [microblaze-uclinux]
PetaLinux and ML505, revisited
Hi all. I'm new at this but I had the same problem as Justin. Each time
I tried to start my system it used to freeze after it had displayed the
"New klimit: 0x502a7000"
message.
The solution I found (not very good) was to return to the 2.4 kernel (I
was previously using the 2.6 kernel), and now it works fine. I'm sure that
it has something to do with the 2.6 kernel's startup configuration. I based
my system ( k2.4) on the "Petalinux Platform From Scratch" document.
This information won't probably help you a lot, but I wanted to share my
limited experience.
Ok, I've checked my Ethernet core, and checked that I have a Gigabit card
in my PC. It turns out I had my ethernet jumpers on the board set
to SGMII, which is not what I was trying to use. So I changed my
jumpers, set my PC line speed to 100 Mb/s, and now my ethernet works.
On to the next problem. I have now transferred images to the board
and written them to flash. When I reboot the board, it looks like
it's going to boot, but hangs right after "New klimit: 0x502a7000",
and just before I should get a "Linux version 2.6.XX...." message.
I'm stumped again. I've googled as many related keywords as
I can think of, and can't find anything. Any ideas?
Thanks so much, Gerd and Michal. I wouldn't be this far if not for
your help.
RE: [microblaze-uclinux]
PetaLinux and ML505, revisited
Hi,
I have done the first tests with OPB-EMAC and with OPB-EMACLITE; both
worked
with U-Boot but I did not get a very stable connection under uClinux
Kernel 2.4.
Than I wrote a proprietary core, because I want to to send additional
highspeed data
from the FPGA bypassing the processor. As first test I connected the
TEMAC to an
FS-Link of the microblaze and wrote some small drivers for U-Boot and
Linux. This connection
is very stable, but the performance is not so high, because I do not use
DMA.
Justin:
I did not discover the problems you have described, but one idea:
Do you have a gigabit ethernet-card in your PC? Than you have to
set it to 100 Mbit before connecting it to the ML505. I suggest to
use Wireshark (www.wireshark.org)
to see if the ML505 sends some
packets...
What ethernet core are you using? EMAC, EMACLITE, TEMAC or proprietary.
If you are using emaclite you can try my emaclite driver for U-BOOT. It
is in microblaze mainline at denx.de.
(drivers/net/xilinx_emaclite.c)
Emaclite needs my edk repository file for configuring that you can find
at www.monstr.eu.
If you are using EMAC I can send you development version of new driver.
TEMAC isn't porting to U-BOOT yet.
And proprietary ethernet core is only your fight.
I recommend you to use tcpdump or ethereal for scanning your ethernet
port on HOST. You can see all packets and analyze where is the problem.
Regards,
Michal Simek
> Gerd,
>
> I thought I had done the changes in your thread. But it seems
I
> missed that one line. This did fix my problem with locked flash.
Thank you.
>
> Now I don't think my Ethernet is working. The status lights
on the
> board blink when there is activity from the PC side, but no blinking
> when I try to ping or tftp from the board. I am using a crossover
> cable connected directly from the ML505 board to the CentOS 4 PC.
The
> PC is configured for a static IP address of 192.168.0.1,
and is also
running a DHCP server.
> If I try to TFTP, the serverip and ipaddr variables are not set, and
> when I set them, it locks up. I have tried 'setenv ipaddr
> 192.168.0.2'
and also 'dhcp'. The latter locks up the U-Boot and
> nothing happens. Have you seen this problem before?
>
> The next step I'm trying is to get the u-boot-s.bin file tftp'ed to
> the system. The aforementioned tutorial says to do this with
>
> U-Boot> tftp $(clobstart) u-boot-s.bin
>
> That's when I find out that the serverip and ipaddr variables
are not
> set. And when I set them to sane values, tftp locks up. I've
tried
> loading the u-boot-s.bin file over kermit, but that just resets the
> processor. I assumed I could send it the same way I sent the
> ub.config.img file, with
>
> U-Boot> loadb $(clobstart)
> Ctrl\c
> C-Kermit> send /bin /tftpboot/u-boot-s.bin connect
>
> But that's when I get the FS-Boot prompt again, saying Waiting for
> SREC image.
>
> Any ideas from here?
>
> Thanks,
>
> Justin
>
>
> "Theidel Gerd" <gerd.theidel@xxxxxx>
> Sent by: owner-microblaze-uclinux@xxxxxxxxxxxxxx
> 08/03/2007 03:04 AM
> Please respond to
> microblaze-uclinux@xxxxxxxxxxxxxx
>
>
> To
> <microblaze-uclinux@xxxxxxxxxxxxxx>
> cc
>
> Subject
> RE: [microblaze-uclinux] PetaLinux and ML505, revisited
>
>
> 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
>> 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