Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Community Manager
2,252 Views

Fresh Quark Board Bring-Up Issue

Hello everyone;

We have developed our custom board Based on Intel Quark x1000 Processor which is almost similar to Galileo rev 2 board except the RAM SIZE is 512MB(256MB+256MB).

We have loaded the Debug enabled "Flash+PlatformData.bin" into LSPI Flash. Flash+PlatformData.bin file was generated using the UDK2014.SPI source code.

Board boot up Process will stuck at the DXE Process as per Below logs.

Please Help us to solve the Issue as soon as possible.

Debug Log:

Platform Data Item List in System Area:

Quark Data Id:Len = 0x0001:0x0002 Desc = PlatformID Ver=0000

Quark Data Id:Len = 0x0006:0x0027 Desc = MrcParams Ver=0001

Quark Data Id:Len = 0x0003:0x0006 Desc = 1st MAC Ver=0000

Quark Data Id:Len = 0x0004:0x0006 Desc = 2nd MAC Ver=0000

Early Platform Thermal Sensor Init

Ioh MAC [B:0, D:20, F:6] VER:1037 ADDR:20-00-00-00-00-00

Ioh MAC [B:0, D:20, F:7] VER:1037 ADDR:20-00-00-00-00-00

Install PPI: 7408D748-FC8C-4EE6-9288-C4BEC092A410

Notify: PPI Guid: 7408D748-FC8C-4EE6-9288-C4BEC092A410, Peim notify entry point: 80015981

Reinstall PPI: 6F8C2B35-FEF4-448D-8256-E11B19D61077

Install PPI: F34C2FA0-DE88-4270-8414-961222F4521C

Flash Map PEIM Loaded

MRC Entry

MRC McFuseStat 0x00000429 : fus_dun_ecc_dis

MRC dram_width 0 rank_enables 1 ddr_speed 0

MRC flags: SCRAMBLE_EN

MRC density=2 tCL=6 tRAS=37500 tWTR=10000 tRRD=10000 tFAW=40000

MRC Version 0112 Nov 28 2016 10:21:08

Meminit build Nov 28 2016 10:21:07

POST: 0x100

POST: 0x101

POST: 0x200

POST: 0x200

POST: 0x103

POST: 0x104

POST: 0x300

POST: 0x300

POST: 0x310

POST: 0x311

POST: 0x312

POST: 0x313

POST: 0x314

POST: 0x400

POST: 0x400

POST: 0x105

POST: 0x106

POST: 0x500

POST: 0x500

POST: 0x510

POST: 0x600

POST: 0x600

POST: 0x610

POST: 0x630

POST: 0x120

POST: 0x700

POST: 0x700

POST: 0x710

POST: 0x711

POST: 0x712

POST: 0x713

POST: 0x720

RDQS T/B eye rank0 lane0 : 8-52 13-48

VREF R/L eye lane0 : 0-63 0-63

RDQS T/B eye rank0 lane1 : 5-55 9-50

VREF R/L eye lane1 : 0-63 0-63

POST: 0x740

POST: 0x800

POST: 0x800

POST: 0x810

POST: 0x811

WDQ eye rank0 lane0 : 234-287

WDQ eye rank0 lane1 : 243-297

POST: 0x10B

POST: 0x10C

POST: 0x10D

POST: 0x10E

POST: 0x110

POST: 0x111

POST: 0x112

POST: 0x113

HteMemInit....done

Memory test result 0

POST: 0x114

---------------------------

ALGO[CH:RK] BL0 BL1 BL2 BL3

===========================

RCVN[00:00] 463 464

WDQS[00:00] 294 301

WDQx[00:00] 260 270

RDQS[00:00] 030 029

VREF[00:00] 031 031

WCMD[00:00] 222 222

WCTL[00:00] 222 222

WCLK[00:00] 158 158

---------------------------

POST: 0x1FF

InstallEfiMemory.

Index 0, Page: 32

Index 1, Page: 3328

