| 14 Jan 2021 |
 therealprof | But you can certainly get rid of the middle man... | 21:50:00 |
 dirbaio | dcx not supported by nrf-hal tho :C | 21:51:20 |
 daschl | I've just tried to find it, looks like I need to set the register manually | 21:53:01 |
| dirbaio | you can also get the hardware to handle the cs pin for you | 21:54:18 |
| dirbaio | again not supported :( | 21:54:27 |
| dirbaio | In reply to @therealprof:matrix.org
That's the whole point of display-interface that it is easy to write optimized adapters without having to touch the display driver. ooh I see, you could implement WriteOnlyDataCommand on top of nrf-hal to do more optimized stuff
without going through embedded-hal::blocking::spi | 21:55:29 |
| dirbaio | nice! | 21:55:38 |
| daschl | ok looks like I need to dive much deeper into that whole subject ... funny thing is there is a ili9341 crate already but it doesn't work for the adafruit display .. | 21:57:28 |
| dirbaio | SPI timing is a pain :D | 21:57:54 |
| daschl | alright guys as usual thanks much for all your help | 21:58:29 |
| 15 Jan 2021 |
| daschl | 
Download Screenshot 2021-01-15 at 15.40.39.png | 14:40:51 |
| daschl | doing it manually looks much better | 14:40:58 |
| daschl | // Pin select for DCX signal
spim.pseldcx.write(|w| {
let w = unsafe { w.pin().bits(dc.pin()) }; // 02
let w = w.port().bit(false); // port 0
w.connect().connected()
});
// Pin select for chip select signal
spim.psel.csn.write(|w| {
let w = unsafe { w.pin().bits(cs.pin()) }; // 03
let w = w.port().bit(false); // port 0
w.connect().connected()
});
// number of command bytes before data
spim.dcxcnt.write(|w| unsafe { w.dcxcnt().bits(0x01) });
| 14:41:10 |
| daschl | now I combine the command and data and send it in one shot over SPI, d/c and cs pins are controlled by the nrf | 14:41:54 |
| daschl | it only works with spim3 though, 0-2 do neither support csn nor dcx | 14:42:17 |
| daschl | (just as an update for the reader who read the above and maybe is interested in a solution) | 14:43:22 |
| dirbaio | Nice! :D
so it was the display not liking the pause? | 17:15:34 |
| 18 Jan 2021 |
|  firefrommoonlight joined the room. | 11:07:30 |
| firefrommoonlight | Hey bros! Trying to broaden my horizons beyond Stm32. From the docs and product descriptions I've read, the nrf52 line appears to be focused on short-distance, low-power RF uses. Is this accurate? So, Stm32 is a good choice if you're not doing RF, and nrf if you are? Is the nrf53 too new to support a HAL? Thank you. | 11:08:45 |
| firefrommoonlight | * Hey bros! Trying to broaden my horizons beyond Stm32. From the docs and product descriptions I've read, the nrf52 line appears to be focused on short-distance, low-power RF uses. Is this accurate? So, Stm32 is a good choice if you're not doing RF, and nrf if you are? Is the nrf53 too new to support a HAL? Thank you. | 11:09:15 |
| therealprof | firefrommoonlight: nRF is indeed focused on on-lower RF. However they're super-flexible (compared to other series) so unless you need high computing power they're generally a very good choice. | 11:14:02 |
| firefrommoonlight | Thank you. I'd love to use one on a future project | 11:32:12 |
| 20 Jan 2021 |
 wassasin | firefrommoonlight: I believe the devkits for the nrf5340 will release sometime next month | 11:43:28 |
| wassasin | So I would wait for that at least | 11:44:11 |
| wassasin | Furthermore for starting out I would recommend using a simpler CPU, i.e. the nRF52840 | 11:45:46 |
| wassasin | The nrf5340 is a dual core CPU, and that comes with a lot of extra possible problems | 11:46:31 |
 f_punk | In reply to @wassasin:matrix.org
firefrommoonlight: I believe the devkits for the nrf5340 will release sometime next month They are already available, at least on mouser. I received one just yesterday | 11:48:35 |
| wassasin | Oh really? :D | 11:48:52 |
| wassasin | buy | 11:49:19 |
| wassasin | Has anyone here soldered a nrf by hand using a hot station? | 11:50:51 |
