04-10-2012 10:09 PM
I have some question pls answere me.
1. In "ml507_bsb_ppc440_vxworks_proj_creation.pdf" and in "xapp1114.pdf" wrote that we must editing bsp ( config.h and make ) in any tetx editor . When SDK generate these files ..... Why we must change it manually ?
2. In these file changes describe very short pls explain for me these varibale ( it equal to wicth parameter from XPS outputs )
LOCAL_MEM_SIZE = ? it is capacity of DDR2 ?
ROM_BASE_ADRS=? it is base address of Linear Flash ( BPI Flash ) ?
ROM_SIZE=? it is size of final elf file (vxworks.elf) ? in those pdf it is not exactly equal to elf file size !!!
ROM_TEXT_ADRS=? in "xapp1114.pdf" we read :
Note: The value of ROM_TEXT_ADRS is where the bootrom image is programmed within the flash. This
address is chosen so that the end of this image will be exactly at the end of the processor address space,
where the boot vector is located (0xFFFFFFFC).
but end of image when we use ((0xFFFFFFFF - ROM_SIZE) + 1) we have 0xFFF000000 with ROM_SIZE=0x00100000
equal to 0xFFFFFFFF not equal to 0xFFFFFFFC !!!
ROM_WARM_ADRS=? it is always ROM_TEXT_ADRS+4 ?
BOOT_TLB_I=? what is different bitween 0xFFFF with 0xFFFE ?
3. in "xapp1114.pdf" where is the address of bram ?
in this pdf we must program linear flash from ROM_TEXT_ADRS (0xFFF00000-0xFE000000(base address of linear Flash )) = 0x01F00000 and load bit file from jtag or platform flash but download.bit contain bootloop.elf file and bootloop program and load from 0xFFFFFFFC ( Boot Sector ) so when bram move to another address ( to have free address in this area for linear flash ) jtag or platform flash can not run and program so system does not work !!!
What we should to do ?
4. in "ml507_bsb_ppc440_vxworks_proj_creation.pdf" I must run a ".sh" file in xbash.exe ( it is working under XPS v13 and I force to use XPS 12 Xbash but I'm working on XPS 13 that it does not have Xbash it is have a cmd.exe) to run genace.tcl to merge download.bit file ( contain bootloop.elf ) and vxworks.elf to generate ".ace" file . ( I was do it and it works with demo image of vxworks 6.3 ) what is happen ? bootloop.elf+vxworks.elf !!!
in previos way , boot address was very critical but in this way boot address does not important ?
please answere and explain any of above question that you know for me and other person have same questions.