Index 2, Page: 96

Index 3, Page: 96

Index 4, Page: 64

Found 0xA0000 bytes at 0x0.

Found 0x60000 bytes at 0xA0000.

Found 0x1FCF0000 bytes at 0x100000.

Found 0x200000 bytes at 0x1FE00000.

Found 0x10000 bytes at 0x1FDF0000.

RedirectMemoryServicesSetPool Base:Size 0x00100000:0x1BED0000

PeiInstallPeiMemory MemoryBegin 0x1BFD0000, MemoryLength 0x2FE0000

RmuMain Base Address : 0x1FDF0000

Found Microcode ADDR:SIZE 0x80000514:0x2000

SaveConfig.

CpuData.CpuAddressWidth : 32

IIO[0] busbase = 0 Limit=FF

IIO[0] IoBase = 2000 IoLimit=FFFF

IIO[0] IoApicBase = FEC00000 IoApicLimit=FEC00FFF

IIO[0] Mem32Base = 90000000 Mem32Limit=AFFFFFFF

IIO[0] RcbaAddress=FED1C000

MemoryInit Complete.

Early PCIe controller initialisation

Platform Erratas After MRC

Register PPI Notify: F894643D-C449-42D1-8EA8-85BDD8C65BDE

Platform Erratas After MRC0

Temp Stack : BaseAddress=0x8007C000 Length=0x4000

Temp Heap : BaseAddress=0x80078000 Length=0x1608

Total temporary memory: 32768 bytes.

temporary memory stack ever used: 16384 bytes.

temporary memory heap used: 5640 bytes.

Old Stack size 16384, New stack size 131072

Stack Hob: BaseAddress=0x1BFD0000 Length=0x20000

Heap Offset = 0x64088000 Stack Offset = 0x64090000

Loading PEIM at 0x0001EFA4150 EntryPoint=0x0001EFA4240

PeiCore.efiImage.c

Reinstall PPI: 8C8CE578-8A3D-4F1C-9935-896185C32DD3

Reinstall PPI: 5473C07A-3DCB-4DCA-BD6F-1E9689E7349A

Reinstall PPI: B9E0ABFE-5979-4914-977F-6DEE78C278A6

Install PPI: F894643D-C449-42D1-8EA8-85BDD8C65BDE

Notify: PPI Guid: F894643D-C449-42D1-8EA8-85BDD8C65BDE, Peim notify entry point: 8002707D

Platform PEIM Memory Callback

Install PPI: EF398D58-9DFD-4103-BF94-78C6F4FE712F

Install PPI: 1F4C6F90-B06B-48D8-A201-BAE5F1CD7D56

Install PPI: 49EDB1C1-BF21-4761-BB12-EB0031AABB39

Notify: PPI Guid: 49EDB1C1-BF21-4761-BB12-EB0031AABB39, Peim notify entry point: 8000594B

The 1th FV start address is 0x0001EE83400, size is 0x00120000, handle is 0x1EE83400

Found firmware volume Image File 1EE83448 in FV[1] 1EE83400

Notify: PPI Guid: 49EDB1C1-BF21-4761-BB12-EB0031AABB39, Peim notify entry point: 80027CDA

PeiSecurityVerifyFv - CurrentFvAddress=0x1EE83400

CpuAddressWidth: 32

Loading PEIM at 0x0001EE81150 EntryPoint=0x0001EE81240

SmmAccessPei.efiImage.c

Install PPI: 268F33A9-CCCD-48BE-8817-86053AC32ED6

SMM Base:Size 1FE00000:00200000

Loading PEIM at 0x0001EE80150 EntryPoint=0x0001EE80240

SmmControlPei.efi

Install PPI: 61C68702-4D7E-4F43-8DEF-A74305CE74C5

Loading PEIM at 0x0001EE7A150 EntryPoint=0x0001EE7A240

DxeIpl.efiImage.c

Install PPI: EE4E5898-3914-4259-9D6E-DC7BD79403CF

