6.0.10 Hello World Graph

stefan65 · March 26, 2025, 8:03am

Please provide the following info (tick the boxes after creating this topic):
Software Version
DRIVE OS 6.0.10.0
DRIVE OS 6.0.8.1
DRIVE OS 6.0.6
DRIVE OS 6.0.5
DRIVE OS 6.0.4 (rev. 1)
DRIVE OS 6.0.4 SDK
other

Target Operating System
Linux
QNX
other

Hardware Platform
DRIVE AGX Orin Developer Kit (940-63710-0010-300)
DRIVE AGX Orin Developer Kit (940-63710-0010-200)
DRIVE AGX Orin Developer Kit (940-63710-0010-100)
DRIVE AGX Orin Developer Kit (940-63710-0010-D00)
DRIVE AGX Orin Developer Kit (940-63710-0010-C00)
DRIVE AGX Orin Developer Kit (not sure its number)
other

SDK Manager Version
2.1.0
other

Host Machine Version
native Ubuntu Linux 20.04 Host installed with SDK Manager
native Ubuntu Linux 20.04 Host installed with DRIVE OS Docker Containers
native Ubuntu Linux 18.04 Host installed with DRIVE OS Docker Containers
other

Issue Description
Getting Hello World on 6.0.10 using Compute Graph Framework Presentation.

/usr/local/driveworks/tools/descriptionScheduleYamlGenerator/descriptionScheduleYamlGenerator.py --app /gw_demo/src/sys/src/cgf/app/graphs/appPebble/DWCGFPebble.app.json --output /gw_demo/src/sys/src/cgf/app/graphs/appPebble/DWCGFPebble__standardSchedule.yaml

{
“name”: “DWCGFPebbleApp”,
“logSpec”: “file/rfc5424:{{logpath}}/{{appname}}.log”,
“parameters”: {},
“requiredSensors”: “../appCommon/DWCGFImagePipe.required-sensors.json”,
“sensorMappingLookups”: [
“../sensor_mappings”
],
“subcomponents”: {
“dwcgfPebbleGraphlet”: {
“componentType”: “./DWCGFPebble.graphlet.json”,
“parameters”: {}
}
},
“connections”: ,
“states”: {
“STANDARD”: {
“stmScheduleKey”: “standardSchedule”,
“default”: true
}
},
“stmSchedules”: {
“standardSchedule”: {
“wcet” : “./DWCGFPebble_wcet.yaml”,
“hyperepochs”: {
“pebbleappHyperepoch”: {
“period”: 10000000,
“epochs”: {
“pebbleappEpoch”: {
“period”: 10000000,
“frames”: 1,
“passes”: [
[
“dwcgfPebbleGraphlet.Hello”
]
]
}
},
“resources”: {
“machine0.CPU0”:
}
}
}
}
},
“processes”: {
“schedule_manager”: {
“runOn”: “machine0”,
“executable”: “ScheduleManager”,
“argv”: {
“–enableScheduleSwitching”: “false”,
“–scheduleManagerHostIP”: “127.0.0.1”,
“–scheduleManagerHostPort”: “40100”
}
},
“stm_master”: {
“runOn”: “machine0”,
“executable”: “stm_master”,
“logSpec”: “file:{{logpath}}/{{appname}}.log”,
“argv”: {
“–allow-unregistered-runnables”: true,
“–timeout-us”: “60000000”,
“–soc”: “TegraA”,
“-v”: true,
“-m”: true
}
},
“pebble_process0”: {
“runOn”: “machine0”,
“executable”: “LoaderLite”,
“subcomponents”: [
“dwcgfPebbleGraphlet.Hello”,
“dwcgfPebbleGraphlet.World”
]
}
},
“extraInfo”: “../appCommon/DWCGFImagePipeExtraInfo.json”
}

Output

Input Description file path: /gw_demo/src/sys/src/cgf/app/graphs/appPebble/DWCGFPebble.app.json

