[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [uClinux-dev] Re: [microblaze-uclinux] uclinux build fails because
yeah!!..I commented out that line and the problem was fixed!!..thanks a bunch...
in any case..can you please elaborate on that clarification if time permits??..i will need to eventually use netflash to update my image..in that case i will be including this checksum too for whatever its worth as a minimal integrity check!!...
I still did not understand what CVS has got to do with file permissions of binaries.Does it then not apply to all binaries being used?
I am still compiling only a local copy right?..maybe i am getting it wrong completely..any clarifications are welcome!!...
I have one more doubt...though I have not explicitly placed any breakpoints in my kernel image..when I download it on to SDRAM using xmd and then try to execute it using the con "start addr" command....the execution halts after giving this message on the xmd console
XMD% USERSTOP AT
..some address in SDRAM: opcode...and the instruction
when I do a bpl(breakpoint listing),nothing shows up
whenever this happens,I do a 'rrd' in the XMD console
and find that register r16(of microblaze) holds the same address as the PC and according to the microblaze software reference manual..this happens whenever a hardware break occurs(register r16 gets the address of the instruction that was to be executed when the break occured...)
i tried searching for this particular information in the xilinx help website but so far i have not been able to find
any useful information(related to this particular problem)
i want to know why this "USERSTOP at" event occurs..?...
i have not placed any breakpoints in the image on my own...
Thanks for any information in this regard
>Jivin anand_12 lays it down ...
>> Hi all
>> I recently uploaded the uClinux dist onto our local CVS
>> .Since we are using only the linux-2.4.x kernel for our project..i did not upload the 2.0 and 2.6 kernels..
>> the current CVS repository can be accessed from
>> then follow MicroBlaze->sw->src
>> 'src' is my parent directory for the uClinux dist...
>> but when i try to build this cksum reports error as shown
>> below ...so the contents of my images directory is now :
>> -rwxr-xr-x 1 root root 0 Jul 24 18:55 image.bin
>> -rwxr-xr-x 1 root root 9504358 Jul 24 18:55 image.elf
>> -rw-r--r-- 1 root root 668508 Jul 24 19:17 imagez.bin
>> -rwxr-xr-x 1 root root 1093492 Jul 24 19:17 linux.bin
>> -rw-r--r-- 1 root root 383804 Jul 24 19:17 linuxz.bin
>> -rw-r--r-- 1 root root 284672 Jul 24 19:17 romfs.img
>> as shown..image.bin size is 0...can anyone tell me
>> why this is happening?..the local distribution builds successfully..but the CVS build does not happen successfully..it does create the other files image.elf etc..but image.bin is not created...rather created but..its size is zero...
>cksum is a binary, perhaps you did not set the binary flag for that
> cvs admin -kb cksum
>alternatively, your probably don't even want cksum, nor want to use it,
>so delete it from your makefile and be happy :-) It's only useful if
>you use netflash to remotely update your images on the target, and you
>want the slight protection of a simple checksum,
>David McCullough, firstname.lastname@example.org Ph:+61 7 34352815 http://www.SnapGear.com
>Custom Embedded Solutions + Security Fx:+61 7 38913630 http://www.uCdot.org
>uClinux-dev mailing list
>This message was resent by email@example.com
Trouble with windows? Re boot....
Trouble with Linux? Be root....
microblaze-uclinux mailing list
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/