Install PPI: A31280AD-481E-41B6-95E8-127F4C984779

Install PPI: 0AE8CE5D-E448-4437-A8D7-EBF5F194F731

Install PPI: 1A36E4E7-FAB6-476A-8E75-695A0576FDD7

Loading PEIM at 0x0001EE78150 EntryPoint=0x0001EE78240

PiSmmCommunicationPei.efi

Loading PEIM at 0x0001EE72150 EntryPoint=0x0001EE72240

S3Resume2Pei.efi

Install PPI: 6D582DBC-DB85-4514-8FCC-5ADF6227B147

Customized Guided section Memory Size required is 0x24C010 and address is 0x1EC20000

Extract guided section Failed - Invalid Parameter

Customized Guided section Memory Size required is 0x24C010 and address is 0x1E9CE000

Extract guided section Failed - Invalid Parameter

DXE IPL Entry

10 Replies
Highlighted
Community Manager
13 Views

Hi Nikunj,

 

 

Thank you for contacting us. We'll help you solve this this issue. Could you provide more details about how you created the Flash+PlatformData.bin file from the UDK2014 SPI source code? If you could provide the steps you followed or a link with information or files you used to create this file it'd be of great help.

 

 

Did you follow the steps on the Quark X1000 BSP? According to Section 9 of the Quark datasheet you need to create the Flash+PlatformData.bin file running the script platform-data-patch.py, which can be found in the spi-flash-tools tarball. Did you run this script to create this file?

 

 

I also noticed the line which says Customized Guided section Memory Size required is 0x24C010 and address is 0x1EC20000. Did you do any software related customization that's related to this message?

 

 

I'll be waiting for your response.

 

 

-Sergio

 

0 Kudos
Highlighted
Community Manager
13 Views

We are following below configuration for Hardware & software.

  • Hardware : We have prototype based on Intel Galileo Gen2 board with Intel Quark X1000 chipset:
    • DDR3 upgrade to 512MB with Channel 0 , Rank 0 Low memory down configure.
    • No PCIe connections
    • No GPIO Mux or Expander
  • Software :
    • We have used following Quark EDKII to start actual grub loader after configuring and loading PEI modules, DXE core & modules and SMM modules using UEFI Shell.
      • Quark EDKII 1.1.0 (We are using)
      • Quark EDKII 1.2.1 (We have checked to verify issue and getting same issue)
    • We have verified following DDR3 memory related parameters into sample-plateform-data.ini file which is stored inside platform-data section and we have generated Flash+PlaformData.bin after applying patch of ini file.
