Unihiker, an $80 single-board PC with 2.8“ touchscreen, quad-core ARM Cortex-A35
1–10 of 241 posts
Re: Unihiker, an $80 single-board PC with 2.8“ touchscreen, quad-core ARM Cortex-A35
#2Re: Unihiker, an $80 single-board PC with 2.8“ touchscreen, quad-core ARM Cortex-A35
#3Re: Unihiker, an $80 single-board PC with 2.8“ touchscreen, quad-core ARM Cortex-A35
#4https://www.unihiker.com/wiki/board-overview
Looks like a neat board, I could see making expansion modules that plug into the bottom and running like a IR blaster or other stuff off the SPI/UART bus.
Re: Unihiker, an $80 single-board PC with 2.8“ touchscreen, quad-core ARM Cortex-A35
#5Re: Unihiker, an $80 single-board PC with 2.8“ touchscreen, quad-core ARM Cortex-A35
#6If I want to program and debug real-time routines in the coprocessor, rather than using the built-in userspace drivers, how do I do that?
Re: Unihiker, an $80 single-board PC with 2.8“ touchscreen, quad-core ARM Cortex-A35
#7Re: Unihiker, an $80 single-board PC with 2.8“ touchscreen, quad-core ARM Cortex-A35
#8Link to the pin out of the bottom connector: https://www.unihiker.com/wiki/board-overview Looks like a neat board, I could see making expansion modules that plug into the bottom and running like a IR blaster or other stuff off the SPI/UART bus.
They really bury the lede here, awesome that there is already an ecosystem that exists for the edge connector.
Re: Unihiker, an $80 single-board PC with 2.8“ touchscreen, quad-core ARM Cortex-A35
#9The video says "No coding skills? No worries. Just write your code with ChatGPT."
Re: Unihiker, an $80 single-board PC with 2.8“ touchscreen, quad-core ARM Cortex-A35
#10The video says "No coding skills? No worries. Just write your code with ChatGPT."
I'm incredibly curious what the experience of trying to write code with ChatGPT is like, if you have no prior knowledge. Obviously, it's impossible for me (and most others reading this) to un-know everything and approach it with fresh eyes. Are there any good real-time videos of non-programmers using ChatGPT to write code? (seems like the best way to understand what it's like)