Analysis…
Traceback (most recent call last):
File “/usr/local/driveworks/tools/descriptionScheduleYamlGenerator/descriptionScheduleYamlGenerator.py”, line 3260, in
main()
File “/usr/local/driveworks/tools/descriptionScheduleYamlGenerator/descriptionScheduleYamlGenerator.py”, line 3188, in main
systemDescription = SystemDescription(appFile)
File “/usr/local/driveworks/tools/descriptionScheduleYamlGenerator/descriptionScheduleYamlGenerator.py”, line 3123, in init
self.schedules = [
File “/usr/local/driveworks/tools/descriptionScheduleYamlGenerator/descriptionScheduleYamlGenerator.py”, line 3124, in
ScheduleDescription(self.baseDir, stmSchedule, stmScheduleKey, identifier, stmScheduleKey == defaultStmScheduleKey, self)
File “/usr/local/driveworks/tools/descriptionScheduleYamlGenerator/descriptionScheduleYamlGenerator.py”, line 1616, in init
self.clients = self.parseClients(clientInfo, resourcesConfig[“clientResources”], scheduleJson[HYPEREPOCHS])
File “/usr/local/driveworks/tools/descriptionScheduleYamlGenerator/descriptionScheduleYamlGenerator.py”, line 1926, in parseClients
if self.getSubComponent(subId):
File “/usr/local/driveworks/tools/descriptionScheduleYamlGenerator/descriptionScheduleYamlGenerator.py”, line 2755, in getSubComponent
return self.subcomponents[componentIdList[0]].getSubComponent(componentIdList[1:])
File “/usr/local/driveworks/tools/descriptionScheduleYamlGenerator/descriptionScheduleYamlGenerator.py”, line 3030, in getSubComponent
raise ValueError('Can not find subComponent: ', componentIdList, ’ in ', self.id)
ValueError: ('Can not find subComponent: ', [‘Hello’], ’ in ', ‘dwcgfPebbleGraphlet’)

Am I missing any step ?

stefan65 · March 26, 2025, 8:49am

{
    "comment": "Hello Node",
    "library": "libpebble_node.so",
    "name": "dw::framework::HelloNode",
    "inputPorts": {},
    "outputPorts": {},
    "parameters": {},
    "passes": [
        {
            "name": "SETUP",
            "processorTypes": [
                "CPU"
            ]
        },
        {
            "name": "PROCESS",
            "processorTypes": [
                "CPU"
            ]
        },
        {
            "name": "TEARDOWN",
            "processorTypes": [
                "CPU"
            ]
        }
    ]
}

{
    "comment": "World node",
    "library": "libpebble_node.so",
    "name": "dw::framework::WorldNode",
    "inputPorts": {},
    "outputPorts": {},
    "parameters": {},
    "passes": [
        {
            "name": "SETUP",
            "processorTypes": [
                "CPU"
            ]
        },
        {
            "name": "PROCESS",
            "processorTypes": [
                "CPU"
            ]
        },
        {
            "name": "TEARDOWN",
            "processorTypes": [
                "CPU"
            ]
        }
    ]
}

Graphlet

{
    "name": "DWCGPebbleApp",
    "inputPorts": {},
    "outputPorts": {},
    "parameters": {},
    "subcomponents": {
        "dw::framework::HelloNode": {
            "componentType": "/gw_demo/src/sys/src/cgf/app/graphs/nodes/hello/Hello.node.json"
        },
        "dw::framework::WorldNode": {
            "componentType": "/gw_demo/src/sys/src/cgf/app/graphs/nodes/world/World.node.json"
        }
    },
    "connections": []
}

Code Successfully Generated…

Below is app jason taken and modified from 6.0.6

{
    "name": "DWCGFPebbleApp",
    "logSpec": "file/rfc5424:{{logpath}}/{{appname}}.log",
    "parameters": {},
    "requiredSensors": "../appCommon/DWCGFImagePipe.required-sensors.json",
    "sensorMappingLookups": [
        "../sensor_mappings"
    ],
    "subcomponents": {
        "dwcgfPebbleGraphlet": {
            "componentType": "./DWCGFPebble.graphlet.json",
            "parameters": {}
        }
    },
    "connections": [],
    "states": {
        "STANDARD": {
            "stmScheduleKey": "standardSchedule",
            "default": true
        }
    },
    "stmSchedules": {
        "standardSchedule": {
            "wcet" : "./DWCGFPebble_wcet.yaml",
            "hyperepochs": {
                "pebbleappHyperepoch": {
                    "period": 10000000,
                    "epochs": {
                        "pebbleappEpoch": {
                            "period": 10000000,
                            "frames": 1,
                            "passes": [
                                [
                                    "dwcgfPebbleGraphlet.Hello"
                                ]
                            ]
                        }
                    },
                    "resources": {
                        "machine0.CPU0": []
                    }
                }
            }
        }
    },
    "processes": {
        "schedule_manager": {
            "runOn": "machine0",
            "executable": "ScheduleManager",
            "argv": {
                "--enableScheduleSwitching": "false",
                "--scheduleManagerHostIP": "127.0.0.1",
                "--scheduleManagerHostPort": "40100"
            }
        },
        "stm_master": {
            "runOn": "machine0",
            "executable": "stm_master",
            "logSpec": "file:{{logpath}}/{{appname}}.log",
            "argv": {
                "--allow-unregistered-runnables": true,
                "--timeout-us": "60000000",
                "--soc": "TegraA",
                "-v": true,
                "-m": true
            }
        },
        "pebble_process0": {
            "runOn": "machine0",
            "executable": "LoaderLite",
            "subcomponents": [
                "dwcgfPebbleGraphlet.Hello",
                "dwcgfPebbleGraphlet.World"
            ]
        }
    },
    "extraInfo": "../appCommon/DWCGFImagePipeExtraInfo.json"
}

/usr/local/driveworks/tools/descriptionScheduleYamlGenerator/descriptionScheduleYamlGenerator.py

Input Description file path: /gw_demo/src/sys/src/cgf/app/graphs/appPebble/DWCGFPebble.app.json
=============================
Analysis...
Traceback (most recent call last):
  File "/usr/local/driveworks/tools/descriptionScheduleYamlGenerator/descriptionScheduleYamlGenerator.py", line 3260, in <module>
    main()
  File "/usr/local/driveworks/tools/descriptionScheduleYamlGenerator/descriptionScheduleYamlGenerator.py", line 3188, in main
    systemDescription = SystemDescription(appFile)
  File "/usr/local/driveworks/tools/descriptionScheduleYamlGenerator/descriptionScheduleYamlGenerator.py", line 3123, in __init__
    self.schedules = [
  File "/usr/local/driveworks/tools/descriptionScheduleYamlGenerator/descriptionScheduleYamlGenerator.py", line 3124, in <listcomp>
    ScheduleDescription(self.baseDir, stmSchedule, stmScheduleKey, identifier, stmScheduleKey == defaultStmScheduleKey, self)
  File "/usr/local/driveworks/tools/descriptionScheduleYamlGenerator/descriptionScheduleYamlGenerator.py", line 1616, in __init__
    self.clients = self.parseClients(clientInfo, resourcesConfig["clientResources"], scheduleJson[HYPEREPOCHS])
  File "/usr/local/driveworks/tools/descriptionScheduleYamlGenerator/descriptionScheduleYamlGenerator.py", line 1926, in parseClients
    if self.getSubComponent(subId):
  File "/usr/local/driveworks/tools/descriptionScheduleYamlGenerator/descriptionScheduleYamlGenerator.py", line 2755, in getSubComponent
    return self.subcomponents[componentIdList[0]].getSubComponent(componentIdList[1:])
  File "/usr/local/driveworks/tools/descriptionScheduleYamlGenerator/descriptionScheduleYamlGenerator.py", line 3030, in getSubComponent
    raise ValueError('Can not find subComponent: ', componentIdList, ' in ', self.id)
ValueError: ('Can not find subComponent: ', ['Hello'], ' in ', 'dwcgfPebbleGraphlet')

stefan65 · March 26, 2025, 9:07am

Success after removing
“dw::framework::HelloNode”: from Node JSON

stefan65 · March 26, 2025, 9:55am

HelloWorld_Launcher.log (17.4 KB)

Once hello world is launched.. stm_master gets terminated..

SivaRamaKrishnaNV · March 26, 2025, 10:14am

Could you try modify the app json as reference from 6.0.10.

Also, can you share Logfolder and used command.

stefan65 · March 26, 2025, 10:21am

sudo /usr/local/driveworks/bin/launcher --binPath=/usr/local/driveworks/bin --spec=$HOME/data/pebble_vcu/target/aarch64/install/graphs/pebble_app/appPebble/DWCGFPebble.app.json --logPath=$HOME/fota/LogFolder/pebble_app/Pebble --path=/usr/local/driveworks/bin --datapath=$HOME/data/pebble_vcu/target/aarch64/install/data/pebble_app --dwdatapath=$HOME/data/pebble_vcu/target/aarch64/install/data --schedule=$HOME/data/pebble_vcu/target/aarch64/install/bin/pebble_app/DWCGFPebble__standardSchedule.stm --start_timestamp=0 --loglevel=DW_LOG_VERBOSE --fullscreen=0 --winSizeW=1920 --winSizeH=1200 --virtual=0 --disableStmControlLogger=1 --gdb_debug=0
LogFolder.tar.gz (6.5 KB)

Which app JSON r u referring to from 6.0.10 ?

stefan65 · March 26, 2025, 10:28am

./apps/cgf_demo/CGFDemo.app.json
This one from sample.. (Sure will give a try).

stefan65 · March 26, 2025, 10:56am

Took Demo.app.json(modified it). Same result.

`{
    "name": "DWCGFPebbleApp",
    "logSpec": "file/rfc5424:{{logpath}}/{{appname}}.log",
    "parameters": {
    },
    "requiredSensors": "../appCommon/DWCGFImagePipe.required-sensors.json",
    "subcomponents": {
        "dwcgfPebbleGraphlet": {
            "componentType": "./DWCGFPebble.graphlet.json",
            "parameters": {}
        }
    },
    "connections": [],
    "states": {
        "SLOW": {
            "stmScheduleKey": "slowSchedule"
        },
        "STANDARD": {
            "stmScheduleKey": "standardSchedule",
            "default": true
        }
    },
    "stmSchedules": {
        "slowSchedule": {
            "wcet": "./DWCGFPebble_wcet.yaml",
            "hyperepochs": {
                "pebbleappHyperepoch": {
                    "period": 330000000,
                    "epochs": {
                        "pebbleappEpoch": {
                            "period": 330000000,
                            "frames": 1,
                            "passes": [
                                [
                                    "dwcgfPebbleGraphlet.HelloNode",
                                    "dwcgfPebbleGraphlet.WorldNode"
                                ]
                            ]
                        }
                    },
                    "resources": {
                        "machine0.CPU0": [],
                        "machine0.CPU1": [],
                        "machine0.CPU2": [],
                        "machine0.CPU3": []                    
                    }
                }
            }
        },
        "standardSchedule": {
            "wcet": "./DWCGFPebble_wcet.yaml",
            "hyperepochs": {
                "pebbleappHyperepoch": {
                    "period": 33000000,
                    "epochs": {
                        "pebbleappEpoch": {
                            "period": 33000000,
                            "frames": 1,
                            "passes": [
                                [
                                    "dwcgfPebbleGraphlet.HelloNode",
                                    "dwcgfPebbleGraphlet.WorldNode"
                                ]
                            ]
                        }
                    },
                    "resources": {
                        "machine0.CPU0": [],
                        "machine0.CPU1": [],
                        "machine0.CPU2": [],
                        "machine0.CPU3": []
                    }
                }
            }
        }
    },
    "processes": {
        "pebble_process0": {
            "runOn": "machine0",
            "executable": "LoaderLite",
            "subcomponents": [
		        "dwcgfPebbleGraphlet.HelloNode",
		        "dwcgfPebbleGraphlet.WorldNode"
            ]
        },
        "schedule_manager": {
            "executable": "ScheduleManager",
            "argv": {
                "--enableScheduleSwitching": "true",
                "--scheduleManagerHostIP": "127.0.0.1",
                "--scheduleManagerHostPort": "4010",
                "--scheduleManagerNumLoaderClients": "5",
                "--scheduleManagerNumSSMClients": "5"
            },
            "runOn": "machine0"
        },
        "stm_master": {
            "executable": "stm_master",
            "argv": {
                "--timeout-us": "80000000",
                "--soc": "TegraA",
                "-m": true
            },
            "runOn": "machine0"
        }
    },
    "extraInfo": "../appCommon/DWCGFImagePipeExtraInfo.json"
}`

stefan65 · March 30, 2025, 3:53pm

When invoking stm_master terminates ???

/usr/local/driveworks/bin/stm_master --schedule=/home/pebble-admin/data/pebble_vcu/target/aarch64/install/bin/pebble_app/DWCGFPebble__standardSchedule.stm --soc=TegraA --timeout-us=80000000 -m --schedule-manager-name=CGF-ScheduleManager --num-input-schedule=2
[STM][INFO] Log Name               : NULL
[STM][INFO] Master Forked Log Path : .
[STM][INFO] SchedArray             : /home/pebble-admin/data/pebble_vcu/target/aarch64/install/bin/pebble_app/DWCGFPebble__standardSchedule.stm
[STM][INFO] Sched Manager Name     : CGF-ScheduleManager
[STM][INFO] Num Input Schedule     : 2
[STM][INFO] SoC                    : TegraA
[STM][INFO] Core                   : -1
[STM][INFO] CPU Affinity           : true
[STM][INFO] Verbose                : false
[STM][INFO] Hyper Epoch Max        : -1
[STM][INFO] Parse Debug            : false
[STM][INFO] Timeout (US)           : 80000000
[STM][INFO] Log Frequency          : 30
[STM][INFO] No Skip On Overrun     : 1
[STM][INFO] Thread Priority        : 1
[STM][INFO] Primary Xavier IP      : NULL
[STM][INFO] Interface              : eth0
[STM][INFO] Socket Timeout US      : 5000000
[STM][INFO] Start Socket Timeout   : 600
[STM][INFO] Suffix Timestamp       : true
[STM][INFO] Blocking Log Send      : false
[STM][INFO] MemLock                : false
[STM][INFO] Base Port              : 8000
[STM][INFO] Discriminator          : -1
[STM][INFO] cuDLA standalone       : false
[STM][INFO] Disable Engine Prefer  : false
[STM][INFO] Disable Engine Fences  : false
[STM][INFO] Allow Unregistered runnables : false
[STM][INFO] Round Robin Skip Count : 0
[STM][INFO] Cond Var Fences      : 1
[STM ERROR]:[src/dwstm/runtime/src/master/master.c][stmMasterInitScheduleList] [167]: Found 1 schedule out of 2.
src/dwstm/runtime/src/master/master.c:168 assertion failure, errno=0 (Success)
Aborted

stefan65 · March 30, 2025, 3:59pm

after changing --num-input-schedule=1

ebble-admin@tegra-ubuntu:~$ /usr/local/driveworks/bin/stm_master --schedule=/home/pebble-admin/data/pebble_vcu/target/aarch64/install/bin/pebble_app/DWCGFPebble__standardSchedule.stm --soc=TegraA --timeout-us=80000000 -m --schedule-manager-name=CGF-ScheduleManager --num-input-schedule=1 -v
[STM][INFO] Log Name               : NULL
[STM][INFO] Master Forked Log Path : .
[STM][INFO] SchedArray             : /home/pebble-admin/data/pebble_vcu/target/aarch64/install/bin/pebble_app/DWCGFPebble__standardSchedule.stm
[STM][INFO] Sched Manager Name     : CGF-ScheduleManager
[STM][INFO] Num Input Schedule     : 1
[STM][INFO] SoC                    : TegraA
[STM][INFO] Core                   : -1
[STM][INFO] CPU Affinity           : true
[STM][INFO] Verbose                : true
[STM][INFO] Hyper Epoch Max        : -1
[STM][INFO] Parse Debug            : false
[STM][INFO] Timeout (US)           : 80000000
[STM][INFO] Log Frequency          : 30
[STM][INFO] No Skip On Overrun     : 1
[STM][INFO] Thread Priority        : 1
[STM][INFO] Primary Xavier IP      : NULL
[STM][INFO] Interface              : eth0
[STM][INFO] Socket Timeout US      : 5000000
[STM][INFO] Start Socket Timeout   : 600
[STM][INFO] Suffix Timestamp       : true
[STM][INFO] Blocking Log Send      : false
[STM][INFO] MemLock                : false
[STM][INFO] Base Port              : 8000
[STM][INFO] Discriminator          : -1
[STM][INFO] cuDLA standalone       : false
[STM][INFO] Disable Engine Prefer  : false
[STM][INFO] Disable Engine Fences  : false
[STM][INFO] Allow Unregistered runnables : false
[STM][INFO] Round Robin Skip Count : 0
[STM][INFO] Cond Var Fences      : 1
[STM WARNING]:[src/dwstm/runtime/src/core/stdout.c][logSetVerbose] [30]: Verbose mode has been enabled for STM. ***Note that this mode affects STM latency guarantees, and is meant for use only in debugging. Do not use '-v' for performance testing.
[STM][WARN] Verbose mode has been enabled for STM. ***Note that this mode affects STM latency guarantees, and is meant for use only in debugging. Do not use '-v' for performance testing.
[STM INFO]:[src/dwstm/runtime/src/master/master.c][stmMasterInitScheduleList] Input Schedule: /home/pebble-admin/data/pebble_vcu/target/aarch64/install/bin/pebble_app/DWCGFPebble__standardSchedule.stm
[STM INFO]:[src/dwstm/runtime/src/master/master.c][stmMasterInitScheduleList] Following 1 schedules provided.
[STM INFO]:[src/dwstm/runtime/src/master/master.c][stmMasterInitScheduleList] 	 Schedule0 : /home/pebble-admin/data/pebble_vcu/target/aarch64/install/bin/pebble_app/DWCGFPebble__standardSchedule.stm.
[STM INFO]:[src/dwstm/runtime/src/master/master.c][stmMasterInitClientPerSchedule] Schedule ID : 0
[STM INFO]:[src/dwstm/runtime/src/master/master.c][stmMasterInitClientPerSchedule] 	Client name: pebble_process0
[STM INFO]:[src/dwstm/runtime/src/master/master.c][stmMasterInitClientPerSchedule] 	Client soc: TegraA
[STM INFO]:[src/dwstm/runtime/src/master/master.c][stmMasterInitClientPerSchedule] 	Client name: framesync_TegraA_pebbleappHyperepoch_pebbleappEpoch
[STM INFO]:[src/dwstm/runtime/src/master/master.c][stmMasterInitClientPerSchedule] 	Client soc: TegraA
terminate called after throwing an instance of 'nvstm::ErrnoError'
  what():  Could not open ShmDescriptor; errno: 17 (File exists)

stefan65 · March 31, 2025, 2:57am

Ran stm_master

udo /usr/local/driveworks/bin/stm_master --schedule=/home/pebble-admin/data/pebble_vcu/aarch64/install/bin/pebble_app/DWCGFPebble__standardSchedule.stm --soc=TegraA --timeout-us=80000000 -m --schedule-manager-name=CGF-ScheduleManager --num-input-schedule=1
[sudo] password for pebble-admin: 
[STM][INFO] Log Name               : NULL
[STM][INFO] Master Forked Log Path : .
[STM][INFO] SchedArray             : /home/pebble-admin/data/pebble_vcu/aarch64/install/bin/pebble_app/DWCGFPebble__standardSchedule.stm
[STM][INFO] Sched Manager Name     : CGF-ScheduleManager
[STM][INFO] Num Input Schedule     : 1
[STM][INFO] SoC                    : TegraA
[STM][INFO] Core                   : -1
[STM][INFO] CPU Affinity           : true
[STM][INFO] Verbose                : false
[STM][INFO] Hyper Epoch Max        : -1
[STM][INFO] Parse Debug            : false
[STM][INFO] Timeout (US)           : 80000000
[STM][INFO] Log Frequency          : 30
[STM][INFO] No Skip On Overrun     : 1
[STM][INFO] Thread Priority        : 1
[STM][INFO] Primary Xavier IP      : NULL
[STM][INFO] Interface              : eth0
[STM][INFO] Socket Timeout US      : 5000000
[STM][INFO] Start Socket Timeout   : 600
[STM][INFO] Suffix Timestamp       : true
[STM][INFO] Blocking Log Send      : false
[STM][INFO] MemLock                : false
[STM][INFO] Base Port              : 8000
[STM][INFO] Discriminator          : -1
[STM][INFO] cuDLA standalone       : false
[STM][INFO] Disable Engine Prefer  : false
[STM][INFO] Disable Engine Fences  : false
[STM][INFO] Allow Unregistered runnables : false
[STM][INFO] Round Robin Skip Count : 0
[STM][INFO] Cond Var Fences      : 1
[STM] Start schedule manager now.
[STM] Waiting for schedule manager : CGF-ScheduleManager ...
[STM] Registered CGF-ScheduleManager with pid 156487
[STM] Schedule manager starting state logic.
[STM] Start clients now.
[STM] Master waiting for all clients to start...
[STM] Waiting for client pebble_process0...
[STM] Starting state machine thread for STM
[STM] Registered client pebble_process0
[STM] Waiting for client framesync_TegraA_pebbleappHyperepoch_pebbleappEpoch...
[STM] Registered client framesync_TegraA_pebbleappHyperepoch_pebbleappEpoch
[STM] All clients running...
[STM] Exporting schedule to clients...
[STM] Sending schedule id for schedule '/home/pebble-admin/data/pebble_vcu/aarch64/install/bin/pebble_app/DWCGFPebble__standardSchedule.stm' to clients

Run ScheduleManager

sudo /usr/local/driveworks/bin/ScheduleManager --loglevel=DW_LOG_VERBOSE --binPath=/usr/local/driveworks/bin --schedule=/home/pebble-admin/data/pebble_vcu/target/aarch64/install/bin/pebble_app/DWCGFPebble__standardSchedule.stm --spec=/home/pebble-admin/data/pebble_vcu/aarch64/install/graphs/pebble_app/appPebble/DWCGFPebble.app.json --enableScheduleSwitching=true --scheduleManagerHostIP=127.0.0.1 --scheduleManagerHostPort=4010 --scheduleManagerNumLoaderClients=5 --scheduleManagerNumSSMClients=5 --logspec=file/rfc5424.user.schedule_manager:/home/pebble-admin/fota/LogFolder/pebble_app/Pebble/schedule_manager.log --schedule-manager-name=CGF-ScheduleManager --sensorSyncEnabled=0 --disablePrioInit=0 --enablePrioSched=1
[sudo] password for pebble-admin: 
Sorry, try again.
[sudo] password for pebble-admin: 
ProgramArguments: Missing argument  'logPath' requested
ProgramArguments: Missing argument  'shadow' requested
[STM] Waiting for STM master to start...
[STM] Master launched
[STM] Connected to STM master

Running LoaderLite established connection with stm_master but fails without much info

root@tegra-ubuntu:/usr/local/driveworks/targets/aarch64-Linux# /usr/local/driveworks/bin/LoaderLite --swcid=pebble_process0 --libname=RuntimeGraphlet --modulename=pebble_process0 --binPath=/usr/local/driveworks/bin --datapath=/home/pebble-admin/data/pebble_vcu/aarch64/install/data/pebble_app --dwdatapath=/home/pebble-admin/data/pebble_vcu/aarch64/install/data --logPath=/home/pebble-admin/fota/LogFolder/pebble_app/Pebble --loglevel=DW_LOG_VERBOSE --path=/usr/local/driveworks/bin --schedule=/home/pebble-admin/data/pebble_vcu/aarch64/install/bin/pebble_app/DWCGFPebble__standardSchedule.stm --spec=/home/pebble-admin/data/pebble_vcu/aarch64/install/graphs/pebble_app/appPebble/DWCGFPebble.app.json --machine_id=machine0 --logspec=file/rfc5424.user.pebble_process0:/home/pebble-admin/fota/LogFolder/pebble_app/Pebble/pebble_process0.log


--------------------------------------------------------------
WARNING: Using default Logger, most probably DriveWorks
         library was linked more than once.
--------------------------------------------------------------

DefaultLogger: [01-05-2024 09:49:04] TopExecutor: set TopExecutor to cpuset /sys/fs/cgroup/cpuset/rr2init/tasks
DefaultLogger: [01-05-2024 09:49:04] Failed to open cpuset /sys/fs/cgroup/cpuset/rr2init/tasks, errno: No such file or directory (2)
DefaultLogger: [01-05-2024 09:49:04] Failed to set TopExecutor to RR2 init cpuset: /sys/fs/cgroup/cpuset/rr2init/tasks
[STM] Waiting for STM master to start...
[STM] Master launched
[STM][INFO] Performing Client Global Shm Init ...
[STM][WARN] Verbose mode has been enabled for STM. ***Note that this mode affects STM latency guarantees, and is meant for use only in debugging. Do not use '-v' for performance testing.
[STM][INFO] Connecting to STM master...
terminate called without an active exception

Any insight into next step to root cause will be a great help. ?

stefan65 · April 1, 2025, 6:16am

Launch ScheduleManager

/usr/local/driveworks/bin/ScheduleManager --loglevel=DW_LOG_VERBOSE --binPath=/usr/local/driveworks/bin --schedule=/home/pebble-admin/data/pebble_vcu/aarch64/install/bin/pebble_app/DWCGFPebble__standardSchedule.stm --spec=/home/pebble-admin/data/pebble_vcu/aarch64/install/graphs/pebble_app/appPebble/DWCGFPebble.app.json --enableScheduleSwitching=true --scheduleManagerHostIP=127.0.0.1 --scheduleManagerHostPort=4010 --scheduleManagerNumLoaderClients=5 --scheduleManagerNumSSMClients=5 --logspec=file/rfc5424.user.schedule_manager:/home/pebble-admin/fota/LogFolder/pebble_app/Pebble/schedule_manager.log --schedule-manager-name=CGF-ScheduleManager --sensorSyncEnabled=0 --disablePrioInit=0 --enablePrioSched=1
ProgramArguments: Missing argument  'logPath' requested
ProgramArguments: Missing argument  'shadow' requested

[STM] Master launched
[STM] Connected to STM master

Launch stm_master

/usr/local/driveworks/bin/stm_master --schedule=/home/pebble-admin/data/pebble_vcu/aarch64/install/bin/pebble_app/DWCGFPebble__standardSchedule.stm --soc=TegraA --timeout-us=80000000 -m --schedule-manager-name=CGF-ScheduleManager --num-input-schedule=1
....STM] Registered client pebble_process0
[STM] Waiting for client framesync_TegraA_pebbleappHyperepoch_pebbleappEpoch...
[STM] Registered client framesync_TegraA_pebbleappHyperepoch_pebbleappEpoch
[STM] All clients running...
[STM] Exporting schedule to clients...
[STM] Sending schedule id for schedule '/home/pebble-admin/data/pebble_vcu/aarch64/install/bin/pebble_app/DWCGFPebble__standardSchedule.stm' to clients
[STM] Initializing sync objects for schedule /home/pebble-admin/data/pebble_vcu/aarch64/install/bin/pebble_app/DWCGFPebble__standardSchedule.stm
[STM] Initializing commands for schedule /home/pebble-admin/data/pebble_vcu/aarch64/install/bin/pebble_app/DWCGFPebble__standardSchedule.stm
[STM] Done exporting schedule to clients
[STM] STM clients starting scheduling loop.
[STM] Waiting for specified number of epochs to complete or any STM client to terminate.

Launch Process…

usr/local/driveworks/bin/LoaderLite --swcid=pebble_process0 --libname=RuntimeGraphlet --modulename=pebble_process0 --app_parameter= --binPath=/usr/local/driveworks/bin --datapath=/home/pebble-admin/data/pebble_vcu/aarch64/install/data/pebble_app --dwdatapath=/home/pebble-admin/data/pebble_vcu/aarch64/install/data --logPath=/home/pebble-admin/fota/LogFolder/pebble_app/Pebble --loglevel=DW_LOG_VERBOSE --path=/usr/local/driveworks/bin --schedule=/home/pebble-admin/data/pebble_vcu/aarch64/install/bin/pebble_app/DWCGFPebble__standardSchedule.stm --spec=/home/pebble-admin/data/pebble_vcu/aarch64/install/graphs/pebble_app/appPebble/DWCGFPebble.app.json --machine_id=machine0 --logspec=file/rfc5424.user.pebble_process0:/home/pebble-admin/fota/LogFolder/pebble_app/Pebble/pebble_process0.log


DefaultLogger: [02-05-2024 13:03:14] TopExecutor: set TopExecutor to cpuset /sys/fs/cgroup/cpuset/rr2init/tasks
DefaultLogger: [02-05-2024 13:03:14] Failed to open cpuset /sys/fs/cgroup/cpuset/rr2init/tasks, errno: No such file or directory (2)
DefaultLogger: [02-05-2024 13:03:14] Failed to set TopExecutor to RR2 init cpuset: /sys/fs/cgroup/cpuset/rr2init/tasks
[STM] Waiting for STM master to start...
[STM] Master launched
[STM][INFO] Performing Client Global Shm Init ...
[STM] Connected to STM master...
[STM] Waiting for receiving pebble_process0's Schedule Instances from master
[STM] Client pebble_process0 is waiting on init semaphore expected to be released by stm_master
[STM] Client pebble_process0 initialized
[STM] stmEnterScheduler called for client pebble_process0
[STM] Starting thread pool0

process.log

> [HelloNode] Hello from HelloNode! Constructor
> [HelloNode] Hello from HelloNode! InitInputPorts
> [HelloNode] Hello from HelloNode! InitOutputPorts
> [HelloNode] Hello from HelloNode! RegisterPasses

I don’t see the processPass() function being invoked.

dwStatus HelloNodeImpl::processPass()
{
    DW_LOGD << "Hello from HelloNode!" << Logger::State::endl;
    return DW_SUCCESS;
}

Any settings.. I may be missing ?

SivaRamaKrishnaNV · April 1, 2025, 8:07am

Thank you for sharing the json files. I will check the issue on DRIVE OS 6.0.10 and get back to you.

stefan65 · April 1, 2025, 9:08am

nvidia.gz (3.0 KB)

stefan65 · April 2, 2025, 3:02am

  "comment": "Hello Node",
    "library": "libpebble_node.so",
    "name": "dw::framework::HelloNode",
    "inputPorts": {
	"Hello": {
            "type": "float",
            "bindingRequired": true
        }
     },
    "outputPorts": {},
    "parameters": {},
    "passes": [
        {
            "name": "SETUP",
            "processorTypes": [
                "CPU"
            ]
        },
        {
            "name": "PROCESS",
            "processorTypes": [
                "CPU"
            ]
        },
        {
            "name": "TEARDOWN",
            "processorTypes": [
                "CPU"
            ]
        }
    ]
}

stefan65 · April 2, 2025, 6:32am

Attempt to provide cleaner logs… (process.log and schedular logs will clean jsons, yaml and stm file)

Result is same as previously reported (dwStatus HelloNodeImpl::processPass() not getting called)

Where auto-generated registerPasses looks like this..

void HelloNodeImpl::registerPasses()
{
    DW_LOGD << "Hello from HelloNode! RegisterPasses " << Logger::State::endl;
    using dw::core::operator""_sv;
    NODE_REGISTER_PASS("PROCESS"_sv,
        [this]() -> dwStatus {
            return processPass();
        });
}

/* Schedule Manager */
root@tegra-ubuntu:/home/pebble-admin# /usr/local/driveworks/bin/ScheduleManager --loglevel=DW_LOG_VERBOSE --binPath=/usr/local/driveworks/bin --schedule=/home/pebble-admin/data/pebble_vcu/aarch64/install/bin/pebble_app/DWCGFPebble__standardSchedule.stm --spec=/home/pebble-admin/data/pebble_vcu/aarch64/install/graphs/pebble_app/appPebble/DWCGFPebble.app.json --enableScheduleSwitching=true --scheduleManagerHostIP=127.0.0.1 --scheduleManagerHostPort=4010 --scheduleManagerNumLoaderClients=5 --scheduleManagerNumSSMClients=5 --logspec=file/rfc5424.user.schedule_manager:/home/pebble-admin/fota/LogFolder/pebble_app/Pebble/schedule_manager.log --schedule-manager-name=CGF-ScheduleManager --sensorSyncEnabled=0 --disablePrioInit=0 --enablePrioSched=1
ProgramArguments: Missing argument  'logPath' requested
ProgramArguments: Missing argument  'shadow' requested
[STM] Waiting for STM master to start...
[STM] Master not launched; reattempting in 1 sec (59 attempts remaining)
[STM] Master not launched; reattempting in 1 sec (58 attempts remaining)
[STM] Master not launched; reattempting in 1 sec (57 attempts remaining)
[STM] Master not launched; reattempting in 1 sec (56 attempts remaining)
[STM] Master launched
[STM] Connected to STM master


/* stm_master */

root@tegra-ubuntu:/home/pebble-admin# sudo /usr/local/driveworks/bin/stm_master --schedule=/home/pebble-admin/data/pebble_vcu/aarch64/install/bin/pebble_app/DWCGFPebble__standardSchedule.stm --soc=TegraA --timeout-us=80000000 -m --schedule-manager-name=CGF-ScheduleManager --num-input-schedule=1
[STM][INFO] Log Name               : NULL
[STM][INFO] Master Forked Log Path : .
[STM][INFO] SchedArray             : /home/pebble-admin/data/pebble_vcu/aarch64/install/bin/pebble_app/DWCGFPebble__standardSchedule.stm
[STM][INFO] Sched Manager Name     : CGF-ScheduleManager
[STM][INFO] Num Input Schedule     : 1
[STM][INFO] SoC                    : TegraA
[STM][INFO] Core                   : -1
[STM][INFO] CPU Affinity           : true
[STM][INFO] Verbose                : false
[STM][INFO] Hyper Epoch Max        : -1
[STM][INFO] Parse Debug            : false
[STM][INFO] Timeout (US)           : 80000000
[STM][INFO] Log Frequency          : 30
[STM][INFO] No Skip On Overrun     : 1
[STM][INFO] Thread Priority        : 1
[STM][INFO] Primary Xavier IP      : NULL
[STM][INFO] Interface              : eth0
[STM][INFO] Socket Timeout US      : 5000000
[STM][INFO] Start Socket Timeout   : 600
[STM][INFO] Suffix Timestamp       : true
[STM][INFO] Blocking Log Send      : false
[STM][INFO] MemLock                : false
[STM][INFO] Base Port              : 8000
[STM][INFO] Discriminator          : -1
[STM][INFO] cuDLA standalone       : false
[STM][INFO] Disable Engine Prefer  : false
[STM][INFO] Disable Engine Fences  : false
[STM][INFO] Allow Unregistered runnables : false
[STM][INFO] Round Robin Skip Count : 0
[STM][INFO] Cond Var Fences      : 1
[STM] Start schedule manager now.
[STM] Waiting for schedule manager : CGF-ScheduleManager ...
[STM] Registered CGF-ScheduleManager with pid 263096
[STM] Schedule manager starting state logic.
[STM] Start clients now.
[STM] Master waiting for all clients to start...
[STM] Waiting for client pebble_process0...
[STM] Starting state machine thread for STM
[STM] Registered client pebble_process0
[STM] Waiting for client framesync_TegraA_pebbleappHyperepoch_pebbleappEpoch...
[STM] Registered client framesync_TegraA_pebbleappHyperepoch_pebbleappEpoch
[STM] All clients running...
[STM] Exporting schedule to clients...
[STM] Sending schedule id for schedule '/home/pebble-admin/data/pebble_vcu/aarch64/install/bin/pebble_app/DWCGFPebble__standardSchedule.stm' to clients
[STM] Initializing sync objects for schedule /home/pebble-admin/data/pebble_vcu/aarch64/install/bin/pebble_app/DWCGFPebble__standardSchedule.stm
[STM] Initializing commands for schedule /home/pebble-admin/data/pebble_vcu/aarch64/install/bin/pebble_app/DWCGFPebble__standardSchedule.stm
[STM] Done exporting schedule to clients
[STM] STM clients starting scheduling loop.
[STM] Waiting for specified number of epochs to complete or any STM client to terminate.
[STM] STM client framesync_TegraA_pebbleappHyperepoch_pebbleappEpoch exited normally with status: 0
[STM] STM client pebble_process0 has exited

/* LoaderLite */

root@tegra-ubuntu:/home/pebble-admin# /usr/local/driveworks/bin/LoaderLite --swcid=pebble_process0 --libname=RuntimeGraphlet --modulename=pebble_process0 --app_parameter= --binPath=/usr/local/driveworks/bin --datapath=/home/pebble-admin/data/pebble_vcu/aarch64/install/data/pebble_app --dwdatapath=/home/pebble-admin/data/pebble_vcu/aarch64/install/data --logPath=/home/pebble-admin/fota/LogFolder/pebble_app/Pebble --loglevel=DW_LOG_VERBOSE --path=/usr/local/driveworks/bin --schedule=/home/pebble-admin/data/pebble_vcu/aarch64/install/bin/pebble_app/DWCGFPebble__standardSchedule.stm --spec=/home/pebble-admin/data/pebble_vcu/aarch64/install/graphs/pebble_app/appPebble/DWCGFPebble.app.json --machine_id=machine0 --logspec=file/rfc5424.user.pebble_process0:/home/pebble-admin/fota/LogFolder/pebble_app/Pebble/pebble_process0.log


--------------------------------------------------------------
WARNING: Using default Logger, most probably DriveWorks
         library was linked more than once.
--------------------------------------------------------------

DefaultLogger: [03-05-2024 13:04:37] TopExecutor: set TopExecutor to cpuset /sys/fs/cgroup/cpuset/rr2init/tasks
DefaultLogger: [03-05-2024 13:04:37] Failed to open cpuset /sys/fs/cgroup/cpuset/rr2init/tasks, errno: No such file or directory (2)
DefaultLogger: [03-05-2024 13:04:37] Failed to set TopExecutor to RR2 init cpuset: /sys/fs/cgroup/cpuset/rr2init/tasks
[STM] Waiting for STM master to start...
[STM] Master launched
[STM][INFO] Performing Client Global Shm Init ...

Tarball contains jsons, stm and process and schedular logs…

nvidia.tar.gz (1.5 MB)

stefan65 · April 2, 2025, 12:41pm

hello_world.tar.gz (512.0 KB)

stefan65 · April 3, 2025, 5:03am

root@tegra-ubuntu:/home/pebble-admin# /usr/local/driveworks/bin/ScheduleManager --loglevel=DW_LOG_VERBOSE --binPath=/usr/local/driveworks/bin --schedule=/home/pebble-admin/data/pebble_vcu/aarch64/install/bin/pebble_app/DWCGFPebble__standardSchedule.stm --spec=/home/pebble-admin/data/pebble_vcu/aarch64/install/graphs/pebble_app/appPebble/DWCGFPebble.app.json --enableScheduleSwitching=true --scheduleManagerHostIP=127.0.0.1 --scheduleManagerHostPort=4010 --scheduleManagerNumLoaderClients=5 --scheduleManagerNumSSMClients=5 --logspec=file/rfc5424.user.schedule_manager:/home/pebble-admin/fota/LogFolder/pebble_app/Pebble/schedule_manager.log --schedule-manager-name=CGF-ScheduleManager --sensorSyncEnabled=0 --disablePrioInit=0 --enablePrioSched=1
ProgramArguments: Missing argument  'logPath' requested
ProgramArguments: Missing argument  'shadow' requested
[STM] Waiting for STM master to start...
[STM] Master not launched; reattempting in 1 sec (59 attempts remaining)
[STM] Master not launched; reattempting in 1 sec (58 attempts remaining)
[STM] Master not launched; reattempting in 1 sec (57 attempts remaining)
[STM] Master not launched; reattempting in 1 sec (56 attempts remaining)
[STM] Master not launched; reattempting in 1 sec (55 attempts remaining)
[STM] Master not launched; reattempting in 1 sec (54 attempts remaining)
[STM] Master not launched; reattempting in 1 sec (53 attempts remaining)
[STM] Master not launched; reattempting in 1 sec (52 attempts remaining)
[STM] Master not launched; reattempting in 1 sec (51 attempts remaining)
[STM] Master not launched; reattempting in 1 sec (50 attempts remaining)
[STM] Master launched
[STM] Connected to STM master

root@tegra-ubuntu:/home/pebble-admin# sudo /usr/local/driveworks/bin/stm_master --schedule=/home/pebble-admin/data/pebble_vcu/aarch64/install/bin/pebble_app/DWCGFPebble__standardSchedule.stm --soc=TegraA --timeout-us=80000000 -v -m --schedule-manager-name=CGF-ScheduleManager --num-input-schedule=1 
[STM][INFO] Log Name               : NULL
[STM][INFO] Master Forked Log Path : .
[STM][INFO] SchedArray             : /home/pebble-admin/data/pebble_vcu/aarch64/install/bin/pebble_app/DWCGFPebble__standardSchedule.stm
[STM][INFO] Sched Manager Name     : CGF-ScheduleManager
[STM][INFO] Num Input Schedule     : 1
[STM][INFO] SoC                    : TegraA
[STM][INFO] Core                   : -1
[STM][INFO] CPU Affinity           : true
[STM][INFO] Verbose                : true
[STM][INFO] Hyper Epoch Max        : -1
[STM][INFO] Parse Debug            : false
[STM][INFO] Timeout (US)           : 80000000
[STM][INFO] Log Frequency          : 30
[STM][INFO] No Skip On Overrun     : 1
[STM][INFO] Thread Priority        : 1
[STM][INFO] Primary Xavier IP      : NULL
[STM][INFO] Interface              : eth0
[STM][INFO] Socket Timeout US      : 5000000
[STM][INFO] Start Socket Timeout   : 600
[STM][INFO] Suffix Timestamp       : true
[STM][INFO] Blocking Log Send      : false
[STM][INFO] MemLock                : false
[STM][INFO] Base Port              : 8000
[STM][INFO] Discriminator          : -1
[STM][INFO] cuDLA standalone       : false
[STM][INFO] Disable Engine Prefer  : false
[STM][INFO] Disable Engine Fences  : false
[STM][INFO] Allow Unregistered runnables : false
[STM][INFO] Round Robin Skip Count : 0
[STM][INFO] Cond Var Fences      : 1
[STM WARNING]:[src/dwstm/runtime/src/core/stdout.c][logSetVerbose] [30]: Verbose mode has been enabled for STM. ***Note that this mode affects STM latency guarantees, and is meant for use only in debugging. Do not use '-v' for performance testing.
[STM][WARN] Verbose mode has been enabled for STM. ***Note that this mode affects STM latency guarantees, and is meant for use only in debugging. Do not use '-v' for performance testing.
[STM INFO]:[src/dwstm/runtime/src/master/master.c][stmMasterInitScheduleList] Input Schedule: /home/pebble-admin/data/pebble_vcu/aarch64/install/bin/pebble_app/DWCGFPebble__standardSchedule.stm
[STM INFO]:[src/dwstm/runtime/src/master/master.c][stmMasterInitScheduleList] Following 1 schedules provided.
[STM INFO]:[src/dwstm/runtime/src/master/master.c][stmMasterInitScheduleList] 	 Schedule0 : /home/pebble-admin/data/pebble_vcu/aarch64/install/bin/pebble_app/DWCGFPebble__standardSchedule.stm.
[STM INFO]:[src/dwstm/runtime/src/master/master.c][stmMasterInitClientPerSchedule] Schedule ID : 0
[STM INFO]:[src/dwstm/runtime/src/master/master.c][stmMasterInitClientPerSchedule] 	Client name: pebble_process0
[STM INFO]:[src/dwstm/runtime/src/master/master.c][stmMasterInitClientPerSchedule] 	Client soc: TegraA
[STM INFO]:[src/dwstm/runtime/src/master/master.c][stmMasterInitClientPerSchedule] 	Client name: framesync_TegraA_pebbleappHyperepoch_pebbleappEpoch
[STM INFO]:[src/dwstm/runtime/src/master/master.c][stmMasterInitClientPerSchedule] 	Client soc: TegraA
[STM INFO]:[src/dwstm/runtime/src/master/master.c][stmMasterInitShmMasterPerClient] Total Numbers of thread for schedule 0 : 2
[STM][INFO] Opening NvSciIpc endpoints...
[STM INFO]:[src/dwstm/runtime/src/master/main.cpp][main] Client Name pebble_process0
[STM INFO]:[src/dwstm/runtime/src/master/main.cpp][main] Client Name framesync_TegraA_pebbleappHyperepoch_pebbleappEpoch
[STM INFO]:[src/dwstm/runtime/src/master/master.c][stmMasterLaunchClient] Launching client: framesync_TegraA_pebbleappHyperepoch_pebbleappEpoch
[STM INFO]:[src/dwstm/runtime/src/master/master.c][stmMasterLaunchClient] Launched client framesync_TegraA_pebbleappHyperepoch_pebbleappEpoch with pid: 283839
[STM] Start schedule manager now.
[STM] Waiting for schedule manager : CGF-ScheduleManager ...
[STM] Registered CGF-ScheduleManager with pid 283830
[STM] Schedule manager starting state logic.
[STM] Start clients now.
[STM] Master waiting for all clients to start...
[STM] Waiting for client pebble_process0...
[STM] Starting state machine thread for STM
[STM][INFO] PID 283837, requesting state transition from STM_STATE_BOOT to STM_STATE_INIT time: 21:55:46.003165152 (856546003165152)
[STM] Registered client pebble_process0
[STM] Waiting for client framesync_TegraA_pebbleappHyperepoch_pebbleappEpoch...
[STM] Registered client framesync_TegraA_pebbleappHyperepoch_pebbleappEpoch
[STM] All clients running...
[STM] Exporting schedule to clients...
[STM] Sending schedule id for schedule '/home/pebble-admin/data/pebble_vcu/aarch64/install/bin/pebble_app/DWCGFPebble__standardSchedule.stm' to clients
[STM][INFO] PID 283837, new state STM_STATE_INIT, time: 21:55:56.309202304 (856556309202304)
[STM][INFO] PID 283837, requesting state transition from STM_STATE_INIT to STM_STATE_READY time: 21:55:56.309242400 (856556309242400)
[STM] Initializing sync objects for schedule /home/pebble-admin/data/pebble_vcu/aarch64/install/bin/pebble_app/DWCGFPebble__standardSchedule.stm
[STM] SyncServer: Begin
[STM] SyncServer: Starting SyncObj s0 (CondVarSync)
[STM] SyncServer: Done SyncObj     s0
[STM] SyncServer: Starting SyncObj s1 (CondVarSync)
[STM] SyncServer: Done SyncObj     s1
[STM] SyncServer: Initializing fences
[STM] SyncServer: Fence initialization done
[STM] SyncServer: End
[STM] Initializing commands for schedule /home/pebble-admin/data/pebble_vcu/aarch64/install/bin/pebble_app/DWCGFPebble__standardSchedule.stm
[STM] Done exporting schedule to clients
[STM] STM clients starting scheduling loop.
[STM] Waiting for specified number of epochs to complete or any STM client to terminate.
[STM][INFO] PID 283837, new state STM_STATE_READY, time: 21:55:56.372722272 (856556372722272)

root@tegra-ubuntu:/home/pebble-admin/fota/LogFolder/pebble_app/Pebble# /usr/local/driveworks/bin/LoaderLite --swcid=pebble_process0 --libname=RuntimeGraphlet --modulename=pebble_process0 --app_parameter= --binPath=/usr/local/driveworks/bin --datapath=/home/pebble-admin/data/pebble_vcu/aarch64/install/data/pebble_app --dwdatapath=/home/pebble-admin/data/pebble_vcu/aarch64/install/data --logPath=/home/pebble-admin/fota/LogFolder/pebble_app/Pebble --loglevel=DW_LOG_VERBOSE --path=/usr/local/driveworks/bin --schedule=/home/pebble-admin/data/pebble_vcu/aarch64/install/bin/pebble_app/DWCGFPebble__standardSchedule.stm --spec=/home/pebble-admin/data/pebble_vcu/aarch64/install/graphs/pebble_app/appPebble/DWCGFPebble.app.json --machine_id=machine0 --logspec=file/rfc5424.user.pebble_process0:/home/pebble-admin/fota/LogFolder/pebble_app/Pebble/pebble_process0.log 


--------------------------------------------------------------
WARNING: Using default Logger, most probably DriveWorks
         library was linked more than once.
--------------------------------------------------------------

DefaultLogger: [04-05-2024 11:36:08] TopExecutor: set TopExecutor to cpuset /sys/fs/cgroup/cpuset/rr2init/tasks
DefaultLogger: [04-05-2024 11:36:08] Failed to open cpuset /sys/fs/cgroup/cpuset/rr2init/tasks, errno: No such file or directory (2)
DefaultLogger: [04-05-2024 11:36:08] Failed to set TopExecutor to RR2 init cpuset: /sys/fs/cgroup/cpuset/rr2init/tasks
[STM] Waiting for STM master to start...
[STM] Master launched
[STM][INFO] Performing Client Global Shm Init ...
[STM][WARN] Verbose mode has been enabled for STM. ***Note that this mode affects STM latency guarantees, and is meant for use only in debugging. Do not use '-v' for performance testing.
[STM][INFO] Connecting to STM master...
[STM] Connected to STM master...
[STM] Waiting for receiving pebble_process0's Schedule Instances from master
[STM][INFO] Waiting for receiving pebble_process0's schedule ID No.  from master
[STM][INFO] Received following Schedule IDs for Clientpebble_process0
[STM][INFO] 	 ID 0 : 0
[STM] Client pebble_process0 is waiting on init semaphore expected to be released by stm_master
[STM] Client pebble_process0 initialized
[STM] SyncClient: Begin
[STM] SyncClient: All SyncObjs created
[STM] SyncClient: Initializing CondVar fences
[STM] SyncClient: CondVar fence initialization done
[STM] SyncClient: End
[STM] stmEnterScheduler called for client pebble_process0
[STM][INFO] Client pebble_process0 is waiting on enter scheduler semaphore for syncing
[STM][INFO] Client pebble_process0 proceeding with enter scheduler
[STM WARNING]:[src/dwstm/runtime/src/core/stdout.c][logSetVerbose] [30]: Verbose mode has been enabled for STM. ***Note that this mode affects STM latency guarantees, and is meant for use only in debugging. Do not use '-v' for performance testing.
[STM][WARN] Verbose mode has been enabled for STM. ***Note that this mode affects STM latency guarantees, and is meant for use only in debugging. Do not use '-v' for performance testing.
[STM] Starting thread pool0
[STM WARNING]:[src/dwstm/runtime/src/client/thread.cpp][stmStart] [166]: Could not set cpuset, setCpuset returned an error. errno=2 (No such file or directory)
[STM INFO]:[src/dwstm/runtime/src/client/thread.cpp][stmStart] Thread waiting on Enter Schedule fence pool0, time: 21:55:56.371657824 (856556371657824)
[STM INFO]:[src/dwstm/runtime/src/client/thread.cpp][stmStart] Thread released from Enter Schedule pool0, time: 21:55:56.372759872 (856556372759872)
[STM INFO]:[src/dwstm/runtime/src/client/thread.cpp][stmStart] Thread waiting on Ready fence pool0, time: 21:55:56.372778400 (856556372778400)

When I kill the process I see the state transition..

[STM][INFO] PID 283880, requesting state transition from STM_STATE_READY to STM_STATE_EXIT time: 21:58:21.195681600 (856701195681600)
[STM][INFO] PID 283880, new state STM_STATE_EXIT, time: 21:58:21.196740544 (856701196740544)
[STM][INFO] PID 283839, requesting state transition from STM_STATE_EXIT to STM_STATE_EXIT time: 21:58:21.196757824 (856701196757824)
[STM][INFO] PID 283839, new state STM_STATE_EXIT, time: 21:58:21.196764896 (856701196764896)
[STM] STM client framesync_TegraA_pebbleappHyperepoch_pebbleappEpoch exited normally with status: 0
[STM] STM client pebble_process0 has exited
[STM] STM Schedule Manager CGF-ScheduleManager has exited
[STM] State Managing Thread for STM exiting successfully.

hello_world_April_2.tar.gz (187.4 KB)

SivaRamaKrishnaNV · April 9, 2025, 6:49am

Dear @stefan65,
As I understand from logs, you could run the node with out any issue but you don’t see prints from processPass() function. I expect the prints to come with DW_LOG_VERBOSE flag as you have used.
If so, can you confirm if the libs(libpebble_node.so) are copied to target after you have made changes in processPass() and compiled again.

stefan65 · April 9, 2025, 6:47pm

Yes, it’s part of the process to always copy libpebble_node.so to the target.
DW_LOGD in processPass was added first and then I added DW_LOGD to constructors to debug what all passes are called.

So I could see additional log added afterwards…

[HelloNode] Hello from HelloNode! Constructor
[HelloNode] Hello from HelloNode! InitInputPorts
[HelloNode] Hello from HelloNode! InitOutputPorts
[HelloNode] Hello from HelloNode! RegisterPasses

Topic		Replies	Views
[BUG] cgf helloworld sample socket communication inconsistency behavior in mailbox+reuse connection DRIVE AGX Orin General driveworks-cgf	13	568	June 5, 2024
Creating a custom hello world application and integration - Driveworks CGF DRIVE AGX Orin General driveworks-cgf	17	796	June 28, 2023
[BUG] cgf helloworld sample nvsci+interprocess communication hangs with exception error DRIVE AGX Orin General driveworks-cgf	32	715	July 29, 2024
[BUG] cgf helloworld example 6.0.8.1 return status 1, stm_master errno=11 (Resource temporarily unavailable) DRIVE AGX Orin General driveworks-cgf	17	1130	January 3, 2024
Driveworks Entron camera queue timeout DRIVE AGX Orin General driveworks	12	92	October 17, 2024
Drive OS Migration from 6.0.6 to 6.0.10 DRIVE AGX Orin General drive-platform-setup	13	42	March 24, 2025
DRIVE AGX : Falshing Failed DRIVE AGX Xavier General drive-platform-setup	4	1280	October 12, 2021
Jetson TX2 GPU & main-stream Linux kernel Jetson TX2	3	1745	July 26, 2018
Drive Orin System hang DRIVE AGX Orin General drive-platform-bootup	43	2170	April 3, 2023
Driveworks sample camera emulation with AR0231 failed DRIVE AGX Xavier General driveworks-cameras	9	1046	October 5, 2023

6.0.10 Hello World Graph

Output

Input Description file path: /gw_demo/src/sys/src/cgf/app/graphs/appPebble/DWCGFPebble.app.json

Related topics