Jump to content
43oh

HanzZ

Members
  • Content Count

    8
  • Joined

  • Last visited

  • Days Won

    1

Reputation Activity

  1. Like
    HanzZ got a reaction from dubnet in QSimKit - MSP430 simulator   
    Hi again,
     
    this new version took me quite a long time, because I had to write and defend first part of my diploma thesis about this project. After I succeed two weeks ago, I've started developing QSimKit again and released this new version 0.0.3. I will have more time for development now, so I will start releasing more often again .
     
    Changes in version 0.0.3:
     
    QSimKit GUI:
    Drawing optimizations Fixed bug when breakpoints got lost when switching between C and ASM Fixed crash when DebugData cannot be loaded Added dialog for adding breakpoints on any change on particular memory address Fixed bug when peripherals have not been removed from left panel when creating new project MSP430:
    Add support for USCI-SPI Add support for USART-SPI Timer optimizations Fix of divider handling in all modules  
    The main feature planned for the next version is support for all series as defined here.
  2. Like
    HanzZ got a reaction from bluehash in QSimKit - MSP430 simulator   
    Hi again,
     
    this new version took me quite a long time, because I had to write and defend first part of my diploma thesis about this project. After I succeed two weeks ago, I've started developing QSimKit again and released this new version 0.0.3. I will have more time for development now, so I will start releasing more often again .
     
    Changes in version 0.0.3:
     
    QSimKit GUI:
    Drawing optimizations Fixed bug when breakpoints got lost when switching between C and ASM Fixed crash when DebugData cannot be loaded Added dialog for adding breakpoints on any change on particular memory address Fixed bug when peripherals have not been removed from left panel when creating new project MSP430:
    Add support for USCI-SPI Add support for USART-SPI Timer optimizations Fix of divider handling in all modules  
    The main feature planned for the next version is support for all series as defined here.
  3. Like
    HanzZ got a reaction from tripwire in QSimKit - MSP430 simulator   
    Hi again,
     
    this new version took me quite a long time, because I had to write and defend first part of my diploma thesis about this project. After I succeed two weeks ago, I've started developing QSimKit again and released this new version 0.0.3. I will have more time for development now, so I will start releasing more often again .
     
    Changes in version 0.0.3:
     
    QSimKit GUI:
    Drawing optimizations Fixed bug when breakpoints got lost when switching between C and ASM Fixed crash when DebugData cannot be loaded Added dialog for adding breakpoints on any change on particular memory address Fixed bug when peripherals have not been removed from left panel when creating new project MSP430:
    Add support for USCI-SPI Add support for USART-SPI Timer optimizations Fix of divider handling in all modules  
    The main feature planned for the next version is support for all series as defined here.
  4. Like
    HanzZ got a reaction from pine in QSimKit - MSP430 simulator   
    Hi,
     
    as my diploma thesis I'm writting MSP430 simulator called QSimKit. It's not finished yet, but it's in state when it's starting to be useful and I would like to get more people to test it, share their opinions, find bugs and basically to create community of people interested in MSP430 simulation.
     
    Releases:
    Version 0.0.3 (2014-02-04), Changelog At first some facts about QSimKit:
    It's written under GPLv2+ in C++/Qt, has been tested on Linux or Windows together with msp430gcc. It supports peripherals (as plugins) written in C++ or Python. Currently there's LED, oscillator, button and HD44708 LCD (not fully implemented yet). MCUs are plugins too and theoretically it's possible to add support for more MCUs (not just MSP430). It can support all MSP430 variants, but only few are supported right now, because I haven't created package data for all MSP430 variants yet. In graphical user interface (Check screenshot), you can do following:
    Add peripherals, connect them to MCU. See the source code of program you are simulating together with Dwarf debugging data (you can see the value of local variables for example) and current instruction. Step the simulation, add breakpoints based on PC register or value of memory. Track pins in oscilloscope-like view. See the registers and other important values from MCU (frequency, BasicClock registers, ...) MSP430 MCU plugin can do following:
    Load ELF/A43 code. Supports all instructions. Supports BasicClock module (TImerA/TimerB). Support for USCI-SPI [NEW in 0.0.3] Support for USART-SPI [NEW in 0.0.3] Initial USI support (just SPI mode). Peripherals:
    Button LCD - HD44708 (only initial support) LED Crystal Oscillator SD Card (only initial support) [NEW in 0.0.2]  
    As I stated earlier, it's not finished yet, but some testers to help me testing are welcome. I can also help anyone who would like to help with development. There is no development documentation yet, but if you tell me what you would like to do, I can write relevant docs to help you.
     
    If you think you have found a bug or you have some feature request, please create ticket on GitHub, I don't want this forum thread to be an issue tracker. You can also find me on IRC in #qsimkit at freenode or as HanzZ in #43oh channel.
  5. Like
    HanzZ got a reaction from bluehash in QSimKit - MSP430 simulator   
    Hi,
     
    after some time (and vacation) I had some time for QSimKit again and I've released version 0.0.2. Check first post for more information about QSimKit.
     
    Changes in version 0.0.2:
     
    QSimKit GUI:
    Save projects with .qsp extension Lot of DWARF debugging symbols loading improvements Auto-reload A43/ELF files when they change MSP430:
    Add support for USI-SPI (tested with SD card) Peripherals:
    Add basic SD card peripheral  
    The main features planned for the next version are SPI communication using USCI and probably way to view memory in hexedit-like window.
  6. Like
    HanzZ got a reaction from tingo in QSimKit - MSP430 simulator   
    Hi,
     
    as my diploma thesis I'm writting MSP430 simulator called QSimKit. It's not finished yet, but it's in state when it's starting to be useful and I would like to get more people to test it, share their opinions, find bugs and basically to create community of people interested in MSP430 simulation.
     
    Releases:
    Version 0.0.3 (2014-02-04), Changelog At first some facts about QSimKit:
    It's written under GPLv2+ in C++/Qt, has been tested on Linux or Windows together with msp430gcc. It supports peripherals (as plugins) written in C++ or Python. Currently there's LED, oscillator, button and HD44708 LCD (not fully implemented yet). MCUs are plugins too and theoretically it's possible to add support for more MCUs (not just MSP430). It can support all MSP430 variants, but only few are supported right now, because I haven't created package data for all MSP430 variants yet. In graphical user interface (Check screenshot), you can do following:
    Add peripherals, connect them to MCU. See the source code of program you are simulating together with Dwarf debugging data (you can see the value of local variables for example) and current instruction. Step the simulation, add breakpoints based on PC register or value of memory. Track pins in oscilloscope-like view. See the registers and other important values from MCU (frequency, BasicClock registers, ...) MSP430 MCU plugin can do following:
    Load ELF/A43 code. Supports all instructions. Supports BasicClock module (TImerA/TimerB). Support for USCI-SPI [NEW in 0.0.3] Support for USART-SPI [NEW in 0.0.3] Initial USI support (just SPI mode). Peripherals:
    Button LCD - HD44708 (only initial support) LED Crystal Oscillator SD Card (only initial support) [NEW in 0.0.2]  
    As I stated earlier, it's not finished yet, but some testers to help me testing are welcome. I can also help anyone who would like to help with development. There is no development documentation yet, but if you tell me what you would like to do, I can write relevant docs to help you.
     
    If you think you have found a bug or you have some feature request, please create ticket on GitHub, I don't want this forum thread to be an issue tracker. You can also find me on IRC in #qsimkit at freenode or as HanzZ in #43oh channel.
  7. Like
    HanzZ got a reaction from jpnorair in QSimKit - MSP430 simulator   
    Hi,
     
    as my diploma thesis I'm writting MSP430 simulator called QSimKit. It's not finished yet, but it's in state when it's starting to be useful and I would like to get more people to test it, share their opinions, find bugs and basically to create community of people interested in MSP430 simulation.
     
    Releases:
    Version 0.0.3 (2014-02-04), Changelog At first some facts about QSimKit:
    It's written under GPLv2+ in C++/Qt, has been tested on Linux or Windows together with msp430gcc. It supports peripherals (as plugins) written in C++ or Python. Currently there's LED, oscillator, button and HD44708 LCD (not fully implemented yet). MCUs are plugins too and theoretically it's possible to add support for more MCUs (not just MSP430). It can support all MSP430 variants, but only few are supported right now, because I haven't created package data for all MSP430 variants yet. In graphical user interface (Check screenshot), you can do following:
    Add peripherals, connect them to MCU. See the source code of program you are simulating together with Dwarf debugging data (you can see the value of local variables for example) and current instruction. Step the simulation, add breakpoints based on PC register or value of memory. Track pins in oscilloscope-like view. See the registers and other important values from MCU (frequency, BasicClock registers, ...) MSP430 MCU plugin can do following:
    Load ELF/A43 code. Supports all instructions. Supports BasicClock module (TImerA/TimerB). Support for USCI-SPI [NEW in 0.0.3] Support for USART-SPI [NEW in 0.0.3] Initial USI support (just SPI mode). Peripherals:
    Button LCD - HD44708 (only initial support) LED Crystal Oscillator SD Card (only initial support) [NEW in 0.0.2]  
    As I stated earlier, it's not finished yet, but some testers to help me testing are welcome. I can also help anyone who would like to help with development. There is no development documentation yet, but if you tell me what you would like to do, I can write relevant docs to help you.
     
    If you think you have found a bug or you have some feature request, please create ticket on GitHub, I don't want this forum thread to be an issue tracker. You can also find me on IRC in #qsimkit at freenode or as HanzZ in #43oh channel.
  8. Like
    HanzZ got a reaction from jpnorair in QSimKit - MSP430 simulator   
    That depends on the complexity of the project. It's discrete simulation running in single thread where every peripheral generates events which have to be handled. With more events, simulation is slower. It's also configured to eat just 60% of your PC CPU right now.
     
    There are places which can be optimized. Those optimizations could make it much more faster (For example SMCLK generates events based on its frequency even when there is no peripheral which needs so high frequency - it has for example divider 8. In this case SMCLK could be simulated with its_frequency/8, which would mean 8x less simulation events == much more faster simulation). I plan to do those optimizations, but for now I'm working on SPI support, but this is definitely on my TODO list.
     
    To give you some numbers:
     
    In LCD simulation (MSP430 + LCD), 0.1 seconds in simulation time takes 1 second in real-time on my machine.
     
    LCD simulation with external oscillators connected to MSP430 (oscillators generate events at 8Mhz and 32Khz), it is 0.02 seconds of simulation time per 1 second in real-time. Again, possible optimization here is to not send "zeros and ones" from external oscillator to MSP430 based on its frequency, but only tell MSP430 something like "this is oscillator connected to this PIN with frequency N". That way, it would run as fast as the version without external oscillators.
     
    So, to sum it up, simulation speed is considered and I have ideas for optimizations in my head, but for now this wasn't priority. For diploma thesis I need at least working SPI and I will work on these optimizations later .
  9. Like
    HanzZ got a reaction from xpg in QSimKit - MSP430 simulator   
    Hi,
     
    as my diploma thesis I'm writting MSP430 simulator called QSimKit. It's not finished yet, but it's in state when it's starting to be useful and I would like to get more people to test it, share their opinions, find bugs and basically to create community of people interested in MSP430 simulation.
     
    Releases:
    Version 0.0.3 (2014-02-04), Changelog At first some facts about QSimKit:
    It's written under GPLv2+ in C++/Qt, has been tested on Linux or Windows together with msp430gcc. It supports peripherals (as plugins) written in C++ or Python. Currently there's LED, oscillator, button and HD44708 LCD (not fully implemented yet). MCUs are plugins too and theoretically it's possible to add support for more MCUs (not just MSP430). It can support all MSP430 variants, but only few are supported right now, because I haven't created package data for all MSP430 variants yet. In graphical user interface (Check screenshot), you can do following:
    Add peripherals, connect them to MCU. See the source code of program you are simulating together with Dwarf debugging data (you can see the value of local variables for example) and current instruction. Step the simulation, add breakpoints based on PC register or value of memory. Track pins in oscilloscope-like view. See the registers and other important values from MCU (frequency, BasicClock registers, ...) MSP430 MCU plugin can do following:
    Load ELF/A43 code. Supports all instructions. Supports BasicClock module (TImerA/TimerB). Support for USCI-SPI [NEW in 0.0.3] Support for USART-SPI [NEW in 0.0.3] Initial USI support (just SPI mode). Peripherals:
    Button LCD - HD44708 (only initial support) LED Crystal Oscillator SD Card (only initial support) [NEW in 0.0.2]  
    As I stated earlier, it's not finished yet, but some testers to help me testing are welcome. I can also help anyone who would like to help with development. There is no development documentation yet, but if you tell me what you would like to do, I can write relevant docs to help you.
     
    If you think you have found a bug or you have some feature request, please create ticket on GitHub, I don't want this forum thread to be an issue tracker. You can also find me on IRC in #qsimkit at freenode or as HanzZ in #43oh channel.
  10. Like
    HanzZ got a reaction from dannyboy in QSimKit - MSP430 simulator   
    Hi,
     
    as my diploma thesis I'm writting MSP430 simulator called QSimKit. It's not finished yet, but it's in state when it's starting to be useful and I would like to get more people to test it, share their opinions, find bugs and basically to create community of people interested in MSP430 simulation.
     
    Releases:
    Version 0.0.3 (2014-02-04), Changelog At first some facts about QSimKit:
    It's written under GPLv2+ in C++/Qt, has been tested on Linux or Windows together with msp430gcc. It supports peripherals (as plugins) written in C++ or Python. Currently there's LED, oscillator, button and HD44708 LCD (not fully implemented yet). MCUs are plugins too and theoretically it's possible to add support for more MCUs (not just MSP430). It can support all MSP430 variants, but only few are supported right now, because I haven't created package data for all MSP430 variants yet. In graphical user interface (Check screenshot), you can do following:
    Add peripherals, connect them to MCU. See the source code of program you are simulating together with Dwarf debugging data (you can see the value of local variables for example) and current instruction. Step the simulation, add breakpoints based on PC register or value of memory. Track pins in oscilloscope-like view. See the registers and other important values from MCU (frequency, BasicClock registers, ...) MSP430 MCU plugin can do following:
    Load ELF/A43 code. Supports all instructions. Supports BasicClock module (TImerA/TimerB). Support for USCI-SPI [NEW in 0.0.3] Support for USART-SPI [NEW in 0.0.3] Initial USI support (just SPI mode). Peripherals:
    Button LCD - HD44708 (only initial support) LED Crystal Oscillator SD Card (only initial support) [NEW in 0.0.2]  
    As I stated earlier, it's not finished yet, but some testers to help me testing are welcome. I can also help anyone who would like to help with development. There is no development documentation yet, but if you tell me what you would like to do, I can write relevant docs to help you.
     
    If you think you have found a bug or you have some feature request, please create ticket on GitHub, I don't want this forum thread to be an issue tracker. You can also find me on IRC in #qsimkit at freenode or as HanzZ in #43oh channel.
  11. Like
    HanzZ got a reaction from bluehash in QSimKit - MSP430 simulator   
    Hi,
     
    as my diploma thesis I'm writting MSP430 simulator called QSimKit. It's not finished yet, but it's in state when it's starting to be useful and I would like to get more people to test it, share their opinions, find bugs and basically to create community of people interested in MSP430 simulation.
     
    Releases:
    Version 0.0.3 (2014-02-04), Changelog At first some facts about QSimKit:
    It's written under GPLv2+ in C++/Qt, has been tested on Linux or Windows together with msp430gcc. It supports peripherals (as plugins) written in C++ or Python. Currently there's LED, oscillator, button and HD44708 LCD (not fully implemented yet). MCUs are plugins too and theoretically it's possible to add support for more MCUs (not just MSP430). It can support all MSP430 variants, but only few are supported right now, because I haven't created package data for all MSP430 variants yet. In graphical user interface (Check screenshot), you can do following:
    Add peripherals, connect them to MCU. See the source code of program you are simulating together with Dwarf debugging data (you can see the value of local variables for example) and current instruction. Step the simulation, add breakpoints based on PC register or value of memory. Track pins in oscilloscope-like view. See the registers and other important values from MCU (frequency, BasicClock registers, ...) MSP430 MCU plugin can do following:
    Load ELF/A43 code. Supports all instructions. Supports BasicClock module (TImerA/TimerB). Support for USCI-SPI [NEW in 0.0.3] Support for USART-SPI [NEW in 0.0.3] Initial USI support (just SPI mode). Peripherals:
    Button LCD - HD44708 (only initial support) LED Crystal Oscillator SD Card (only initial support) [NEW in 0.0.2]  
    As I stated earlier, it's not finished yet, but some testers to help me testing are welcome. I can also help anyone who would like to help with development. There is no development documentation yet, but if you tell me what you would like to do, I can write relevant docs to help you.
     
    If you think you have found a bug or you have some feature request, please create ticket on GitHub, I don't want this forum thread to be an issue tracker. You can also find me on IRC in #qsimkit at freenode or as HanzZ in #43oh channel.
  12. Like
    HanzZ got a reaction from multivac in QSimKit - MSP430 simulator   
    Hi,
     
    as my diploma thesis I'm writting MSP430 simulator called QSimKit. It's not finished yet, but it's in state when it's starting to be useful and I would like to get more people to test it, share their opinions, find bugs and basically to create community of people interested in MSP430 simulation.
     
    Releases:
    Version 0.0.3 (2014-02-04), Changelog At first some facts about QSimKit:
    It's written under GPLv2+ in C++/Qt, has been tested on Linux or Windows together with msp430gcc. It supports peripherals (as plugins) written in C++ or Python. Currently there's LED, oscillator, button and HD44708 LCD (not fully implemented yet). MCUs are plugins too and theoretically it's possible to add support for more MCUs (not just MSP430). It can support all MSP430 variants, but only few are supported right now, because I haven't created package data for all MSP430 variants yet. In graphical user interface (Check screenshot), you can do following:
    Add peripherals, connect them to MCU. See the source code of program you are simulating together with Dwarf debugging data (you can see the value of local variables for example) and current instruction. Step the simulation, add breakpoints based on PC register or value of memory. Track pins in oscilloscope-like view. See the registers and other important values from MCU (frequency, BasicClock registers, ...) MSP430 MCU plugin can do following:
    Load ELF/A43 code. Supports all instructions. Supports BasicClock module (TImerA/TimerB). Support for USCI-SPI [NEW in 0.0.3] Support for USART-SPI [NEW in 0.0.3] Initial USI support (just SPI mode). Peripherals:
    Button LCD - HD44708 (only initial support) LED Crystal Oscillator SD Card (only initial support) [NEW in 0.0.2]  
    As I stated earlier, it's not finished yet, but some testers to help me testing are welcome. I can also help anyone who would like to help with development. There is no development documentation yet, but if you tell me what you would like to do, I can write relevant docs to help you.
     
    If you think you have found a bug or you have some feature request, please create ticket on GitHub, I don't want this forum thread to be an issue tracker. You can also find me on IRC in #qsimkit at freenode or as HanzZ in #43oh channel.
  13. Like
    HanzZ got a reaction from RobG in QSimKit - MSP430 simulator   
    Hi,
     
    as my diploma thesis I'm writting MSP430 simulator called QSimKit. It's not finished yet, but it's in state when it's starting to be useful and I would like to get more people to test it, share their opinions, find bugs and basically to create community of people interested in MSP430 simulation.
     
    Releases:
    Version 0.0.3 (2014-02-04), Changelog At first some facts about QSimKit:
    It's written under GPLv2+ in C++/Qt, has been tested on Linux or Windows together with msp430gcc. It supports peripherals (as plugins) written in C++ or Python. Currently there's LED, oscillator, button and HD44708 LCD (not fully implemented yet). MCUs are plugins too and theoretically it's possible to add support for more MCUs (not just MSP430). It can support all MSP430 variants, but only few are supported right now, because I haven't created package data for all MSP430 variants yet. In graphical user interface (Check screenshot), you can do following:
    Add peripherals, connect them to MCU. See the source code of program you are simulating together with Dwarf debugging data (you can see the value of local variables for example) and current instruction. Step the simulation, add breakpoints based on PC register or value of memory. Track pins in oscilloscope-like view. See the registers and other important values from MCU (frequency, BasicClock registers, ...) MSP430 MCU plugin can do following:
    Load ELF/A43 code. Supports all instructions. Supports BasicClock module (TImerA/TimerB). Support for USCI-SPI [NEW in 0.0.3] Support for USART-SPI [NEW in 0.0.3] Initial USI support (just SPI mode). Peripherals:
    Button LCD - HD44708 (only initial support) LED Crystal Oscillator SD Card (only initial support) [NEW in 0.0.2]  
    As I stated earlier, it's not finished yet, but some testers to help me testing are welcome. I can also help anyone who would like to help with development. There is no development documentation yet, but if you tell me what you would like to do, I can write relevant docs to help you.
     
    If you think you have found a bug or you have some feature request, please create ticket on GitHub, I don't want this forum thread to be an issue tracker. You can also find me on IRC in #qsimkit at freenode or as HanzZ in #43oh channel.
  14. Like
    HanzZ got a reaction from spirilis in QSimKit - MSP430 simulator   
    Hi,
     
    as my diploma thesis I'm writting MSP430 simulator called QSimKit. It's not finished yet, but it's in state when it's starting to be useful and I would like to get more people to test it, share their opinions, find bugs and basically to create community of people interested in MSP430 simulation.
     
    Releases:
    Version 0.0.3 (2014-02-04), Changelog At first some facts about QSimKit:
    It's written under GPLv2+ in C++/Qt, has been tested on Linux or Windows together with msp430gcc. It supports peripherals (as plugins) written in C++ or Python. Currently there's LED, oscillator, button and HD44708 LCD (not fully implemented yet). MCUs are plugins too and theoretically it's possible to add support for more MCUs (not just MSP430). It can support all MSP430 variants, but only few are supported right now, because I haven't created package data for all MSP430 variants yet. In graphical user interface (Check screenshot), you can do following:
    Add peripherals, connect them to MCU. See the source code of program you are simulating together with Dwarf debugging data (you can see the value of local variables for example) and current instruction. Step the simulation, add breakpoints based on PC register or value of memory. Track pins in oscilloscope-like view. See the registers and other important values from MCU (frequency, BasicClock registers, ...) MSP430 MCU plugin can do following:
    Load ELF/A43 code. Supports all instructions. Supports BasicClock module (TImerA/TimerB). Support for USCI-SPI [NEW in 0.0.3] Support for USART-SPI [NEW in 0.0.3] Initial USI support (just SPI mode). Peripherals:
    Button LCD - HD44708 (only initial support) LED Crystal Oscillator SD Card (only initial support) [NEW in 0.0.2]  
    As I stated earlier, it's not finished yet, but some testers to help me testing are welcome. I can also help anyone who would like to help with development. There is no development documentation yet, but if you tell me what you would like to do, I can write relevant docs to help you.
     
    If you think you have found a bug or you have some feature request, please create ticket on GitHub, I don't want this forum thread to be an issue tracker. You can also find me on IRC in #qsimkit at freenode or as HanzZ in #43oh channel.
  15. Like
    HanzZ got a reaction from dubnet in QSimKit - MSP430 simulator   
    Hi,
     
    as my diploma thesis I'm writting MSP430 simulator called QSimKit. It's not finished yet, but it's in state when it's starting to be useful and I would like to get more people to test it, share their opinions, find bugs and basically to create community of people interested in MSP430 simulation.
     
    Releases:
    Version 0.0.3 (2014-02-04), Changelog At first some facts about QSimKit:
    It's written under GPLv2+ in C++/Qt, has been tested on Linux or Windows together with msp430gcc. It supports peripherals (as plugins) written in C++ or Python. Currently there's LED, oscillator, button and HD44708 LCD (not fully implemented yet). MCUs are plugins too and theoretically it's possible to add support for more MCUs (not just MSP430). It can support all MSP430 variants, but only few are supported right now, because I haven't created package data for all MSP430 variants yet. In graphical user interface (Check screenshot), you can do following:
    Add peripherals, connect them to MCU. See the source code of program you are simulating together with Dwarf debugging data (you can see the value of local variables for example) and current instruction. Step the simulation, add breakpoints based on PC register or value of memory. Track pins in oscilloscope-like view. See the registers and other important values from MCU (frequency, BasicClock registers, ...) MSP430 MCU plugin can do following:
    Load ELF/A43 code. Supports all instructions. Supports BasicClock module (TImerA/TimerB). Support for USCI-SPI [NEW in 0.0.3] Support for USART-SPI [NEW in 0.0.3] Initial USI support (just SPI mode). Peripherals:
    Button LCD - HD44708 (only initial support) LED Crystal Oscillator SD Card (only initial support) [NEW in 0.0.2]  
    As I stated earlier, it's not finished yet, but some testers to help me testing are welcome. I can also help anyone who would like to help with development. There is no development documentation yet, but if you tell me what you would like to do, I can write relevant docs to help you.
     
    If you think you have found a bug or you have some feature request, please create ticket on GitHub, I don't want this forum thread to be an issue tracker. You can also find me on IRC in #qsimkit at freenode or as HanzZ in #43oh channel.
  16. Like
    HanzZ got a reaction from roadrunner84 in QSimKit - MSP430 simulator   
    Hi,
     
    as my diploma thesis I'm writting MSP430 simulator called QSimKit. It's not finished yet, but it's in state when it's starting to be useful and I would like to get more people to test it, share their opinions, find bugs and basically to create community of people interested in MSP430 simulation.
     
    Releases:
    Version 0.0.3 (2014-02-04), Changelog At first some facts about QSimKit:
    It's written under GPLv2+ in C++/Qt, has been tested on Linux or Windows together with msp430gcc. It supports peripherals (as plugins) written in C++ or Python. Currently there's LED, oscillator, button and HD44708 LCD (not fully implemented yet). MCUs are plugins too and theoretically it's possible to add support for more MCUs (not just MSP430). It can support all MSP430 variants, but only few are supported right now, because I haven't created package data for all MSP430 variants yet. In graphical user interface (Check screenshot), you can do following:
    Add peripherals, connect them to MCU. See the source code of program you are simulating together with Dwarf debugging data (you can see the value of local variables for example) and current instruction. Step the simulation, add breakpoints based on PC register or value of memory. Track pins in oscilloscope-like view. See the registers and other important values from MCU (frequency, BasicClock registers, ...) MSP430 MCU plugin can do following:
    Load ELF/A43 code. Supports all instructions. Supports BasicClock module (TImerA/TimerB). Support for USCI-SPI [NEW in 0.0.3] Support for USART-SPI [NEW in 0.0.3] Initial USI support (just SPI mode). Peripherals:
    Button LCD - HD44708 (only initial support) LED Crystal Oscillator SD Card (only initial support) [NEW in 0.0.2]  
    As I stated earlier, it's not finished yet, but some testers to help me testing are welcome. I can also help anyone who would like to help with development. There is no development documentation yet, but if you tell me what you would like to do, I can write relevant docs to help you.
     
    If you think you have found a bug or you have some feature request, please create ticket on GitHub, I don't want this forum thread to be an issue tracker. You can also find me on IRC in #qsimkit at freenode or as HanzZ in #43oh channel.
  17. Like
    HanzZ got a reaction from Automate in QSimKit - MSP430 simulator   
    Hi,
     
    as my diploma thesis I'm writting MSP430 simulator called QSimKit. It's not finished yet, but it's in state when it's starting to be useful and I would like to get more people to test it, share their opinions, find bugs and basically to create community of people interested in MSP430 simulation.
     
    Releases:
    Version 0.0.3 (2014-02-04), Changelog At first some facts about QSimKit:
    It's written under GPLv2+ in C++/Qt, has been tested on Linux or Windows together with msp430gcc. It supports peripherals (as plugins) written in C++ or Python. Currently there's LED, oscillator, button and HD44708 LCD (not fully implemented yet). MCUs are plugins too and theoretically it's possible to add support for more MCUs (not just MSP430). It can support all MSP430 variants, but only few are supported right now, because I haven't created package data for all MSP430 variants yet. In graphical user interface (Check screenshot), you can do following:
    Add peripherals, connect them to MCU. See the source code of program you are simulating together with Dwarf debugging data (you can see the value of local variables for example) and current instruction. Step the simulation, add breakpoints based on PC register or value of memory. Track pins in oscilloscope-like view. See the registers and other important values from MCU (frequency, BasicClock registers, ...) MSP430 MCU plugin can do following:
    Load ELF/A43 code. Supports all instructions. Supports BasicClock module (TImerA/TimerB). Support for USCI-SPI [NEW in 0.0.3] Support for USART-SPI [NEW in 0.0.3] Initial USI support (just SPI mode). Peripherals:
    Button LCD - HD44708 (only initial support) LED Crystal Oscillator SD Card (only initial support) [NEW in 0.0.2]  
    As I stated earlier, it's not finished yet, but some testers to help me testing are welcome. I can also help anyone who would like to help with development. There is no development documentation yet, but if you tell me what you would like to do, I can write relevant docs to help you.
     
    If you think you have found a bug or you have some feature request, please create ticket on GitHub, I don't want this forum thread to be an issue tracker. You can also find me on IRC in #qsimkit at freenode or as HanzZ in #43oh channel.
  18. Like
    HanzZ got a reaction from oPossum in QSimKit - MSP430 simulator   
    Hi,
     
    as my diploma thesis I'm writting MSP430 simulator called QSimKit. It's not finished yet, but it's in state when it's starting to be useful and I would like to get more people to test it, share their opinions, find bugs and basically to create community of people interested in MSP430 simulation.
     
    Releases:
    Version 0.0.3 (2014-02-04), Changelog At first some facts about QSimKit:
    It's written under GPLv2+ in C++/Qt, has been tested on Linux or Windows together with msp430gcc. It supports peripherals (as plugins) written in C++ or Python. Currently there's LED, oscillator, button and HD44708 LCD (not fully implemented yet). MCUs are plugins too and theoretically it's possible to add support for more MCUs (not just MSP430). It can support all MSP430 variants, but only few are supported right now, because I haven't created package data for all MSP430 variants yet. In graphical user interface (Check screenshot), you can do following:
    Add peripherals, connect them to MCU. See the source code of program you are simulating together with Dwarf debugging data (you can see the value of local variables for example) and current instruction. Step the simulation, add breakpoints based on PC register or value of memory. Track pins in oscilloscope-like view. See the registers and other important values from MCU (frequency, BasicClock registers, ...) MSP430 MCU plugin can do following:
    Load ELF/A43 code. Supports all instructions. Supports BasicClock module (TImerA/TimerB). Support for USCI-SPI [NEW in 0.0.3] Support for USART-SPI [NEW in 0.0.3] Initial USI support (just SPI mode). Peripherals:
    Button LCD - HD44708 (only initial support) LED Crystal Oscillator SD Card (only initial support) [NEW in 0.0.2]  
    As I stated earlier, it's not finished yet, but some testers to help me testing are welcome. I can also help anyone who would like to help with development. There is no development documentation yet, but if you tell me what you would like to do, I can write relevant docs to help you.
     
    If you think you have found a bug or you have some feature request, please create ticket on GitHub, I don't want this forum thread to be an issue tracker. You can also find me on IRC in #qsimkit at freenode or as HanzZ in #43oh channel.
×
×
  • Create New...