Changes between Version 28 and Version 29 of Developer/Eclipse/Information
- Timestamp:
- 11/22/18 16:26:46 (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Developer/Eclipse/Information
v28 v29 1 1 = RTEMS Eclipse Support = 2 2 3 RTEMS provides an Eclipse Plugin you can use to help integrate your work 3 RTEMS provides an Eclipse Plugin you can use to help integrate your workflow with RTEMS. 4 4 5 5 [[TOC(Developer/Eclipse/Information, depth=2)]] … … 18 18 years honing RTEMS and tuning it to be a competitive run-time and it 19 19 certainly has the technical capabilities to compete. But often RTEMS gets 20 dinged for not having a "pretty face". Projects in this category 21 address that deficiency. 22 23 [http://www.eclipse.org Eclipse] is an open source Integrated Development 20 dinged for not having a "pretty face". Projects in this category address that deficiency. 21 22 [http://www.eclipse.org Eclipse] is an open-source Integrated Development 24 23 Environment (IDE) which has become very popular in the real-time embedded 25 systems community. For RTEMS to continue to compare favo rably against24 systems community. For RTEMS to continue to compare favourably against 26 25 its commercial proprietary competition, Eclipse support is an important 27 26 feature. Eclipse has a plug-in architecture and there are already 28 27 multiple plug-ins and add-ons for embedded development. 29 28 30 This is a very open 29 This is a very open-ended project which has a number of steps based 31 30 upon sub-projects or plugins which need to be made available to RTEMS 32 31 developers. … … 41 40 application and a few of those simulate target hardware with networking 42 41 capabilities. There are existing RTEMS BSPs that run on simulators so 43 the person(s) working on this project would not require special target42 the person(s) working on this project would not require a special target 44 43 hardware or anything that costs to verify that their implementation 45 44 works with multiple hardware configurations. … … 66 65 = RSE = 67 66 68 [http://www.eclipse.org/dsdp/tm/ '''RSE'''] Remote System Explorer (Target Management) can be used to create a SSH (Secure SHell) connection to the QEMU (Quick EMUlator) emulator. This can be done by connecting to69 the local host via SSH ,since the SSH port of the host has been redirected to the SSH port of the emulator. Once this connection had been established a remote shell can be launched on the QEMU using the “Launch Shell” option under “SSH Shells”. This shell can be used to browse the emulator filesystem and run commands on the emulator.67 [http://www.eclipse.org/dsdp/tm/ '''RSE'''] Remote System Explorer (Target Management) can be used to create an SSH (Secure SHell) connection to the QEMU (Quick EMUlator) emulator. This can be done by connecting to 68 the local host via SSH since the SSH port of the host has been redirected to the SSH port of the emulator. Once this connection had been established a remote shell can be launched on the QEMU using the “Launch Shell” option under “SSH Shells”. This shell can be used to browse the emulator filesystem and run commands on the emulator. 70 69 71 70 One of the interesting aspects of this is how Wind River has adopted Eclipse as the platform for vxWorks and Embedded Linux development. It appears that they are putting significant effort into contributing code back to the DSDP platform and trying to help create open standards for this type of development environment. It would be nice if this work ends up meaning that an Eclipse platform could talk to a target server on either vxWorks, Linux or RTEMS. … … 73 72 = RTSC = 74 73 75 [http://www.eclipse.org/rtsc '''RTSC (Real-Time Software Components)'''] provides foundational tools and low-level runtime content to enable component-based development using the C language targeting all embedded platforms. While other component technologies exist for embedded systems, RTSC is unique in that it scales down to highly resource 74 [http://www.eclipse.org/rtsc '''RTSC (Real-Time Software Components)'''] provides foundational tools and low-level runtime content to enable component-based development using the C language targeting all embedded platforms. While other component technologies exist for embedded systems, RTSC is unique in that it scales down to highly resource-constrained embedded systems including DSPs and 16-bit micro-controllers. 76 75 = eRCP = 77 76 … … 187 186 188 187 189 The publish ofinitial implementation of RTEMS Eclipse Plug-in came with188 The publishing of the initial implementation of RTEMS Eclipse Plug-in came with 190 189 some accidents. It's Joel Sherrill who first discovered the appearance 191 190 of such implementation. One night the initial implementer was uploading 192 screen 191 screenshots to the wiki site to document the usage of the plug-in, there 193 192 were problems with uploading files, and later the wiki site became inaccessible. 194 193 The implementer thought he might bring down the wiki site, so went to sleep. 195 On the next morning, somehow these accidents alerted Joel. Except images194 On the next morning, somehow these accidents alerted Joel. Except for images 196 195 of Eclipse with RTEMS awareness, he could not find the email address of 197 196 the "culprit", thus he yelled out on the mailing list, and so came the … … 200 199 201 200 The initial plug-in has most features of a full-fledged Eclipse/CDT IDE with 202 ordinary GNU tool chain. After setup, except typing inproject name and201 ordinary GNU toolchain. After setup, except typing in the project name and 203 202 post build commands, with only mouse clicks, it can finish the whole 204 203 process of: … … 208 207 * Link 209 208 * Generate boot image and externally start up the system (in simulator) 210 * Setup break 211 212 The detail document for the initial implementation including its209 * Setup breakpoints, and hook GDB to the remote target 210 211 The detailed document for the initial implementation including its 213 212 limitations can be found [wiki:Initial_RTEMS_Eclipse_Plug-in here]. 214 213