I am using the “Jetson Xavier NX module (P3668-0000) ” Board and trying for"GPIO application demonstrates" by following the below this page [Jetson Sensor Processing Engine (SPE) Developer Guide: GPIO Application (app/gpio-app.c) ]. But facing the below errors while compiling…
Set the ENV variables like below:
#sudo make bin_t19x;
Errors: (Though I am able to see the env set correctly I see the below errors)
If I remove the error line 37 from the top Makefile I am able to compile but I see different error like below.
Could someone please help me to compile for “Jetson NX” {#make bin_t19x}.
jachen
January 30, 2023, 3:09am
3
Hello,
cat spe-firmware-build.sh
#!/bin/bash
set -e
export TOP="${HOME}/Work/jetson_sdk/32.5/spe-fw/l4t-rt"
export CROSS_COMPILE="${HOME}/Tools/gcc-arm-none-eabi-4_8-2014q3/bin/arm-none-eabi-"
export FREERTOS_DIR=${TOP}/FreeRTOSV8.1.2/FreeRTOS/Source
export FREERTOS_COMMON_DIR=${TOP}/freertos-common
## To build for Jetson AGX ##
cd ${TOP}/rt-aux-cpu-demo && make -j8 bin_t19x && make docs
br
I will add something to what @jachen is suggesting…
You can run “sudo -s” prior to setting variables, and then they will exist for that sudo session. However, it is probably wrong to use sudo for this. Better to leave pristine source owned by root, but with an output and configuration location owned by the individual user, although I don’t know what direct support there is for that with that particular software.
I changed the permission for the source code to full permission. After that I am able to compile and create the spe.bin for my Jetson Xavier NX module (P3668-0000) "
But I am facing the Kernel panic error after loading this spe.bin. I followed the below kernel building guide (skipped the “Optionally, archive the installed kernel modules:” since I do not have any kernel changes)https://docs.nvidia.com/jetson/archives/r35.1/DeveloperGuide/text/SD/Kernel/KernelCustomization.html#building-the-kernel
Will post you the logs soon.
Hello Team,
I am using the “Jetson Xavier NX module (P3668-0000) ” Board and trying for"GPIO application demonstrates" by following the below this page [Jetson Sensor Processing Engine (SPE) Developer Guide: GPIO Application (app/gpio-app.c) ].
I am able to compile the spe.bin and generate the flash image for my board and this spe.bin is successfully coming up with my logs.(Rapsodo debug log Setting GPIO_APP_OUT to 1 - IRQ should trigger)
But I am seeing the kenel panic in the logs. Full log is attached with this.
Please review and correct me if i am doing any mistakeslog.txt (41.3 KB)
Kernel-Panic:
[ 4.720262] tsec 15100000.tsecb: initialized#1 ] PREEMPT SMP#1
jachen
January 31, 2023, 5:33am
7
Hello,Jetson Sensor Processing Engine (SPE) Developer Guide: GPIO Application (app/gpio-app.c) (nvidia.com) ?
In order to access a AON GPIO from the Cortex-R5 SPE/AON for Jetson NX, ENABLE_SPE_FOR_NX flag has to be set to 1 in the target_specific.mk file in the in the soc/t19x. The GPIO SCR, GPIO interrupt map and pinmux settings need to be updated as described in below steps.
Update SCR values as below in the file tegra194-mb1-bct-scr-cbb-mini-p3668.cfg:
scr.49.6 = 0x18001010; # GPIO_CC_SCR_04_0 scr.53.6 = 0x18001010; # GPIO_DD_SCR_00_0
Update gpio interrupt mapping as below in tegra194-mb1-bct-gpioint-p3668-0001-a00.cfg:
gpio-intmap.port.CC.pin.4 = 2; # GPIO CC4 to INT2 gpio-intmap.port.DD.pin.0 = 2; # GPIO DD0 to INT2
Update default pinmux configuration as below in the file tegra19x-mb1-pinmux-p3668-a01.cfg:
pinmux.0x0c302000 = 0x00000025; # touch_clk_pcc4: GPIO, pull-down, input-disable pinmux.0x0c302040 = 0x00000075; # gen2_i2c_sda_pdd0: i2c2, pull-down, input-enable
Compile device tree and flash the entire board to ensure that the SCR, gpio interrupt mapping and pinmux settings are flashed on the board.
Short GPIO pins of the 40 pin header J12 pin 15 and pin 27, this should print out “GPIO input irq triggered” message since pin 15 is configured as OUT which drives the pin 27 which is configured as INPUT and also has interrupt enabled.
After all those changes, please re-flash the whole device.
br
Yes. Followed.
Did you check my logs? I am able to bring up the spe firmware with AON enabled.
[ 4.724374] gic 2a41000.agic-controller: GIC IRQ controller registered [ 4.749906] tegra-aconnect aconnect@2a41000: Tegra ACONNECT bus registered [ 4.763023] gpio-374 (wifi-enable): hogged as output/high [ 4.763555] gpio-431 (camera-control-output-low): hogged as output/low [ 4.763965] gpio-432 (camera-control-output-low): hogged as output/low [ 4.765775] gpiochip1: registered GPIOs 335 to 503 on tegra194-gpio [ 4.767547] gpiochip2: registered GPIOs 305 to 334 on tegra194-gpio-aon [ 4.767936] CPU:0, Error: aon-noc@c600000, irq=17 [ 4.773843] CPU:0, Error:aon-noc [ 4.777257] Error Logger : 0 [ 4.780411] ErrLog0 : 0x80030000 [ 4.784008] Transaction Type : RD - Read, Incrementing [ 4.789327] Error Code : SLV [ 4.792740] Error Source : Target [ 4.796414] Error Description : Target error detected by CBB slave [ 4.802823] AXI2APB_5 bridge error: RDFIFOF - Read Response FIFO Full interrupt
jachen
January 31, 2023, 5:59am
9
Hello,
Flash the device with original BSP/SPE firmware. The device should be able to boot correctly.
You can re-compile your own kernel and boot the device with updated kernel image. Make sure it works well.
Compile the SPE firmware package, without any change. Replace the spe.bin with your own building,
If 3 is good, you can start with GPIO changes in SPE firmware.
Let us know your progress.
br
First 3 steps are ok. only with cfg file changes I am seeing this errors.
jachen
January 31, 2023, 6:12am
11
Which BSP / SPE firmware version you are using?
br
All packages are downloaded from here:
Jetson Linux 35.2.1 is a production quality release which brings support for Jetson Orin NX 16GB production module and includes Linux Kernel 5.10, an Ubuntu 20.04 based root file system, a UEFI based bootloader, and OP-TEE as Trusted Execution...
I am using ubuntu 22.04 image
Could you confirm the .cfg configuration are correct? I suspect this
jachen
January 31, 2023, 7:33am
15
o. I’ve not tried 35.2.1 yet.
I will check 35.2.1 locally, but it may take time.
br
SPE will not be available for old BSP. I have checked for 32.5 its not there.
Anyhow, We want the latest one and not interested in old one (we have this latest BSP for others). Could you try and confirm?
jachen
January 31, 2023, 9:44am
17
You can visit L4T 32.5 Archive | NVIDIA Developer https://developer.nvidia.com/embedded/L4T/r32_Release_v5.0/sources/T186/l4t_rt_aux_cpu_src.tbz2
You can just start from 32.5 SPE development and get familiar with SPE updates.
Sure, we will check 35.2 SPE functions, but it may take time.
br
jachen
February 2, 2023, 8:21am
18
Hello,Jetson Sensor Processing Engine (SPE) Developer Guide: Welcome (nvidia.com)
br
Hi Jachen,
Thanks for the conformation. Is the below version is tested for Xavier NX platform??
You can take a look at Jetson Sensor Processing Engine (SPE) Developer Guide: Welcome (nvidia.com)
Regards,
jachen
February 10, 2023, 2:48am
21
Hello,Jetson Sensor Processing Engine (SPE) Developer Guide: GPIO Application (app/gpio-app.c) (nvidia.com) contains the Xavier NX information, and that means the corresponding package is verified in Xavier NX platform.
br
OK. I will try 32.5 SPE development.
