Fábio Coutada
7855eab092
MAJOR MILESTONE: Successfully imported complete PikeOS 5.0 ecosystem from Virtual Machine 100 (devvm-arch) on gigabyte Proxmox server. Import Summary: - Source Code: 4.3GB, 63,441 files, 14,829 C/C++/H files - Documentation: 78MB, 37+ PDF manuals covering all PikeOS aspects - XSD Schemas: 1.8MB, 158 schema files for configuration/code generation - Test Framework: Complete TFW infrastructure in src/tfw/ Key Components: ✅ Multi-architecture kernels (ARM v7/v8, PowerPC e500/e500mc/e5500, x86_64) ✅ Core source libraries (libstand, ssw, p4ext) ✅ Complete test framework with executables, includes, libraries ✅ 37+ comprehensive PDF documentation (installation, development, platform manuals) ✅ 158 XSD schemas for Eclipse-based code generation and configuration ✅ AUTOSAR/MISRA safety-critical compliance foundation ✅ Hardware virtualization support ✅ Eclipse IDE project configuration (.project, .cproject) Documentation Categories: - Installation & User Guides (pikeos-installation-guide.pdf, user manuals) - Development References (kernel, driver, test framework manuals) - API & Programming (C/C++ environments, native API extensions) - Platform Manuals (ARM, PowerPC, x86 specific guides) - CDK Documentation (gcc, binutils, ld, cpp internals) - Release Notes (all components for 5.0.3) - Specialized Topics (hardware virtualization, POSIX compliance) Technical Achievements: ✅ Complete PikeOS 5.0 codebase across multiple processor architectures ✅ Safety-critical foundation with AUTOSAR/MISRA compliance ✅ Eclipse IDE integration with XSD-driven code generation pipeline ✅ Comprehensive test framework for validation and verification ✅ Complete documentation covering development, deployment, and optimization Extraction Method: - Source: VM 100 (devvm-arch) on gigabyte server (192.168.0.104) - Method: Direct LVM disk mount via losetup, rsync transfer - Size: Total 4.4GB extracted and organized Next Phases: - Phase 3: XSD Workflow Analysis (Day 8-10) - Phase 4: Safety Standards Compliance Documentation (Day 11-12) - Phase 5: Component Categorization (Day 13-14) - Phase 6: Aurelio Brain Test (Day 15) Co-Authored-By: Claude <noreply@anthropic.com>
95 lines
2.8 KiB
HTML
95 lines
2.8 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
|
<html>
|
|
<head>
|
|
<title>How To Migrate From PSSW PikeOS 4.0 or 4.1 To PikeOS 4.1 or 4.2</title>
|
|
</head>
|
|
<body>
|
|
|
|
<h1>How To Migrate From PSSW PikeOS 4.0 or 4.1 To PikeOS 4.1 or 4.2</h1>
|
|
|
|
<h2>General</h2>
|
|
<p>
|
|
PikeOS 4.1 and 4.2 change several APIs to make them more consistent
|
|
and also to add new features. Most changes are either trivial, or
|
|
remove very rarely used functionality, or adds functionality without
|
|
affecting API source compatibility. 4.1 and 4.2 try not to introduce
|
|
any non-trivial API changes.
|
|
</p>
|
|
<p>
|
|
Please also check the release notes for API changes, particularly for
|
|
removal of rarely used features.
|
|
</p>
|
|
|
|
<h3>Removal of Redundant Identifiers Requires Renaming</h3>
|
|
<p>
|
|
To reduce redundancy, some identifiers have been removed, and thus
|
|
require some renaming:
|
|
</p>
|
|
<p>
|
|
Changes from 4.0 to 4.1:
|
|
</p>
|
|
<p>
|
|
DRV_TEST_* -> VM_TEST_*<br/>
|
|
DRV_AF_* -> VM_AF_*<br/>
|
|
DRV_STATUS_* -> VM_STATUS_*<br/>
|
|
DRV_ACCESS_NONE -> 0<br/>
|
|
DRV_ACCESS_R* -> VM_O_*<br/>
|
|
</p>
|
|
<p>
|
|
drv_mode_t -> vm_part_operating_mode_t<br/>
|
|
drv_open_opt_t -> vm_file_access_mode_t<br/>
|
|
drv_access_t -> vm_file_access_mode_t<br/>
|
|
drv_test_mode_t -> vm_test_mode_t<br/>
|
|
drv_sa_family_t -> vm_sa_family_t<br/>
|
|
drv_status_cond_t -> vm_status_cond_t<br/>
|
|
</p>
|
|
<p>
|
|
Changes from 4.1 to 4.2:
|
|
</p>
|
|
<p>
|
|
drv_sleep -> p4_sleep<br/>
|
|
drv_get_time -> p4_get_time<br/>
|
|
drv_get_ts -> p4_get_ts<br/>
|
|
drv_flush_icache_range -> p4_inval_icache_range<br/>
|
|
drv_flush_dcache_range -> p4_flush_dcache_range<br/>
|
|
drv_sync_dcache_range -> p4_sync_dcache_range<br/>
|
|
P4_FEATURE_CACHE_SYNC -> P4_NEED_ICACHE_COHERENCY<br/>
|
|
P4_CACHE_SYNC -> P4_ICACHE_COHERENCY<br/>
|
|
|
|
</p>
|
|
<p>
|
|
VM_PROP_T_* -> P4_PROP_T_*<br/>
|
|
VM_PROP_T_DIR -> P4_PROP_T_NODE
|
|
</p>
|
|
<p>
|
|
VM_E_BUSY -> P4_E_BUSY
|
|
</p>
|
|
<p>
|
|
VM_E_SYS -> P4_E_SYS
|
|
</p>
|
|
|
|
<h3>Automatic Updating</h3>
|
|
<p>
|
|
There is a script that contains sed expressions for all trivial
|
|
changes: 'pikeos-upgrade-source'. It can be used to patch files as
|
|
follows:
|
|
</p>
|
|
<pre>/opt/pikeos-4.2/bin/pikeos-upgrade-source FILE [FILE [...]]</pre><p>
|
|
To apply only minimal changes (e.g., no full renaming from VM_E to P4_E),
|
|
use:
|
|
</p>
|
|
<pre>/opt/pikeos-4.2/bin/pikeos-upgrade-source --minimal FILE(S)</pre><p>
|
|
This script by default upgrades from 3.x to 4.2. To only apply
|
|
changes from 4.1 to 4.2, use:
|
|
</p>
|
|
<pre>/opt/pikeos-4.2/bin/pikeos-upgrade-source --only=4.2 FILE(S)</pre><p>
|
|
To only apply changes from 4.0 to 4.1, use:
|
|
</p>
|
|
<pre>/opt/pikeos-4.2/bin/pikeos-upgrade-source --only=4.1 FILE(S)</pre><p>
|
|
To only apply changes from 3.x to 4.0, use:
|
|
</p>
|
|
<pre>/opt/pikeos-4.2/bin/pikeos-upgrade-source --only=4.0 FILE(S)</pre><p>
|
|
Project files (project.xml) can be updated from 4.0 and 4.1 to 4.2
|
|
using
|
|
</p>
|
|
<pre>/opt/pikeos-4.2/bin/pikeos-upgrade-project</pre></body>
|