[U-Boot] PCIE Switch Support in u-boot-2015.01
Hi, I am using u-boot-2015.01 loader on MPC8641D based Board. I have following queries Related to PCIe bus 1. Does it provide support to pcie switch(PES64H16AG2) support? 2. Do I need any specific driver for this switch to make it up? After booting its not showing any link the logs are: U-Boot 2015.01 (Mar 23 2015 - 16:02:00) CPU: 8641D, Version: 3.0, (0x80900130) Core: e600 Core 0, Version: 2.2, (0x80040202) Clock Configuration: CPU:1200 MHz, MPX:400 MHz DDR:200 MHz (400 MT/s data rate), LBC:25 MHz L1:D-cache 32 KiB enabled I-cache 32 KiB enabled L2:512 KiB enabled Board: ESM From Vrinda Technologies Pvt Ltd (ref: BOSS) I2C: ready DRAM: 1 GiB Flash: 384 MiB SRIO1: enabled PCIe1: Root Complex, no link, regs @ 0xd0008000 PCIe1: Bus 00 - 00 In:serial Out: serial Err: serial Net: eTSEC1 [PRIME], eTSEC2, eTSEC3, eTSEC4 Hit any key to stop autoboot: 0 Any pointers/debugging tips to bring it up will be really helpful Thanks & Regards @$HI$H ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-boot on MPC8641D based board
Hi Sinan, Thanks for your Reply, I am using u-boot-2013.04 version. These are the following configuration which we are using: 1. SySclk-> 100Mhz 2. MPX Clk -> 400Mhz 3. Core Clk ->1200Mhz 4. LBC clk -> 25Mhz 5. LBC CS0-> Flash1(128Mbyte s29gl01gs) 6. LBC CS1-> Flash2(256Mbyte s70gl02gs) I have attached booting and crash log file. But when I type bdinfo in there its display only current flash size. I hope this information will help to understand the problem. On Thu, Mar 19, 2015 at 11:02 PM, Sinan Akman wrote: > > Hi Ashish > > > On 03/19/2015 08:12 AM, Ashish Khetan wrote: > >> Hi All, >> I have been facing a strange problem in my board which is MPC8641D based. >> In this board we have two nor spansion flashes connected to cs0 and cs1. U >> boot had detected both the flashes and when flinfo command is it shows >> both >> flash information but when we try to access another flash u-boot is >> crashing. >> >> Flash part no is s29gl01gs which is CFI complaint. >> >> Please provide some pointers where I should concentrate more to resolve >> this issue. As I have checked all the configuration in configuration file >> it seems to be fine. Any help will be really appreciated. >> > > As a rule of thumb, you need to provide u-boot version that > you are running. Ideally you should run the latest mainline > u-boot and reproduce the problem if you like to get effective > help from others. > > So please reproduce the issue with the latest mainline u-boot, > document the steps and provide some more info on your target hw. > > Regards > Sinan Akman > > > U-Boot 2013.04 (Feb 26 2015 - 13:50:34) CPU: 8641D, Version: 3.0, (0x80900130) Core: E600 Core 0, Version: 2.2, (0x80040202) Clock Configuration: CPU:1200 MHz, MPX:400 MHz DDR:200 MHz (400 MT/s data rate), LBC:25 MHz L1:D-cache 32 KB enabled I-cache 32 KB enabled L2:512 KB enabled Board: ESM From Vrinda Technologies Pvt Ltd (ref: BOSS) I2C: ready DRAM: 1 GiB SDRAM test phase 1: SDRAM test phase 2: SDRAM test passed. Flash: 384 MiB SRIO1: disabled PCIe1: disabled In:serial Out: serial Err: serial Net: eTSEC1 [PRIME], eTSEC2, eTSEC3, eTSEC4 Hit any key to stop autoboot: 10 0 ESMv0.2R=> ESMv0.2R=> ESMv0.2R=> ESMv0.2R=> flinfo Bank # 1: CFI conformant flash (16 x 16) Size: 128 MB in 1024 Sectors AMD Standard command set, Manufacturer ID: 0x01, Device ID: 0x227E2801 Erase timeout: 2048 ms, write timeout: 1 ms Buffer write timeout: 3 ms, buffer size: 512 bytes Sector Start Addresses: F800F802F804F806F808 F80AF80CF80EF810F812 F814F816F818F81AF81C F81EF820F822F824F826 F828F82AF82CF82EF830 F832F834F836F838F83A F83CF83EF840F842F844 F846F848F84AF84CF84E F850F852F854F856F858 F85AF85CF85EF860F862 F864F866F868F86AF86C F86EF870F872F874F876 F878F87AF87CF87EF880 F882F884F886F888F88A F88CF88EF890F892F894 F896F898F89AF89CF89E F8A0F8A2F8A4F8A6F8A8 F8AAF8ACF8AEF8B0F8B2 F8B4F8B6F8B8F8BAF8BC F8BEF8C0F8C2F8C4F8C6 F8C8F8CAF8CCF8CEF8D0 F8D2F8D4F8D6F8D8F8DA F8DCF8DEF8E0F8E2F8E4 F8E6F8E8F8EAF8ECF8EE F8F0F8F2F8F4F8F6F8F8 F8FAF8FCF8FEF900F902 F904F906F908F90AF90C F90EF910F912F914
[U-Boot] U-boot on MPC8641D based board
Hi All, I have been facing a strange problem in my board which is MPC8641D based. In this board we have two nor spansion flashes connected to cs0 and cs1. U boot had detected both the flashes and when flinfo command is it shows both flash information but when we try to access another flash u-boot is crashing. Flash part no is s29gl01gs which is CFI complaint. Please provide some pointers where I should concentrate more to resolve this issue. As I have checked all the configuration in configuration file it seems to be fine. Any help will be really appreciated. Ashish Khetan +91-8886013575 ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] VxWorks Booting using U-boot as Bootloader
Thanks Again, which u-boot version are you referring, because I am using 2013.04 version and in this there is no directory named board/BuR/KWB. can you please send the Boot Arguments which you used to boot the vxworks and which method are you using to boot vxworks? On Mon, Sep 8, 2014 at 10:16 PM, Hannes Petermaier wrote: > Hi Ashish, > > okay - i am using vxworks 6.9.3.3, and there is is a issue around the > interrupt vectors. In later versions 6.9.4 upwards windriver takes care > about this and sets up the interruptvectors. > U-Boot does sets them to some address within u-boot code, but vxWorks > expects that the interrupt vector are at the place where they are after > poweron-reset. > > In my case (using AM3352 from TI) i've set the interrupt vectors back to > original state (have a look to my KWB-Board, board/BuR/kwb/board.c). > > BTW: i am using a stripped image which i directly start with "go > ", but that shouldn't matter. > > best regards, > Hannes > > > > On 2014-09-09 03:56, Ashish Khetan wrote: > >> Hi Hannes >> Thanks for your reply. I am using VxWorks 6.7 and the image is not >> stripped. The loadaddress is also same within kernel configuration. I am >> using bootvx command to boot VxWorks. Do I need to update boot >> parameters? >> On Sep 8, 2014 4:11 PM, "Hannes Petermaier" < >> hannes.peterma...@br-automation.com> wrote: >> >> Hi Ashish, >>> >>> i had a problem booting vxworks in the past around interrupt vectors. >>> Which version of vxworks you are using ? do you use a stripped image ? >>> is the loadaddress the same within kernel configuration ? >>> >>> best regards, >>> hannes >>> >>> From: Ashish Khetan >>>> To: u-boot@lists.denx.de >>>> Date: 04.09.2014 14:13 >>>> Subject: [U-Boot] VxWorks Booting using U-boot as Bootloader >>>> Sent by: u-boot-boun...@lists.denx.de >>>> >>>> Hi, >>>> I was trying to boot vxworks using u-boot bootloader for learning >>>> >>> purpose >>> >>>> on MPC8640DHPCN board. Previously I successfully ported QNX os along >>>> >>> with >>> >>>> linux on same board using u-boot. while booting using bootvx command its >>>> not booting and stucking after showing the following message: >>>> >>>> tftp 0100 vxWorks >>>> Speed: 1000, full duplex >>>> Using eTSEC1 device >>>> TFTP from server 192.168.10.2; our IP address is 192.168.10.4 >>>> Filename 'vxWorks'. >>>> Load address: 0x100 >>>> Loading: >>>> >>> * # >>> >>>> # >>>> # >>>> 12.3 MiB/s >>>> done >>>> Bytes transferred = 2392432 (248170 hex) >>>> BOSSv2.0=> bootvx 0010 100 >>>> ## Ethernet MAC address not copied to NV RAM >>>> ## Using bootline (@ 0x4200): root=/dev/nfs rw >>>> nfsroot=192.168.10.2:/opt/eldk-5.3/powerpc/rootfs-basic >>>> ip=192.168.10.4:192.168.10.2:192.168.10.1:255.255.255.0:Boss:eth0:off >>>> panic=1 console=ttyS0,115200 >>>> ## Starting vxWorks at 0x0010 ... >>>> >>>> >>>> please somebody provide me some link or any pointer to help me get more >>>> understanding about booting multiple os using uboot. >>>> ___ >>>> U-Boot mailing list >>>> U-Boot@lists.denx.de >>>> http://lists.denx.de/mailman/listinfo/u-boot >>>> >>> >>> >> > ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] VxWorks Booting using U-boot as Bootloader
Hi Hannes Thanks for your reply. I am using VxWorks 6.7 and the image is not stripped. The loadaddress is also same within kernel configuration. I am using bootvx command to boot VxWorks. Do I need to update boot parameters? On Sep 8, 2014 4:11 PM, "Hannes Petermaier" < hannes.peterma...@br-automation.com> wrote: > Hi Ashish, > > i had a problem booting vxworks in the past around interrupt vectors. > Which version of vxworks you are using ? do you use a stripped image ? > is the loadaddress the same within kernel configuration ? > > best regards, > hannes > > > From: Ashish Khetan > > To: u-boot@lists.denx.de > > Date: 04.09.2014 14:13 > > Subject: [U-Boot] VxWorks Booting using U-boot as Bootloader > > Sent by: u-boot-boun...@lists.denx.de > > > > Hi, > > I was trying to boot vxworks using u-boot bootloader for learning > purpose > > on MPC8640DHPCN board. Previously I successfully ported QNX os along > with > > linux on same board using u-boot. while booting using bootvx command its > > not booting and stucking after showing the following message: > > > > tftp 0100 vxWorks > > Speed: 1000, full duplex > > Using eTSEC1 device > > TFTP from server 192.168.10.2; our IP address is 192.168.10.4 > > Filename 'vxWorks'. > > Load address: 0x100 > > Loading: > * # > > # > > # > > 12.3 MiB/s > > done > > Bytes transferred = 2392432 (248170 hex) > > BOSSv2.0=> bootvx 0010 100 > > ## Ethernet MAC address not copied to NV RAM > > ## Using bootline (@ 0x4200): root=/dev/nfs rw > > nfsroot=192.168.10.2:/opt/eldk-5.3/powerpc/rootfs-basic > > ip=192.168.10.4:192.168.10.2:192.168.10.1:255.255.255.0:Boss:eth0:off > > panic=1 console=ttyS0,115200 > > ## Starting vxWorks at 0x0010 ... > > > > > > please somebody provide me some link or any pointer to help me get more > > understanding about booting multiple os using uboot. > > ___ > > U-Boot mailing list > > U-Boot@lists.denx.de > > http://lists.denx.de/mailman/listinfo/u-boot > > > ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] VxWorks Booting using U-boot as Bootloader
Hi, I was trying to boot vxworks using u-boot bootloader for learning purpose on MPC8640DHPCN board. Previously I successfully ported QNX os along with linux on same board using u-boot. while booting using bootvx command its not booting and stucking after showing the following message: tftp 0100 vxWorks Speed: 1000, full duplex Using eTSEC1 device TFTP from server 192.168.10.2; our IP address is 192.168.10.4 Filename 'vxWorks'. Load address: 0x100 Loading: *# # # 12.3 MiB/s done Bytes transferred = 2392432 (248170 hex) BOSSv2.0=> bootvx 0010 100 ## Ethernet MAC address not copied to NV RAM ## Using bootline (@ 0x4200): root=/dev/nfs rw nfsroot=192.168.10.2:/opt/eldk-5.3/powerpc/rootfs-basic ip=192.168.10.4:192.168.10.2:192.168.10.1:255.255.255.0:Boss:eth0:off panic=1 console=ttyS0,115200 ## Starting vxWorks at 0x0010 ... please somebody provide me some link or any pointer to help me get more understanding about booting multiple os using uboot. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] MPC8641 ASMP u-boot booting
Hi, I am a little bit confused about u-boot smp and u-boot asmp on mpc8641d based HPCN board. when i am enable config_mp, in which mode it boots? In SMP u-boot or ASMP u-boot? and if it boots in smp mode then how am i going to boot ASMP linux? Please show me some way to boot ASMP linux . Any pointer/direction will be really helpful. Thanks & Regards @$hi$h ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] MPC8641D stucks before relocation
I disabled the 2nd core by using "cfg_core1_enable" and D2_MSRCID1 signal is not connected and we are using DDR controller 2... will this create any obstacles to relocate? Is there any other register configuration for DDR? can somebody help me to understand this or give me some pointer to get more understanding for this... I am getting frusted because I am stuck at this point from last 20 days. please help... thanks in advance and Regards On Sat, Oct 26, 2013 at 12:20 AM, Ashish Khetan wrote: > Thanks For reply, i check DDR configuration using Code warrior, and > successfully getting read/write from DDR. I use the following configuration > in code warrior and same in u-boot... > writemem.l 0xf8006000 0x001f # CS0_BNDSwritemem.l > 0xf8006080 0x80914102 # CS0_CONFIGwritemem.l0xf8006100 0x0007 > # TIMING_CFG_3writemem.l0xf8006104 0xFF770F0F # TIMING_CFG_0 > writemem.l > 0xf8006108 0x7F78F777 # TIMING_CFG_1 writemem.l0xf800610C > 0x00205114 # TIMING_CFG_2 > > writemem.l0xf8006110 0x43088008 # DDR_SDRAM_CFG > > writemem.l0xf8006114 0x24401000 # DDR_SDRAM_CFG2 > writemem.l0xf8006118 0x43800E52 # DDR_SDRAM_MODE writemem.l > 0xf800611C 0x8000C000 # DDR_SDRAM_MODE_2writemem.l0xf8006120 > 0x # DDR_SDRAM_MD_CNTL writemem.l0xf8006124 0x0508 # > DDR_SDRAM_INTERVAL > > writemem.l0xf8006128 0x # DDR_DATA_INIT > > writemem.l0xf8006130 0x0380 # DDR_SDRAM_CLK_CNTL > > sleep 200 > > writemem.l0xf8006110 0xC3088008 # DDR_SDRAM_CFG > > > but I did not understand... can you give some light on this. > > thanks again... > > > On Fri, Oct 25, 2013 at 10:25 PM, York Sun wrote: > >> It is probably because your DDR wasn't initialized correctly. You can >> try to dump all DDR registers and check if anyone is suspicious. You can >> also override any register before enabling the controller. >> >> You may also add some memory test before relocation. >> >> York >> >> On 10/25/2013 06:38 AM, Ashish Khetan wrote: >> > hii I am using MPC8641D based custom board for evaluation purpose. I am >> > using minimal configuration for this board i.e. only FLASH and DDR >> > initialisation. when I compiled U-boot in debug mode its printing >> > addresses, i check for those addresses and found that it is unable to >> > relocate itself to DDR(4*MT47H64M16). The following message was >> printed... >> > >> > U-Boot 2013.04 (Oct 25 2013 - 15:05:33) >> > >> > Unicore software on multiprocessor system!! >> > To enable mutlticore build define CONFIG_MP >> > CPU: 8641, Version: 2.1, (0x80900021) >> > Core: E600 Core 0 (MSSCR0=8000, PORDEVSR=ab08307), Version: 2.2, >> > (0x80040202) >> > Clock Configuration: >> >CPU:800 MHz, MPX:400 MHz >> >DDR:200 MHz (400 MT/s data rate), LBC:25 MHz >> > L1:D-cache 32 KB enabled >> >I-cache 32 KB enabled >> > L2:Disabled >> > Board: Wind River SBC8641D >> > DRAM: DDR: 512 MiB >> > Top of RAM usable for U-Boot at: 2000 >> > Reserving 114k for U-Boot at: 1ffe3000 >> > Reserving 136k for malloc() at: 1ffc1000 >> > Reserving 80 Bytes for Board Info at: 1ffc0fb0 >> > Reserving 152 Bytes for Global Data at: 1ffc0f18 >> > Stack Pointer at: 1ffc0f00 >> > New Stack Pointer is: 1ffc0f00 >> > >> > and stuck here... >> > >> > Any pointer or link to get more about this will be helpful. >> > Thanks in Advance >> > >> > >> > >> > ___ >> > U-Boot mailing list >> > U-Boot@lists.denx.de >> > http://lists.denx.de/mailman/listinfo/u-boot >> > >> >> >> > ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] MPC8641D stucks before relocation
Thanks For reply, i check DDR configuration using Code warrior, and successfully getting read/write from DDR. I use the following configuration in code warrior and same in u-boot... writemem.l 0xf8006000 0x001f # CS0_BNDS writemem.l 0xf8006080 0x80914102 # CS0_CONFIG writemem.l0xf8006100 0x0007 # TIMING_CFG_3 writemem.l0xf8006104 0xFF770F0F # TIMING_CFG_0 writemem.l 0xf8006108 0x7F78F777 # TIMING_CFG_1 writemem.l0xf800610C 0x00205114 # TIMING_CFG_2 writemem.l0xf8006110 0x43088008 # DDR_SDRAM_CFG writemem.l0xf8006114 0x24401000 # DDR_SDRAM_CFG2 writemem.l0xf8006118 0x43800E52 # DDR_SDRAM_MODE writemem.l 0xf800611C 0x8000C000 # DDR_SDRAM_MODE_2 writemem.l0xf8006120 0x # DDR_SDRAM_MD_CNTL writemem.l0xf8006124 0x0508 # DDR_SDRAM_INTERVAL writemem.l0xf8006128 0x # DDR_DATA_INIT writemem.l0xf8006130 0x0380 # DDR_SDRAM_CLK_CNTL sleep 200 writemem.l0xf8006110 0xC3088008 # DDR_SDRAM_CFG but I did not understand... can you give some light on this. thanks again... On Fri, Oct 25, 2013 at 10:25 PM, York Sun wrote: > It is probably because your DDR wasn't initialized correctly. You can > try to dump all DDR registers and check if anyone is suspicious. You can > also override any register before enabling the controller. > > You may also add some memory test before relocation. > > York > > On 10/25/2013 06:38 AM, Ashish Khetan wrote: > > hii I am using MPC8641D based custom board for evaluation purpose. I am > > using minimal configuration for this board i.e. only FLASH and DDR > > initialisation. when I compiled U-boot in debug mode its printing > > addresses, i check for those addresses and found that it is unable to > > relocate itself to DDR(4*MT47H64M16). The following message was > printed... > > > > U-Boot 2013.04 (Oct 25 2013 - 15:05:33) > > > > Unicore software on multiprocessor system!! > > To enable mutlticore build define CONFIG_MP > > CPU: 8641, Version: 2.1, (0x80900021) > > Core: E600 Core 0 (MSSCR0=8000, PORDEVSR=ab08307), Version: 2.2, > > (0x80040202) > > Clock Configuration: > >CPU:800 MHz, MPX:400 MHz > >DDR:200 MHz (400 MT/s data rate), LBC:25 MHz > > L1:D-cache 32 KB enabled > >I-cache 32 KB enabled > > L2:Disabled > > Board: Wind River SBC8641D > > DRAM: DDR: 512 MiB > > Top of RAM usable for U-Boot at: 2000 > > Reserving 114k for U-Boot at: 1ffe3000 > > Reserving 136k for malloc() at: 1ffc1000 > > Reserving 80 Bytes for Board Info at: 1ffc0fb0 > > Reserving 152 Bytes for Global Data at: 1ffc0f18 > > Stack Pointer at: 1ffc0f00 > > New Stack Pointer is: 1ffc0f00 > > > > and stuck here... > > > > Any pointer or link to get more about this will be helpful. > > Thanks in Advance > > > > > > > > ___ > > U-Boot mailing list > > U-Boot@lists.denx.de > > http://lists.denx.de/mailman/listinfo/u-boot > > > > > ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] MPC8641D stucks before relocation
hii I am using MPC8641D based custom board for evaluation purpose. I am using minimal configuration for this board i.e. only FLASH and DDR initialisation. when I compiled U-boot in debug mode its printing addresses, i check for those addresses and found that it is unable to relocate itself to DDR(4*MT47H64M16). The following message was printed... U-Boot 2013.04 (Oct 25 2013 - 15:05:33) Unicore software on multiprocessor system!! To enable mutlticore build define CONFIG_MP CPU: 8641, Version: 2.1, (0x80900021) Core: E600 Core 0 (MSSCR0=8000, PORDEVSR=ab08307), Version: 2.2, (0x80040202) Clock Configuration: CPU:800 MHz, MPX:400 MHz DDR:200 MHz (400 MT/s data rate), LBC:25 MHz L1:D-cache 32 KB enabled I-cache 32 KB enabled L2:Disabled Board: Wind River SBC8641D DRAM: DDR: 512 MiB Top of RAM usable for U-Boot at: 2000 Reserving 114k for U-Boot at: 1ffe3000 Reserving 136k for malloc() at: 1ffc1000 Reserving 80 Bytes for Board Info at: 1ffc0fb0 Reserving 152 Bytes for Global Data at: 1ffc0f18 Stack Pointer at: 1ffc0f00 New Stack Pointer is: 1ffc0f00 and stuck here... Any pointer or link to get more about this will be helpful. Thanks in Advance ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
