Dev June 2015

dev@lists.96boards.org

10 participants
12 discussions

by Peter Griffin

Hi folks, For fun I've done a minimal U-Boot port for the HiKey board, I thought I'd post it here in case anyone else is interested. This work is based on top of Linus Walleij Juno port. The code can be found here: - ssh://git@git.linaro.org:/people/peter.griffin/u-boot Currently the port supports: - 1) Serial 2) eMMC (although only basic read testing) 3) USB (ASIX usb networking works, no mass storage) 4) GPIO So you have ATF -> u-boot -> kernel / your_own_rtos The main "useful" thing I suppose is the ability to quickly tftp kernels etc into DDR over the network. Obviously the ability to toggle the LEDs in u-boot is also something to amuse yourself with. Pre-built binaries can be found here: - http://people.linaro.org/~peter.griffin/hikey/hikey-u-boot-release_r1/ NB: These are built with the latest PSCI enabled ATF, so you also need to use the corresponding PSCI enabled kernel to get all 8 cores. The readme on how to replicate everything from source can be found here: - http://people.linaro.org/~peter.griffin/hikey/hikey-u-boot-release_r1/u-boo… . Any patches please send them along to me, one obvious missing feature is sdhci support. That doesn't look very hard to get going, as long as we can get the IP clocked and out of reset (and would be significantly easier if the published datasheet documented the registers...). Have Fun! regards, Peter. p.s. serial trace below debug EMMC boot: print init OK debug EMMC boot: send RST_N . debug EMMC boot: start eMMC boot...... load fastboot1! Switch to aarch64 mode. CPU0 executes at 0xf9801000! NOTICE: Booting Trusted Firmware NOTICE: BL1: v1.1(release):9a97502 NOTICE: BL1: Built : 08:13:36, Mar 10 2015 NOTICE: succeed to init lpddr3 rank0 dram phy INFO: lpddr3_freq_init, set ddrc 533mhz INFO: init ddr3 rank0 in 533MHz INFO: ddr3 rank1 init pass in 533MHz INFO: Elpida DDR NOTICE: BL1: Booting BL2 NOTICE: BL2: v1.1(debug):9a97502 NOTICE: BL2: Built : 10:22:35, Mar 17 2015 INFO: BL2: Loading BL3-1 INFO: Using FIP INFO: Loading file 'bl31.bin' at address 0xf9858000 INFO: File 'bl31.bin' loaded: 0xf9858000 - 0xf985f010 INFO: BL2: Loading BL3-3 INFO: Using FIP INFO: Loading file 'bl33.bin' at address 0x37000000 INFO: File 'bl33.bin' loaded: 0x37000000 - 0x3703db38 NOTICE: BL1: Booting BL3-1 NOTICE: BL3-1: v1.1(debug):9a97502 NOTICE: BL3-1: Built : 10:22:38, Mar 17 2015 INFO: BL3-1: Initializing runtime services INFO: BL3-1: Preparing for EL3 exit to normal world INFO: BL3-1: Next image address = 0x37000000 INFO: BL3-1: Next image spsr = 0x3c9 U-Boot 2015.04-rc1-00010-g49ec0dd (Mar 17 2015 - 10:11:00) hikey_aemv8a DRAM: 1 GiB MMC: HiKey DWMMC: 0 Using default environment In: serial Out: serial Err: serial Net: Net Initialization Skipped No ethernet found. Hit any key to stop autoboot: 0 HiKey64# usb start starting USB... USB0: Core Release: 3.00a scanning bus 0 for devices... 3 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found scanning usb for ethernet devices... Warning: asx0 using MAC address from net device 1 Ethernet Device(s) found HiKey64# HiKey64# setenv ipaddr 192.168.0.200 HiKey64# HiKey64# setenv serverip 192.168.0.10 HiKey64# HiKey64# tftpboot 0x10000000 Image Using asx0 device TFTP from server 192.168.0.10; our IP address is 192.168.0.200 Filename 'Image'. Load address: 0x10000000 Loading: ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ######################################################T ########### ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ############################################## 238.3 KiB/s done Bytes transferred = 12214232 (ba5fd8 hex) HiKey64# tftpboot 0x13000000 hi6220-hikey.dtb Using asx0 device TFTP from server 192.168.0.10; our IP address is 192.168.0.200 Filename 'hi6220-hikey.dtb'. Load address: 0x13000000 Loading: ################# 237.3 KiB/s done Bytes transferred = 85319 (14d47 hex) HiKey64# ï¿½ooti 0x10000000 - 0x13000000 Unknown command 'ï¿½ooti' - try 'help' HiKey64# Unknown command 'ï¿½ooti' - try 'help' HiKey64# booti 0x10000000 - 0x13000000 ## Flattened Device Tree blob at 13000000 Booting using the fdt blob at 0x13000000 Using Device Tree in place at 0000000013000000, end 0000000013017d46 Starting kernel ... [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 3.18.0+ (griffinp@griffinp-ThinkPad-X1-Carbon-2nd) (gcc version 4.9.2 20140904 (prerelease) (crosstool-NG linaro-1.13.1-4.9-2014.09 - Linaro GCC 4.9-2014.09) ) #5 SMP PREEMPT Tue Mar 17 08:21:27 GMT 2015 [ 0.000000] CPU: AArch64 Processor [410fd033] revision 3 [ 0.000000] Detected VIPT I-cache on CPU0 [ 0.000000] efi: Getting EFI parameters from FDT: [ 0.000000] efi: UEFI not found. [ 0.000000] cma: Reserved 16 MiB at 0x000000003f000000 [ 0.000000] On node 0 totalpages: 262144 [ 0.000000] DMA zone: 3584 pages used for memmap [ 0.000000] DMA zone: 0 pages reserved [ 0.000000] DMA zone: 262144 pages, LIFO batch:31 [ 0.000000] psci: probing for conduit method from DT. [ 0.000000] psci: PSCIv1.0 detected in firmware. [ 0.000000] psci: Using standard PSCI v0.2 function IDs [ 0.000000] PERCPU: Embedded 14 pages/cpu @ffffffc03eefc000 s18688 r8192 d30464 u57344 [ 0.000000] pcpu-alloc: s18688 r8192 d30464 u57344 alloc=14*4096 [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0] 4 [0] 5 [0] 6 [0] 7 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 258560 [ 0.000000] Kernel command line: console=ttyAMA0,115200n8 root=/dev/sda1 rw earlyprintk=pl011,0x7ff80000 debug user_debug=31 loglevel=9 [ 0.000000] log_buf_len individual max cpu contribution: 4096 bytes [ 0.000000] log_buf_len total cpu_extra contributions: 28672 bytes [ 0.000000] log_buf_len min size: 16384 bytes [ 0.000000] log_buf_len: 65536 bytes [ 0.000000] early log buf free: 14752(90%) [ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes) [ 0.000000] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes) [ 0.000000] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes) [ 0.000000] Memory: 994464K/1048576K available (7777K kernel code, 651K rwdata, 3116K rodata, 376K init, 492K bss, 54112K reserved) [ 0.000000] Virtual kernel memory layout: [ 0.000000] vmalloc : 0xffffff8000000000 - 0xffffffbdffff0000 ( 247 GB) [ 0.000000] vmemmap : 0xffffffbe00000000 - 0xffffffbfc0000000 ( 7 GB maximum) [ 0.000000] 0xffffffbe00000000 - 0xffffffbe00e00000 ( 14 MB actual) [ 0.000000] PCI I/O : 0xffffffbffa000000 - 0xffffffbffb000000 ( 16 MB) [ 0.000000] fixed : 0xffffffbffbdfe000 - 0xffffffbffbdff000 ( 4 KB) [ 0.000000] modules : 0xffffffbffc000000 - 0xffffffc000000000 ( 64 MB) [ 0.000000] memory : 0xffffffc000000000 - 0xffffffc040000000 ( 1024 MB) [ 0.000000] .init : 0xffffffc000b25000 - 0xffffffc000b83000 ( 376 KB) [ 0.000000] .text : 0xffffffc000080000 - 0xffffffc000b24564 ( 10898 KB) [ 0.000000] .data : 0xffffffc000b83000 - 0xffffffc000c25fd8 ( 652 KB) [ 0.000000] Preemptible hierarchical RCU implementation. [ 0.000000] RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=8. [ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8 [ 0.000000] NR_IRQS:64 nr_irqs:64 16 [ 0.000000] hisi_clk_register_stub: base=0xffffff8000002af4, comm_base=0xffffff8000008000 [ 0.000000] hisi_clk_init: base ffffff800000a000 [ 0.000000] hisi_clk_init: base ffffff800000c000 [ 0.000000] hisi_clk_init: base ffffff800000e000 [ 0.000000] hisi_clk_init: base ffffff8000010000 [ 0.000000] Architected cp15 timer(s) running at 1.20MHz (phys). [ 0.000005] sched_clock: 56 bits at 1200kHz, resolution 833ns, wraps every 3579139414016ns [ 0.000422] Console: colour dummy device 80x25 [ 0.001558] allocated 4194304 bytes of page_cgroup [ 0.001562] please try 'cgroup_disable=memory' option if you don't want memory cgroups [ 0.001575] Calibrating delay loop (skipped), value calculated using timer frequency.. 2.40 BogoMIPS (lpj=12000) [ 0.001584] pid_max: default: 32768 minimum: 301 [ 0.001694] Security Framework initialized [ 0.001710] SELinux: Initializing. [ 0.001737] SELinux: Starting in permissive mode [ 0.001787] Mount-cache hash table entries: 2048 (order: 2, 16384 bytes) [ 0.001794] Mountpoint-cache hash table entries: 2048 (order: 2, 16384 bytes) [ 0.002309] Initializing cgroup subsys memory [ 0.002333] Initializing cgroup subsys freezer [ 0.002343] Initializing cgroup subsys hugetlb [ 0.002352] Initializing cgroup subsys debug [ 0.004190] /cpus/cpu@0: Missing clock-frequency property [ 0.004230] /cpus/cpu@1: Missing clock-frequency property [ 0.004269] /cpus/cpu@2: Missing clock-frequency property [ 0.004309] /cpus/cpu@3: Missing clock-frequency property [ 0.004350] /cpus/cpu@4: Missing clock-frequency property [ 0.004393] /cpus/cpu@5: Missing clock-frequency property [ 0.004437] /cpus/cpu@6: Missing clock-frequency property [ 0.004481] /cpus/cpu@7: Missing clock-frequency property [ 0.004517] hw perfevents: enabled with arm/armv8-pmuv3 PMU driver, 7 counters available [ 0.004545] EFI services will not be available. [ 0.079936] CPU1: Booted secondary processor [ 0.079944] Detected VIPT I-cache on CPU1 [ 0.099879] CPU2: Booted secondary processor [ 0.099882] Detected VIPT I-cache on CPU2 [ 0.119886] CPU3: Booted secondary processor [ 0.119889] Detected VIPT I-cache on CPU3 [ 0.139922] CPU4: Booted secondary processor [ 0.139929] Detected VIPT I-cache on CPU4 [ 0.159920] CPU5: Booted secondary processor [ 0.159924] Detected VIPT I-cache on CPU5 [ 0.179929] CPU6: Booted secondary processor [ 0.179932] Detected VIPT I-cache on CPU6 [ 0.199941] CPU7: Booted secondary processor [ 0.199944] Detected VIPT I-cache on CPU7 [ 0.200014] Brought up 8 CPUs [ 0.200049] SMP: Total of 8 processors activated. [ 0.200626] devtmpfs: initialized [ 0.204994] xor: measuring software checksum speed [ 0.299605] 8regs : 2381.600 MB/sec [ 0.399639] 8regs_prefetch: 2176.000 MB/sec [ 0.499674] 32regs : 2639.200 MB/sec [ 0.599708] 32regs_prefetch: 2321.600 MB/sec [ 0.599714] xor: using function: 32regs (2639.200 MB/sec) <snip>