data[00-01] - platform_id u16 - should match value of platform type/id record as sanity check.0800# data[02-05] - flags u32 - bit[0] ECC_EN, bit[1] SCRAMBLE_EN, others=RESERVED02000000# data[06] - dram_width u8 - 0=x8, 1=x16, others=RESERVED.00# data[07] - dram_speed u8 - 0=DDRFREQ_800, 1=DDRFREQ_1066, others=RESERVED. Only 533MHz SKU support 1066 memory.00# data[08] - dram_type u8 - 0=DDR3, 1=DDR3L, others=RESERVED.00# data[09] - rank_mask u8 - bit[0] RANK0_EN, bit[1] RANK1_EN, others=RESERVED.01# data[0A] - chan_mask u8 - bit[0] CHAN0_EN, others=RESERVED..01# data[0B] - chan_width u8 - 1=x16, others=RESERVED.01# data[0C] - addr_mode u8 - 0, 1, 2 (mode 2 forced if ecc enabled), others=RESERVED00# data[0D] - sr_int u8 - 1=1.95us, 2=3.9us, 3=7.8us, others=RESERVED. REFRESH_RATE.03# data[0E] - sr_temp u8 - 0=normal, 1=extended, others=RESERVED. SR_TEMP_RANGE.00# data[0F] - dram_ron_val u8 - 0=34ohm, 1=40ohm, others=RESERVED. RON_VALUE Select MRS1.DIC driver impedance control.00# data[10] - dram_rtt_nom_val u8 - 0=40ohm, 1=60ohm, 2=120ohm, others=RESERVED. RTT_NOM_VALUE.02# data[11] - dram_rtt_wr_val u8 - 0=off, others=RESERVED00# data[12] - soc_rd_odt_val u8 - 0=off, 1=60ohm, 2=120ohm, 3=180ohm, others=RESERVED. RD_ODT_VALUE.00# data[13] - soc_wr_ron_val u8 - 0=27ohm, 1=32ohm, 2=40ohm, others=RESERVED. (WR_RON_VALUE select Vref code for DQ DRV PU evaluation using external resistor).01# data[14] - soc_wr_slew u8 - 0=2.5V/ns, 1=4V/ns, others=RESERVED. (WR_SLEW_RATE).01# data[15] - dram_density u8 - 0=512Mb, 1=Gb, 2=2Gb, 3=4Gb, others=RESERVED.02# data[16-19] - tRAS u32 - ACT to PRE command period in picoseconds.7C920000# data[1A-1D] - tWTR u32 - Delay from start of internal write transaction to internal read command in picoseconds.10270000# data[1E-21] - tRRD u32 - ACT to ACT command period (JESD79 specific to page size 1K/2K) in picoseconds.10270000# data[22-25] - tFAW u32 - Four activate window (JESD79 specific to page size 1K/2K) in picoseconds.409c0000# data[26] - tCL u8 - DRAM CAS Latency in cl06

  • So, we have updated DRAM density to 02 as per DDR3 RAM size 512MB (256MB x 2) into ini file and it seems like initial block 32 MB of Total RAM is initialized after that settings. All other parameters are same as Intel Galileo Gen 2 board which we are using now for our development purpose.
  • We are also using following commands to generate Flash+PlaformData.bin in debug mode to get all debug logs on UART1 after flashing that bin file into LSPI Flash using Dediprog tool and starting debug console on UART1 with baud-rate 115200.

     

  • ./buildallconfigs.sh GCC46 QuarkPlatform ---> Build EDKII source files

     

  • ../../spi-flash-tools_v1.1.0/Makefile ---> To generate Flash-missingPDAT.bin which should be stored into SPI Flash

     

  • python platform-data-patch.py -p sample-platform-data.ini -i ../../sysimage_*/sysimage.CP-8M-debug/Flash-missingPDAT.bin ---> To apply platform data patch means ini file related changes which we have made as per above data

     

  • sudo ./flashrom -p dediprog -w Flash+PlatformData.bin ---> To flash final image into LSPI Flash

     

Issue : Board boot-up process is stuck while extracting GUID section decode in DxeLoad.c file which is mainly used to customize guided section memor...

0 Kudos
Highlighted
Community Manager
13 Views

Hi Nikunj,

 

 

Thank you for providing such a detailed response. I've a few comments and suggestions:

 

 

-You said you've updated the DRAM density value to 02. In the data[15] line which is underlined you should choose the 512Mb option, which can be seen here https://kernel.googlesource.com/pub/scm/linux/kernel/git/jejb/Quark_EDKII/+/master/galileo-platform-... https://kernel.googlesource.com/pub/scm/linux/kernel/git/jejb/Quark_EDKII/+/master/galileo-platform-... . Confirm you've chosen the appropriate value in this point.

 

 

-Next, where you typed this command ./buildallconfigs.sh GCC46 QuarkPlatform, you have to take into account this applies for release 1.1 and earlier and you said you also tried 1.2.1 so make sure you've used the correct command for the version you're trying. Also, depending on the release you're using you have to take into consideration the GCC version installed on your system. For GCC4x there's a note that says: "GCC flags used for this build. Set to the version of GCC you have installed. Note: Tested on GCC46. GCC43 is not supported from release 1.2 onwards." Which GCC version do you have installed on your system? You can see these notes in the Quark X1000 BSP section 4. http://www.intel.com/content/www/us/en/embedded/products/quark/quark-x1000-bsp-build-sw-rel-user-gui... http://www.intel.com/content/www/us/en/embedded/products/quark/quark-x1000-bsp-build-sw-rel-user-gui...

 

 

