benhaz1024/raspbian-tee

Raspbian with OP-TEE support.

raspbian-tee's Issues

Update the version of raspbian and op-tee

Hello,

I practice op-tee recently, and your project is really helpful to me.
However, it seems the version of the raspbian and op-tee is about six months ago.
How can I update these components?
Can I just download the newer version, and do the same steps to build them?
Or I need to modify some files, such as Makefile or patch.

Your advices will be greatly appreciated. Thanks.

Where can I see the allocated memory size

Adding new example

@benhaz1024
Hi,
I created a new example code, I have put the .ta under / lib / optee_armtz and the executable under / bin but when I run the program I get:

optee_example_my_ta_test: TEEC_Opensession failed with code 0xffff3024 origin 0x3

Is there a solution or am I missing something?

Thank you so much!

config.txt needs change

add
kernel=u-boot.bin

No u-boot.bin in out/boot/

might want a cp in Makefile

cannot find -lteec file during make

Hi @benhaz1024

Wondering if there's any changes need to be made on the Makefile if my toolchains dir is inside the raspbian-tee dir. When running make, the error arm-none-linux-gnueabihf/bin/ld: cannot find -lteec collect2: error: ld returned 1 exit status still persists.
If i run gcc -lteec --verbose on my local bins, it still outputs the same error /usr/bin/ld: cannot find -ltee
For context, Im running on Ubuntu 20.04.3 LTS for my Rpi3B+

boot problem

hello @benhaz1024,

I'm trying to follow up on your work.
But my target is not booting.
I'm new, so I don't know many things. So even if you give me a little advice, I'll appreciate it.

Below is my development environment and my details.
Did I do anything wrong?

Host OS : ubuntu 16.04
Cross Build Toolchain
 - gcc-linaro-7.4.1-2019.02-x86_64_aarch64-linux-gnu.tar.xz
 - gcc-linaro-7.4.1-2019.02-x86_64_arm-linux-gnueabihf.tar.xz
Hardware : Raspberry pi3 B+
Raspbian : 2019-09-26-raspbian-buster-lite.img
MicroSD : 8GB

1. Flasing Raspbian into MicroSD 
   $ sudo dd bs=4M if=2019-09-26-raspbian-buster-lite.img of=/dev/sdd status=progress conv=fsync

I checked that the Razbian boots and runs normally in this state for an intermediate inspection.

2. download benhaz1024/raspbian-tee 
   $ git clone https://github.com/benhaz1024/raspbian-tee.git

3. config your cross build toolchain at config.mk
   $ vi config.mk
     export CROSS_COMPILE := /home/work/raspbian-tee/toolchains/aarch32/bin/arm-linux-gnueabihf-
    export CROSS_COMPILE_AARCH64 := /home/work/raspbian-tee/toolchains/aarch64/bin/aarch64-linux-gnu-

4. download all packages and build
   $ ./prepare-env.sh
   $ make patch
   $ make

5. confirm out folder results
   All the same output as the capture screen at https://github.com/gagachang/raspbian-tee/tree/add_xtest#build was in the out folder.

6. Install
   https://github.com/gagachang/raspbian-tee/tree/add_xtest#install

I copied the results from out to MicroSD with raspbian installed.

$ sudo mount /dev/sdd1 /media/sdd1
$ sudo cp -rf ./out/boot/* /media/sdd1

$ sudo mount /dev/sdd2 /media/sdd2
$ sudo cp -rf ./out/rootfs/* /media/sdd2

$ sudo umount /dev/sdd1
$ sudo umount /dev/sdd2

7. rpi3 Booting
   I inserted the microSD that I worked on above into my Target (rpi3 b+) and then tried booting it up, and it's not working.
   In HDMI connected to the monitor, only gradient screens are displayed, and nothing is output from uart.

I don't know what's wrong with me.
If possible, could you tell me more about your environment?
For example, raspbian version and cross copiler version.
I'd really appreciate it if you could help me.

If someone who have succeeded in this project know my problems, please advise me. (@gagachang, @mnwrhsn, @Ruide, @Hacklog24)

Thanks,

I2C/SPI not working

Although I enable I2C/SPI in the config.txt (say dtparam=i2c_arm=on and
dtparam=spi=on) I can't access from NW in Raspbian -- returns the error:

Error: Could not open file `/dev/i2c-1' or `/dev/i2c/1': No such file or directory

I have similar problem in older version of OPTEE (that uses older u-boot without device tree support, see the issue:OP-TEE/optee_os#2957) -- however this should not the be case here since we are using updated u-boot with device-tree.

Any thoughts?

rpi3 firmware already loaded device tree, redundant load in uboot

can comment out

load_fdt=fatload mmc 0:1 ${fdt_addr_r} bcm2710-rpi-3-b-plus.dtb

and
run load_fdt in mmcboot