<re_irc>
<nihal.pasham> adamgreig: So, imxrt series come with "cortex-m" series cores and the imx8 includes"cortex-a and cortex-m" cores.
<re_irc>
<nihal.pasham> usually the imx8 chipset is used to run both linux and some mcu firmware on a single board
<re_irc>
<nihal.pasham> So, imxrt series come with "cortex-m" series cores and the imx8 includes "cortex-a and cortex-m" cores.
<re_irc>
<adamgreig> Aah, cool. Sorry, I don't know of any Rust stuff for imx8 then
starblue has quit [Ping timeout: 268 seconds]
starblue has joined #rust-embedded
starblue has quit [Quit: WeeChat 3.0]
thomas25- is now known as thomas25
m5zs7k has joined #rust-embedded
brazuca has joined #rust-embedded
brazuca has quit [Quit: Client closed]
crabbedhaloablut has quit [Ping timeout: 258 seconds]
crabbedhaloablut has joined #rust-embedded
dc740 has joined #rust-embedded
dc740 has quit [Remote host closed the connection]
dc740 has joined #rust-embedded
crabbedhaloablut has quit [Remote host closed the connection]
crabbedhaloablut has joined #rust-embedded
<re_irc>
<James Munns> nihal.pasham: If you do find one/make one, I'd be interested to hear about it! I have that chip on my "eventually would like to support" list for mnemos :D
<re_irc>
<James Munns> I've seen imx6 in bare metal rust, but not for the imx7 or 8 family yet.
<re_irc>
<James Munns> diondokter re: https://twitter.com/Geoxion/status/1564982924918784002, is the problem you need to know (in the bootloader?) where the VTOR will be? Or are you dynamically trying to build the VTOR somehow?
<re_irc>
<diondokter> James Munns: Yeah, building the VTOR dynamically. With normal interrupts you know ahead of time which ones are there, but in my case a library user can choose to expose a function and then that function has to be included in the VTOR at a predictable spot.
<re_irc>
<diondokter> If I could convince the linker to use something like the names for alphabetic ordering, then I'd almost have the solution
<re_irc>
<diondokter> So if that's possible, please let me know!
<re_irc>
<James Munns> I mean you could do something like "export.1", and have specific slots in the linker scropt
<re_irc>
<James Munns> * script
<re_irc>
<James Munns> but that doesn't help you if you don't always have all of them
<re_irc>
<adamgreig> The VTOR is the vector table offset register, are you talking about that or just about the vector table?
<re_irc>
<adamgreig> Or is it something else again...
<re_irc>
<diondokter> adamgreig: Oh right, of course that is what that means. I meaning just a custom function pointer table
<re_irc>
<diondokter> * I'm
<re_irc>
<adamgreig> Aah got it, to use for interrupt handlers or just a general table of function pointers?
<re_irc>
<diondokter> James Munns: Well, they aren't predefined and I want to make it super simple for users. So just put a macro attribute on the function and it's exported in the correct way
<re_irc>
<diondokter> Just general. It's for a bootloader to call into the app and vice versa
<re_irc>
<tigerdruid21> Hi everyone,
<re_irc>
For example if I have a I2C display and a I2C temperature & humidity sensor and any other I2C peripheral, how can I safely shared the I2C bus between all those peripherals?
<re_irc>
Is there a default safe way to share a bus between different devices?
<re_irc>
What the default or best way to do it in a rust safe way?
WSalmon has quit [Read error: Connection reset by peer]