-Also, in the last section I noticed you set dram_speed = DDRFREQ_1066. Remember that 1066MHz DDR3 RAM is not supported, as can be seen in this thread /thread/108051 https://communities.intel.com/thread/108051 .

 

 

Let us know if you find this useful.

 

 

-Sergio

 

0 Kudos
Highlighted
Community Manager
13 Views

Hello Sergio;

Thanks for your help;

Hardware : We have prototype based on Intel Galileo Gen2 board with Intel Quark X1000 chipset:

  • DDR3 upgrade to 512MB with Channel 0 , Rank 0 Low memory down configure.
  • No PCIe connections
  • No GPIO Mux or Expander.

We have compile same code with above method and load into Galileo Rev 2 board . Galileo Rev 2 Board is proper boot up and proper work with the SD imge mode and Flash image Mode.

We have load same code in our custom board but it is not proper work and stop with below error. Also behaviour of our board is random means some time stop at "Platform PEIM Memory Callback" and some time stop with "Extract guided section Failed - Invalid Parameter" error.

If you have face any problem related to this please help us how to debug with hardware point of view or tell us if any our debugging method to debug our custom board.

Debug Log:

Install PPI: 1E2ACC41-E26A-483D-AFC7-A056C34E087B

Register PPI Notify: 3ACF33EE-D892-40F4-A2FC-3854D2E1323D

Loading PEIM at 0x00080012C6C EntryPoint=0x00080012D5C FaultTolerantWritePei.efi

Install PPI: 1D3E9CB8-43AF-490B-830A-3516AA532047

Loading PEIM at 0x00080013EA4 EntryPoint=0x00080013F94 PeiVariable.efi

Install PPI: 2AB86EF5-ECB5-4134-B556-3854CA1FE1B4

Loading PEIM at 0x00080015894 EntryPoint=0x00080015984 CpuPei.efi

Install PPI: C153205A-E898-4C24-8689-A4B4BCC5C8A2

Register PPI Notify: 7408D748-FC8C-4EE6-9288-C4BEC092A410

Loading PEIM at 0x00080018CCC EntryPoint=0x00080018DBC CapsulePei.efi

Install PPI: 3ACF33EE-D892-40F4-A2FC-3854D2E1323D

Notify: PPI Guid: 3ACF33EE-D892-40F4-A2FC-3854D2E1323D, Peim notify entry point: 800247C5

IsFirstBoot = 1 , EnableFastBoot= 1.

BootMode: FullCfg

Register PPI Notify: 49EDB1C1-BF21-4761-BB12-EB0031AABB39

Quark EDKII SECURE LOCKDOWN DISABLED

Quark EDKII Stage1 Boot Image 0

Quark EDKII Stage2 0xFFD70400:0x0011FC00 - Payload 0xFF800400:0x00100000

Platform Data Item List in System Area:

Early Platform Thermal Sensor Init

Ioh MAC [B:0, D:20, F:6] VER:1037 ADDR:02-00-00-00-00-00

Ioh MAC [B:0, D:20, F:7] VER:1037 ADDR:02-00-00-00-00-01

Install PPI: 7408D748-FC8C-4EE6-9288-C4BEC092A410

Notify: PPI Guid: 7408D748-FC8C-4EE6-9288-C4BEC092A410, Peim notify entry point: 80015B72

Reinstall PPI: 6F8C2B35-FEF4-448D-8256-E11B19D61077

Install PPI: F34C2FA0-DE88-4270-8414-961222F4521C

Flash Map PEIM Loaded

MRC Entry

MRC McFuseStat 0x00000429 : fus_dun_ecc_dis

