You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, 👋
I am trying to port the cFS project on a GR740 board.
Discussion #314 has been very helpful, and I succeeded in implementing TARFS in cFS itself.
All the apps have been loaded except for cfe_assert, which I assumed is not essential since it is a test module.
Right now, I am working on the RKI project. I thought it would be nice if I had a shell prompt to use.
So in other words, I am starting a whole new porting project from scratch.
I wrote the mentioned info about TARFS to let you know I have some (very light) experience on cFS porting 😅
I looked through the BeagleBoneBlack demo and LEON3-RCC demo by @alanc98 ...
BBB version was quite easy, I just needed the BBB board, which I had.
The problem is the LEON3-RCC version and GR740 version that I have to implement.
I got the notion that cFS have to be built as an relocatable, not an executable.
This was done by setting RTEMS_DYNAMIC_LOAD TRUE.
From what I gathered, the difference between BBB version and LEON3-RCC version is static loading and dynamic loading.
I didn't know what I should try, so I went on trying the LEON3-RCC version to decide.
(I thought if I understood both versions I could port GR740 demo easily)
But unlike BBB, the repository did not have a cFS submodule.
I tried with the main branch and modified some settings, but cFS does not work in LEON3 version of RKI.
The problems I encountered:
The cross-compiler couldn't find <LINK_FLAGS> from RCC's lib directory.
Solved - I added CMAKE_EXE_LINKER_FLAGS_INIT explicitly.
RKI couldn't mount the file system.
Solved - SIS simulator didn't have enough memory allocated. I reduced RAM_DISK_0_BLOCKS.
Now, RKI stops here.
sis> run
RTEMS Kernel Image Booting
*** RTEMS Info ***
5.0.0
BSP Ticks Per Second = 100
*** End RTEMS info ***
Populating Root file system from TAR file.
Setting up filesystems.
setup_ramdisk: Registering RAM disk at /dev/rda (blocks=8192, block_size=512)
setup_ramdisk: SUCCESS - RAM disk registered
rki_init_network: Calling system_init.
Initializing network
ERR: Could not ioctl tun: Operation not permitted
greth: driver attached
**** PHY ****
Vendor: 885 Device: 11 Revision: 2
Current Operating Mode: 100 Mbit Full Duplex
Autonegotiation Time: 0ms
�������"�"ay��C��CInitializing network DONE
Destination Gateway/Mask/Hw Flags Refs Use Expire Interface
default 192.168.0.1 UGS 0 0 0 gr_eth1
127.0.0.1 127.0.0.1 UH 0 0 0 lo0
192.168.0.0 255.255.255.0 U 0 0 1 gr_eth1
192.168.0.1 UHL 1 0 1 gr_eth1
************ INTERFACE STATISTICS ************
***** lo0 *****
Address:127.0.0.1 Net mask:255.0.0.0
Flags: Up Loopback Running Multicast
Send queue limit:50 length:0 Dropped:0
***** gr_eth1 *****
Ethernet Address: 00:80:7F:22:61:79
Address:192.168.0.67 Broadcast Address:192.168.0.255 Net mask:255.255.255.0
Flags: Up Broadcast Running Simplex
Send queue limit:50 length:0 Dropped:0
Rx Interrupts:0 Rx Packets:0 Length:0 Non-octet:0
Bad CRC:0 Overrun:0 Tx Interrupts:0 Maximal Frags:1 GBIT MAC:0
Starting the FTP Server.
syslog: ftpd: FTP daemon started (1 session max)
Initializing Local Commands.
Adding Target specific commands
Running /shell-init.
1: mkdir ram
2: mkrfs /dev/rda
3: mount -t rfs /dev/rda /ram
mounted /dev/rda -> /ram
4: hello
____ ______________ ________
/ __ \/_ __/ ____/ \/ / ___/
/ /_/ / / / / __/ / /\_/ /\__ \
/ _, _/ / / / /___/ / / /___/ /
/_/ \_| /_/ /_____/_/ /_//____/
Hello RTEMS!
Create your own command here!
Starting shell....
RTEMS Shell on /dev/console. Use 'help' to list commands.
shell0 [/] # startcfedl
shell0 [/] # handle: 0x40c6e090 has unresolved externals
dlsym OK: symbol OS_BSPMain found
*** Calling OS_BSPMain() - cFS startup beginning ***
*** RTEMS Info ***
Copyright (C) 1989, 2020 RTEMS Project and contributors
rtems-5.0.0 (SPARC/w/FPU-detect/leon3)
Stack size=0
Workspace size=8388608
RTEMS_NO_CMDLINE:TRUE, command line not implemented
*** End RTEMS info ***
I don't know how I can go on. Sorry for the naive question, but I really don't.
Is there some other way I can debug? It's really hard to start debugging because of the process of loading cFS into RKI. (The error logs go missing, I think)
Or do I have to clear all settings about RTEMS in cFS, because RKI does all the settings?
I thought of this because in the cFS version of RKI-BBB demo, there are just a few source files in psp/fsw/generic-rtems.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, 👋
I am trying to port the cFS project on a GR740 board.
Discussion #314 has been very helpful, and I succeeded in implementing TARFS in cFS itself.
All the apps have been loaded except for cfe_assert, which I assumed is not essential since it is a test module.
Right now, I am working on the RKI project. I thought it would be nice if I had a shell prompt to use.
So in other words, I am starting a whole new porting project from scratch.
I wrote the mentioned info about TARFS to let you know I have some (very light) experience on cFS porting 😅
I looked through the BeagleBoneBlack demo and LEON3-RCC demo by @alanc98 ...
BBB version was quite easy, I just needed the BBB board, which I had.
The problem is the LEON3-RCC version and GR740 version that I have to implement.
I got the notion that cFS have to be built as an relocatable, not an executable.
This was done by setting
RTEMS_DYNAMIC_LOAD TRUE.From what I gathered, the difference between BBB version and LEON3-RCC version is static loading and dynamic loading.
I didn't know what I should try, so I went on trying the LEON3-RCC version to decide.
(I thought if I understood both versions I could port GR740 demo easily)
But unlike BBB, the repository did not have a cFS submodule.
I tried with the main branch and modified some settings, but cFS does not work in LEON3 version of RKI.
The problems I encountered:
The cross-compiler couldn't find
<LINK_FLAGS>from RCC's lib directory.Solved - I added
CMAKE_EXE_LINKER_FLAGS_INITexplicitly.RKI couldn't mount the file system.
Solved - SIS simulator didn't have enough memory allocated. I reduced
RAM_DISK_0_BLOCKS.Now, RKI stops here.
I don't know how I can go on. Sorry for the naive question, but I really don't.
Is there some other way I can debug? It's really hard to start debugging because of the process of loading cFS into RKI. (The error logs go missing, I think)
Or do I have to clear all settings about RTEMS in cFS, because RKI does all the settings?
I thought of this because in the cFS version of RKI-BBB demo, there are just a few source files in
psp/fsw/generic-rtems.I appriciate all help! Thank you all!
Beta Was this translation helpful? Give feedback.
All reactions