- #CUDATEXT DEBUGGER UPDATE#
- #CUDATEXT DEBUGGER FULL#
- #CUDATEXT DEBUGGER PORTABLE#
- #CUDATEXT DEBUGGER SOFTWARE#
- #CUDATEXT DEBUGGER CODE#
I am very impressed at the quality feel of this opensource project. Granted, the Oberon compiler is MUCH simpler to deal with as far as compilers go, it appears that rigging up any other compiler would be rather strait forward. I am (or plan to soon) be setting this up for Astrobe Oberon, which is an Oberon compiler for the LPCxxx family chips (ARM 3/4/5). I found a cool project called CudaText which could easily replace Eclipse if you are willing to do some minor mods. The time saved in getting a developer started is staggering. Same compiler, same debugger, same jtag software+hardware. We're currently developing products based on the following MCUs: Nordic nRF51822, STM32F103, TI CC3300 Guess what? We didn't have to change a thing in our environment when developers switch between projects.
#CUDATEXT DEBUGGER FULL#
Actual example, shipping product, wearables segment: Full rebuild time in IAR: 20 minutes Full rebuild time with GCC in Linux: ~35 seconds How many times a day are your developers compiling their code? Multiply that with the speedup you'd get by switching to something like gcc in Linux, and you'll come up with some pretty interesting figures. And anyone that says that you'll save time by using Keil or IAR are straight up misinformed.
SCM/RCS is done in git, since we're living in 2016 these days.
gcc + gdb + openocd are the tools for us, and each developer gets to choose how they (or don't) wrap them with IDEs and whatnot. Not that my company is very "standard", but you'd get extra points for knowing the free tools, as that's what we're using for development and production.
#CUDATEXT DEBUGGER SOFTWARE#
Their initial boards would have been more expensive but the development time would have been less and the value of the investment in the software would not have to be written off so quickly because it would be possible to use more powerfull and cheaper DSPs.
#CUDATEXT DEBUGGER PORTABLE#
If the software engineers had written the software in a more portable language/way they could have switched DSP suppliers more easely and create cost savings in their products by using cheaper DSPs. During that conference call it turned out the software was all written in assembly for a DSP which was about to become obsolete and worse: Motorola wasn't going anywhere with their DSPs so the software got kinda stuck between a rock and a hard place needing a massive amount of work to port it. The company I worked for wanted to use their IP.
Over a decade ago I was in a conference call with a company who made DSP solutions. Software has become a major asset of any company involved in software development so like any asset this needs carefull consideration and 'nursing'. In other words: the firmware gets more complex and needing to start from scratch for every product is a no go. That is old school thinking!! Nowadays a product containing a microcontroller needs 5% of time spend on hardware and 95% on the firmware. then go for Keil when having some experience. So, from what I read, most of you recommend starting up with one of the free tools build around eclipse (manufacturer's own IDEs). I still wonder about development of products (based on ARM MCUs) if they breadboard the target MCU (after soldering it on a small PCB) on a breadboard and do stuff like us PIC guys do, or they _always_ get a dev board and build everything around it then get the mcu that was on it and download the program.
#CUDATEXT DEBUGGER CODE#
So I can not use the code I wrote for, say STM23 or one of their disco boards, when making the actual product unless I go in and re-write many parts of it to suite the new compiler or MCU itself. How about their compilers? Different compilers leads to different syntax and stuff like people argued above. However, when companies hire embedded engineers, will they consider someone who hasn't used Keil/IAR and kept using free tools. dlang.Well, I will follow your advice and use a free tool when learning STM32 that I think ST provide (based on eclipse I guess). The autocompletition, for me, works just for the "reserved words" of the language, doesn't seems to be completition of variables or classes, however there is this thread that ask for help with the integration of DCD ( forum. The sintaxt hightlight it's not really complete
#CUDATEXT DEBUGGER UPDATE#
However on internet there is no guide or discussion of how use all the listed feature, checking direclty the application seems that the editor is lack in the most of the feature, is it better to update the page? Hello, I was searching for a good IDE or editor with dlang support and looking at the "editors" page in the wiki ( ) Cudatext(and synwrite) have a really good built-in support for dlang.
0 kommentar(er)
