Starting into bare-metal drivers using a Teensy 4.0

Status
Not open for further replies.
L

Lockna

New Member
Hey!
So I want to start writing some bare-metal using my Teensy 4.0 development board.
I want to write them in Rust, to improve myself.

So, I guess, one of the first things I have to do, is to get a serial connection to the pc. So I can send data from and to the uC. Where should I start with this?
I have found the datasheet for the cpu and I'm reading in it
But, since there are multiple serial ports I don't know which one to choose. Should I use a hardware one, or should I go for the on in USB? (UART)

Are there any other things I should think of? do you know some good resources, to get into it?
I mean I probably have to read to understand mmio, usb, serial, uart etc.

Best regards
 
Lockna said:
Well yes, but that is not my intention
Click to expand...

So why even ask here? - you want to write code using an obscure and fairly unknown language, with little support - you're unlikely to find members here who have ever used it, or have any plans to.

If you want help with an obscure language you need to find a forum that specifically supports it.
 
I have played with the Teensy 3.6 and found the Arduino IDE an exceptional tool.. I gather from your response to Mike you want to write your own drivers.. Good luck with that, But even downloading the Arduino tools, all the details can be ripped direct from their code...

BUT!! as it worked so well I just used it...
 
Doesn't writing drivers need an operating system which kinda isn't bare metal!! Or are your drivers somehow different? I've written code on lots of different micros and never needed to write or obtain a driver.

Mike.
 
No, not bare metal drivers.
See, I write a Serial Driver, so the user can send a message via Serial.write or Serial.println whatever
So, the User don't have to interact with the hardware himself
 
We seem to have different ideas about what a driver is. To me, a driver allows an operating system to interact with hardware and a library is just convenient code you can include in your code. Not to worry, it's just semantics.

Mike.
 
Pommie said:
We seem to have different ideas about what a driver is. To me, a driver allows an operating system to interact with hardware and a library is just convenient code you can include in your code. Not to worry, it's just semantics.

Mike.
Click to expand...

Yes, I think he's got a wildly different idea of what a 'driver' might be?

However, it should basically be part of his programming system - and all he should need to write is something like the standard:

C: 
char getch(void)
{
    return EUSART1_Read();
}

void putch(char txData)
{
    EUSART1_Write(txData);
}
 
Lockna said:
I want to write them in Rust, to improve myself.
Click to expand...

I thought This was going to be a setup where he was waiting for someone to ask what the hell "Rust" is so he can go into shill-mode and and encourage all of us to get a copy and write our own "bare metal" code. So far, I'm wrong. But I'm patient.
 
gophert said:
I thought This was going to be a setup where he was waiting for someone to ask what the hell "Rust" is so he can go into shill-mode and and encourage all of us to get a copy and write our own "bare metal" code. So far, I'm wrong. But I'm patient.
Click to expand...
I tried once, but I used stainless steel so the code would never compile..
 
Status
Not open for further replies.

Similar threads

B
  • Question
problems with a miso line in spi comunication
Replies
17
Views
3K
Nigel Goodwin
S
  • Question
Need a support for IAR-STM8
Replies
1
Views
7K
rjenkinsgb
S
STM32F407 software trigger a one pulse timer using HAL
Replies
0
Views
8K
Si14
S
L
How can the Teensy Board use avr?
Replies
2
Views
5K
Lockna
L
S
  • Question
problem with reciving answer from sim800
Replies
2
Views
5K
STP.Asghari
S
Menu
Log in
Register
Cookies are required to use this site. You must accept them to continue using the site. Learn more…