Re: Teensy 4.1 Implementation

2022-08-23 Thread Shiny Saana
> Your board code should be setting the init-nsvtor property on > the armv7m object to 0x0020, if it isn't already. I'm going to add that property right away! > Yes, this would be in line with the way we use -kernel on other > M-profile board models. Got it! Thank you for correcting my under

Re: Teensy 4.1 Implementation

2022-08-23 Thread Peter Maydell
On Tue, 23 Aug 2022 at 15:00, Shiny Saana wrote: > From experimentation and dissasembly on the ROM, (located in 0x0020_), > the very first int (converted to BE) is "0x2020_1000" , which is located to > "OCRAM2", also referred as "ROM RAM" by the documentation, and the next int > is "0x0020_

Re: Teensy 4.1 Implementation

2022-08-23 Thread Shiny Saana
Thank you again for your time! I didn't know at all about the generic loader!! It feels to me that it will definitely be very useful in loading the Teensy image. (To give more background: the Teensy-Arduinon toolchain first compiles an .elf and then convert that to an Intex hex file. We can retri

Re: Teensy 4.1 Implementation

2022-08-23 Thread Peter Maydell
On Sun, 21 Aug 2022 at 01:05, Shiny Saana wrote: > I've been able to write an initial Teensy 4.1 machine, for now with > only the few important memory regions initialized, and successfully > ran some hand-written ARM code on it. Great, that's good progress! > The documentation ( https://www.pjrc

Re: Teensy 4.1 Implementation

2022-08-20 Thread Shiny Saana
Hello! Thank you all again for your initial guidance. I've been able to write an initial Teensy 4.1 machine, for now with only the few important memory regions initialized, and successfully ran some hand-written ARM code on it. I was wondering what your opinions might be for implementing the nex

Re: Teensy 4.1 Implementation

2022-08-16 Thread Alex Bennée
Shiny Saana writes: > Thank you very much for your answer! > > Apologies if I mess up the process of communicating via mailing lists, > it's my first time communicating via this channel. Don't worry about it - mailing lists are absolutely a good place to discuss things ahead of time. I suspect

Re: Teensy 4.1 Implementation

2022-08-16 Thread Peter Maydell
On Tue, 16 Aug 2022 at 10:59, Alex Bennée wrote: > Shiny Saana writes: > > I personally don't need any of the GPIO interfaces, but if needed > > by someone else, that could be a good second step to > > work on once that part of the board is implemented. > > Handling GPIOs in QEMU is fine (we have

Re: Teensy 4.1 Implementation

2022-08-15 Thread Shiny Saana
Thank you very much for your answer! Apologies if I mess up the process of communicating via mailing lists, it's my first time communicating via this channel. The project that requires me to implement this board in QEMU currently would require full USB interface and flash storage at the end of th

Re: Teensy 4.1 Implementation

2022-08-15 Thread Peter Maydell
On Sat, 13 Aug 2022 at 18:54, Shiny Saana wrote: > I'd like to implement support for emulating the teensy 4.1 board ( > https://www.pjrc.com/store/teensy41.html) to QEMU. > > I'm honestly quite lost as to where to start at the moment, since > I can't really find any emulated Cortex-M7 that would b

Teensy 4.1 Implementation

2022-08-13 Thread Shiny Saana
Hello! I'd like to implement support for emulating the teensy 4.1 board ( https://www.pjrc.com/store/teensy41.html) to QEMU. I'm honestly quite lost as to where to start at the moment, since I can't really find any emulated Cortex-M7 that would be close to that board already implemented. I asked