MRC dram_width 0 rank_enables 1 ddr_speed 0

MRC flags: SCRAMBLE_EN

MRC density=2 tCL=6 tRAS=37500 tWTR=10000 tRRD=10000 tFAW=40000

MRC Version 0112 Nov 29 2016 11:24:19

Meminit build Nov 29 2016 11:24:18

POST: 0x100

POST: 0x101

POST: 0x200

POST: 0x200

POST: 0x103

POST: 0x104

POST: 0x300

POST: 0x300

POST: 0x310

POST: 0x311

POST: 0x312

POST: 0x313

POST: 0x314

POST: 0x400

POST: 0x400

POST: 0x105

POST: 0x106

POST: 0x500

POST: 0x500

POST: 0x510

POST: 0x600

POST: 0x600

POST: 0x610

POST: 0x630

POST: 0x120

POST: 0x700

POST: 0x700

POST: 0x710

POST: 0x711

POST: 0x712

POST: 0x713

POST: 0x720

RDQS T/B eye rank0 lane0 : 7-53 13-49

VREF R/L eye lane0 : 0-63 0-63

RDQS T/B eye rank0 lane1 : 5-54 9-50

VREF R/L eye lane1 : 0-63 0-63

POST: 0x740

POST: 0x800

POST: 0x800

POST: 0x810

POST: 0x811

WDQ eye rank0 lane0 : 235-287

WDQ eye rank0 lane1 : 243-297

POST: 0x10B

POST: 0x10C

POST: 0x10D

POST: 0x10E

POST: 0x110

POST: 0x111

POST: 0x112

POST: 0x113

HteMemInit....done

Memory test result 0

POST: 0x114

---------------------------

ALGO[CH:RK] BL0 BL1 BL2 BL3

===========================

RCVN[00:00] 464 465

WDQS[00:00] 294 301

WDQx[00:00] 261 270

RDQS[00:00] 030 029

VREF[00:00] 031 031

WCMD[00:00] 222 222

WCTL[00:00] 222 222

WCLK[00:00] 158 158

---------------------------

POST: 0x1FF

InstallEfiMemory.

Index 0, Page: 32

Index 1, Page: 3328

Index 2, Page: 96

Index 3, Page: 96

Index 4, Page: 64

Found 0xA0000 bytes at 0x0.

Found 0x60000 bytes at 0xA0000.

Found 0x1FCF0000 bytes at 0x100000.

Found 0x200000 bytes at 0x1FE00000.

Found 0x10000 bytes at 0x1FDF0000.

RedirectMemoryServicesSetPool Base:Size 0x00100000:0x1BED0000

PeiInstallPeiMemory MemoryBegin 0x1BFD0000, MemoryLength 0x2FE0000

RmuMain Base Address : 0x1FDF0000

Found Microcode ADDR:SIZE 0x80000504:0x2000

SaveConfig.

CpuData.CpuAddressWidth : 32

IIO[0] busbase = 0 Limit=FF

IIO[0] IoBase = 2000 IoLimit=FFFF

IIO[0] IoApicBase = FEC00000 IoApicLimit=FEC00FFF

IIO[0] Mem32Base = 90000000 Mem32Limit=AFFFFFFF

IIO[0] RcbaAddress=FED1C000

MemoryInit Complete.

Early PCIe controller initialisation

Platform Erratas After MRC

Register PPI Notify: F894643D-C449-42D1-8EA8-85BDD8C65BDE

Temp Stack : BaseAddress=0x8007C000 Length=0x4000

Temp Heap : BaseAddress=0x80078000 Length=0x1620

Total temporary memory: 32768 bytes.

temporary memory stack ever used: 16384 bytes.

temporary memory heap used: 5664 bytes.

Old Stack size 16384, New stack size 131072

Stack Hob: BaseAddress=0x1BFD0000 Length=0x20000

Heap Offset = 0x64088000 Stack Offset = 0x64090000