8 years, 9 months

bl1 crash

by Stefan Johansson

So I built hikey ATF and l-loader for the first time and seemed to be able to flash the l-loader.bin However, the serial log shows this, what did I do wrong ? debug EMMC boot: print init OK debug EMMC boot: send RST_N . debug EMMC boot: start eMMC boot...... load fastboot1! Switch to aarch64 mode. CPU0 executes at 0xf9801000! INFO: BL1: 0xf9810000 - 0xf9817000 [size = 28672] NOTICE: Booting Trusted Firmware NOTICE: BL1: v1.1(debug):a0c0399 NOTICE: BL1: Built : 09:31:15, May 28 2015 INFO: BL1: RAM 0xf9810000 - 0xf9817000 Platform exception reporting: ESR_EL3: 0000000002000000 ELR_EL3: 00000000f9803348 ...

9 years

Re: [Dev] Is 96boards just another scam or another failing kickstarter project?

by Clint Cooley

Gregoire Total understand. As you may be aware Circuitco has been involved with OSHW for over 8 years. We are very excited about the 9 boards program and are comic red to making it a success and building a strong community. Thank you for your passion and I am also aware of your support of these types of communities We are happy to have you on board! Clint CooleyCircuitco Electronics LLCPresident -------- Original message -------- From: Gregoire Gentil <gregoire(a)gentil.com> Date: 06/12/2015 4:33 PM (GMT-06:00) To: Clint Cooley <clint(a)circuitco.com>, dev(a)lists.96boards.org Cc: customer.care(a)avnet.com, sales(a)circuitco.com Subject: Re: Is 96boards just another scam or another failing kickstarter project? Thanks for the answer and the clarification. It's more the lack of communication and the feeling to be in front of a black box à la Kickstarter that triggers my comment to the mailing list. I guess that I'm not the only one in this situation. I have waited for 4 months, at this point, I can probably wait for another week or so! Hopefully, customers (including me) are about to get those boards soon, Grégoire On 06/12/2015 02:27 PM, Clint Cooley wrote: > Hello Gregoire, > > Thank you for the escalation and my apologies for the lack of proper > communication. > > As you may know Circuitco did the hardware development and the initial > production for the Hikey board. Similar to any new product release > there have been some delays. The good news is production boards are > coming off our lines now and are shipping and hopefully stocked within > the next 5 days or less. > > I was unaware that Avnet actually allowed any purchase other than pre > order but will be happy to check in to this for you as we do work very > closely with them. > > The Hikey project is very real and I assure you not a scam. We have > actually delivered hundreds of pre production boards for Beta > development that was very well received. > > I am happy to directly address and facilitate a solution for you. Due > to customer confidentiality I will need to do this outside the public > forum. > > Please contact me directly at clint(a)circuitco.com. > > Thank you > > > Clint Cooley > President > Circuitco > > > > > > Clint Cooley > Circuitco Electronics LLC > President > > > -------- Original message -------- > From: Gregoire Gentil <gregoire(a)gentil.com> > Date: 06/12/2015 4:08 PM (GMT-06:00) > To: dev(a)lists.96boards.org > Cc: customer.care(a)avnet.com, sales(a)circuitco.com > Subject: Is 96boards just another scam or another failing kickstarter > project? > > To the project leader of 96 boards, > > > I have ordered through Avnet a HiKey board shortly after it was > announced. My order is dated February 19, four months ago (PO Number: > WEB5348914). And I still have received NOTHING. > > The shipping date has been pushed at least three times on the Avnet > website and the promise date is now /6/3/2015. BTW, today is 6/12/2015. > > I have contacted 96boards back a months ago and after a short email > exchange with CircuitCo (I still don't get it why my message was > forwarded to CircuitCo), I didn't receive neither a precise shipping > date, nor an explanation of what's going on. > > So can the project leader of 96boards.org explain the situation and > clarify if this project is just another scam or one of those failing > kickstarter project to deliver? How can I get a refund? Avnet is > refusing to reimburse. > > I don't know if I'm the only one in this situation, but this is a > complete poor experience. When I ordered, I didn't see a message like > "you are not going to receive your board soon". > > Grégoire > > PS: There is even not an email address on the 96boards.org website. Who > is in charge of this project?

9 years, 1 month

About enable software cursor of xf86-video-armsoc driver

by Xinliang Liu

Hello, since our SoC doesn't support hardware cursor, i want to enable SW cursor with xf86-video-armsoc driver. So i set the cursor API type to HWCURSOR_API_NONE in my driver. list as bellow. +struct drmmode_interface hisi_interface = { + 1 /* use_page_flip_events */, + 1 /* use_early_display */, + CURSORW /* cursor width */, + CURSORH /* cursor_height */, + CURSORPAD /* cursor padding */, + HWCURSOR_API_NONE /* cursor_api */, + NULL /* init_plane_for_cursor */, + 0 /* vblank_query_supported */, + create_custom_gem /* create_custom_gem */, +}; But when i run startx the X crash with log pasted bellow: And if i set the cursor API type to HWCURSOR_API_STANDARD, X can start up , but without cursor display. ---------------------xorg log start------------------- [ 92.153] (II) ARMSOC(0): drmmode_set_mode_major:428: Exiting [ 92.985] (EE) [ 92.985] (EE) Backtrace: [ 92.985] (EE) 0: /usr/bin/X (xorg_backtrace+0x5c) [0x7fb527075c] [ 92.985] (EE) [ 92.986] (EE) Segmentation fault at address 0x7fb50b7ffc [ 92.986] (EE) Fatal server error: [ 92.986] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 92.986] (EE) [ 92.986] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 92.986] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 92.986] (EE) [ 92.987] (EE) Server terminated with error (1). Closing log file. ---------------------xorg log end------------------- Does anybody know what's wrong it is? And how to enable SW cursor with xf86-video-armsoc driver? Best regards, xinliang

9 years, 1 month

Re: [Dev] Is 96boards just another scam or another failing kickstarter project?

by Clint Cooley

Hello Gregoire, Thank you for the escalation and my apologies for the lack of proper communication. As you may know Circuitco did the hardware development and the initial production for the Hikey board. Similar to any new product release there have been some delays. The good news is production boards are coming off our lines now and are shipping and hopefully stocked within the next 5 days or less. I was unaware that Avnet actually allowed any purchase other than pre order but will be happy to check in to this for you as we do work very closely with them. The Hikey project is very real and I assure you not a scam. We have actually delivered hundreds of pre production boards for Beta development that was very well received. I am happy to directly address and facilitate a solution for you. Due to customer confidentiality I will need to do this outside the public forum. Please contact me directly at clint(a)circuitco.com. Thank you Clint CooleyPresidentCircuitco Clint CooleyCircuitco Electronics LLCPresident -------- Original message -------- From: Gregoire Gentil <gregoire(a)gentil.com> Date: 06/12/2015 4:08 PM (GMT-06:00) To: dev(a)lists.96boards.org Cc: customer.care(a)avnet.com, sales(a)circuitco.com Subject: Is 96boards just another scam or another failing kickstarter project? To the project leader of 96 boards, I have ordered through Avnet a HiKey board shortly after it was announced. My order is dated February 19, four months ago (PO Number: WEB5348914). And I still have received NOTHING. The shipping date has been pushed at least three times on the Avnet website and the promise date is now /6/3/2015. BTW, today is 6/12/2015. I have contacted 96boards back a months ago and after a short email exchange with CircuitCo (I still don't get it why my message was forwarded to CircuitCo), I didn't receive neither a precise shipping date, nor an explanation of what's going on. So can the project leader of 96boards.org explain the situation and clarify if this project is just another scam or one of those failing kickstarter project to deliver? How can I get a refund? Avnet is refusing to reimburse. I don't know if I'm the only one in this situation, but this is a complete poor experience. When I ordered, I didn't see a message like "you are not going to receive your board soon". Grégoire PS: There is even not an email address on the 96boards.org website. Who is in charge of this project?

9 years, 1 month

Is 96boards just another scam or another failing kickstarter project?

by Gregoire Gentil

To the project leader of 96 boards, I have ordered through Avnet a HiKey board shortly after it was announced. My order is dated February 19, four months ago (PO Number: WEB5348914). And I still have received NOTHING. The shipping date has been pushed at least three times on the Avnet website and the promise date is now /6/3/2015. BTW, today is 6/12/2015. I have contacted 96boards back a months ago and after a short email exchange with CircuitCo (I still don't get it why my message was forwarded to CircuitCo), I didn't receive neither a precise shipping date, nor an explanation of what's going on. So can the project leader of 96boards.org explain the situation and clarify if this project is just another scam or one of those failing kickstarter project to deliver? How can I get a refund? Avnet is refusing to reimburse. I don't know if I'm the only one in this situation, but this is a complete poor experience. When I ordered, I didn't see a message like "you are not going to receive your board soon". Grégoire PS: There is even not an email address on the 96boards.org website. Who is in charge of this project?

9 years, 1 month

Hikey kernel crash on OE build

by Will Chen

Hi hikey_developers, I built OE hikey successfully, but the generated kernel will crash during booting. The attached files are conf setting and kernel crash log. Could you please check this issue? *Below are the build configurations:* willchen@willchen-NB:~/lhg/96board/hikey/oe/oe-core/hikey$ bitbake linux-hikey Parsing recipes: 100% |#########################################| Time: 00:00:39 Parsing of 1482 .bb files complete (0 cached, 1482 parsed). 1960 targets, 105 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "1.26.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "Ubuntu-14.04" TARGET_SYS = "aarch64-oe-linux" MACHINE = "hikey" DISTRO = "nodistro" DISTRO_VERSION = "nodistro.0" TUNE_FEATURES = "aarch64" TARGET_FPU = "" meta = "fido:b266977372f2d5704d00dd07b29ea49898ebf70e" meta-oe = "master:a8b76a264155f4b9f6ba1bebe3ac87640a6f35ed" meta-96boards = "master:4f43c70d636d2b3ab5d20e2cdded0df353323c88" NOTE: Preparing RunQueue NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks WARNING: Failed to fetch URL git:// sourceware.org/git/glibc.git;branch=release/2.21/master, attempting MIRRORS if available WARNING: QA Issue: linux-hikey: Files/directories were installed but not shipped /lib/firmware/sb16 /lib/firmware/sb16/alaw_main.csp /lib/firmware/sb16/ima_adpcm_playback.csp /lib/firmware/sb16/ima_adpcm_init.csp /lib/firmware/sb16/mulaw_main.csp /lib/firmware/sb16/ima_adpcm_capture.csp [installed-vs-shipped] NOTE: Tasks Summary: Attempted 407 tasks of which 0 didn't need to be rerun and all succeeded. BR, Will

9 years, 1 month

SMMU

by Stefan Johansson

Hello, In the Hi6220 function specification there is a base address for "SMMU_S" @0xF421_0000. However, there seems to be only 0x0 at these addresses. Is there some function to turn on SMMU ? Power ? Clocks ? Is it part of the media subsystem ? Any documentation released ? Thank you, Stefan

9 years, 1 month

eFUSE ?

by Stefan Johansson

Hello, The eFUSE decription in "Hi6220V100_Multi-Mode_Application_Processor_Function_Description.pdf" Chapter 1.6.1 and 1.6.2 is difficult to understand. Are there any function on the platform that can be used as a "consumer unit switch" i.e. lock boot-code or similar ? Do you know any memory that can be programmed once, i.e. store keys etc ? Thanks, Stefan

9 years, 1 month

Re: [Dev] How to flash a binary-file

by Haojian Zhuang

On Thu, 2015-06-04 at 14:26 +0000, Stefan Johansson wrote: > Many thanks again! > > One last question: > Do you know why the bl33 is loaded to 0x3500_0000 ? > Is the DRAM 0x0000_0000 - 0x34FF_FFFF not free at boot ? > Don't touch the memory address after 0x3500_0000. The memory address space is reserved for UEFI & OPTEE. [0x05E0_0000 - 0x05EF_FFFF] is reserved for MCU firmware. The rest memory address space is free. Regards Haojian

9 years, 1 month

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Dev June 2015