GitXplorerGitXplorer
p

mini-os-LM3S6965EVB

public
1 stars
1 forks
0 issues

Commits

List of commits on branch master.
Unverified
66853bc3793b8c28ed59c949867c126ec30251ec

write readme in english, remove docs

ppgimalac committed 4 years ago
Unverified
2c6004d38ce547395f9567739166054b763aa664

use clang-format to prettify

ppgimalac committed 4 years ago
Unverified
21a976e86725880c0b0ea016cd43656018fd3025

correction of filesystem and the two tests procs

ppgimalac committed 5 years ago
Unverified
de91334a8cd37e4c1fef19f44d7c99158c7824e5

merge

ppgimalac committed 5 years ago
Unverified
71bff36e04648da782c8c7ae9117973f81306975

add .gitattributes to avoid wrong langage stats

ppgimalac committed 5 years ago
Unverified
4e5c85abb1d3840bfb2a481cfe1c157927c59091

add licence, update readme, add sources, add assets

ppgimalac committed 5 years ago

README

The README file for this repository.

mini-os LM3S6965EVB

Informations

This project was realised as a two week long end of the (first) year project at Telecom Paris.

It was supervised by Guillaume Duc.

Project

The objective of the project was to write a minimalistic OS on a Luminary Micro Stellaris LM3S6965EVB equipped with a ARM Cortex-M3 processor.

There wasn't a list of things to do and it was the first year such a project was attempted so it was a little bit improvised over the two weeks.

Dependencies

The project uses Qemu (as it occurred during a lock-down and the chip wasn't available for testing) to launch.

At first the official QEMU System ARM version was used, but to implement a small file system some RAM was added between the addresses 0xF0000000 and 0xF0A00000. To do so you must modify the file hw/arm/stellaris.c in the QEMU repository, then compile and install.

The GCC arm-none-eabi tool chain was used to compile and debug the project.

Final state

By the end of the project the processus handling and sequencing were working fine.

System calls work rather fine but no intensive test was made. fork doesn't work.

The file system was almost not tested and thus may be filled with bugs but it seemed to work fine in the few tests realised.

Processes are constantly with high priviledges.

Nothing was optimised, as speed was not the objective of the project.

Significant issue

A small part of memory seemed to take longer to access, causing one process (the one that had its RAM in this region) to be slower. No explanation was found.