Loading PEIM at 0x0001EFA4150 EntryPoint=0x0001EFA4240 PeiCore.efi

Reinstall PPI: 8C8CE578-8A3D-4F1C-9935-896185C32DD3

Reinstall PPI: 5473C07A-3DCB-4DCA-BD6F-1E9689E7349A

Reinstall PPI: B9E0ABFE-5979-4914-977F-6DEE78C278A6

Install PPI: F894643D-C449-42D1-8EA8-85BDD8C65BDE

Notify: PPI Guid: F894643D-C449-42D1-8EA8-85BDD8C65BDE, Peim notify entry point: 800261E7

Platform PEIM Memory Callback

Install PPI: EF398D58-9DFD-4103-BF94-78C6F4FE712F

Install PPI: 1F4C6F90-B06B-48D8-A201-BAE5F1CD7D56

Install PPI: 49EDB1C1-BF21-4761-BB12-EB0031AABB39

Notify: PPI Guid: 49EDB1C1-BF21-4761-BB12-EB0031AABB39, Peim notify entry point: 80005974

The 1th FV start address is 0x0001EE84400, size is 0x0011FC00, handle is 0x1EE84400

Found firmware volume Image File 1EE84448 in FV[1] 1EE84400

Notify: PPI Guid: 49EDB1C1-BF21-4761-BB12-EB0031AABB39, Peim notify entry point: 80026D18

PeiSecurityVerifyFv - CurrentFvAddress=0x1EE84400

CpuAddressWidth: 32

Loading PEIM at 0x000...

0 Kudos
Highlighted
Community Manager
13 Views

Hi Nikunj,

 

 

I want to double check to make sure I'm understanding your issue correctly. You said that the image you flashed onto the Galileo and your custom board is the same, and that that image boots only on the Galileo, is this correct? I also looked at the Platform PEIM Memory Callback message you highlighted and this doesn't seem to be an error. What seems to be causing this is the message before Extract guided section Failed - Invalid Parameter, that's related to memory.

 

In our previous reply we asked about the dram density, the GCC compiler used and the supported memory types. Have you checked that you're using the appropriate configurations, compilers and a supported memory configuration?

 

 

The debugging options available for the Quark X1000 can be found here https://www-ssl.intel.com/content/www/us/en/embedded/products/quark/x1000/documentation.html https://www-ssl.intel.com/content/www/us/en/embedded/products/quark/x1000/documentation.html in the documents OpenOCD Source Level Debug: Application Note and Debug Operations: Specification Update.

 

 

We'll be waiting for your response.

 

 

-Sergio

 

 

0 Kudos
Highlighted
Community Manager
13 Views

Hello Sergio;

Our Board Total dram Density: 512MB.

We are using GCC46 for compile the code.

We have been used same DDR3 RAM . just only change the double density (256MB instead of 128MB).

Thanks in advance.

0 Kudos
Highlighted
Community Manager
13 Views

Hi Nikunj,

 

 

There's some configuration that needs to be done in order to enable the DDR3. Have you modified any of these files? They can be found in section 5.7 of the UEFI Firmware Writers Guide.

 

 

You can find the guide here http://www.intel.com/content/www/us/en/embedded/products/quark/quark-x1000-uefi-firmware-writers-gui... . Section 5 has information about the DDR3 configuration. Let us know which files you edited and their contents.

 

 

We'll be waiting for your response.

 

 

-Sergio

 

0 Kudos
Highlighted
Employee
13 Views

Hi Nikunj,

Do you still need assistance with this case? Did you find useful the information we posted?

-Sergio

0 Kudos
Highlighted
Beginner
13 Views

We are observing the similar issue. May I know the fix/configuration made in Quark BIOS?

0 Kudos
Highlighted
Community Manager
13 Views

Hi jlkjk;

This was the issue related to the hardware and most likely ddr3 ram. I think you should resolder the ddr3 ram or processor.

0 Kudos