ATC_TLSR_Paper
ATC_TLSR_Paper copied to clipboard
atc1441
Hanshow Nebular
Did someone already got hands on Nebular devices?
They are popping up in stores around here. They've got BW/Yellow and BW/Red. Also there a ones which are big, like a DinA5 sheet...
Hey. The 3.5" ones are directly compatible and will also do Bluetooth :)
Included the general files today but the display itself still needs the correct custom driving, different resolution and different custom LUT for fast updates
Hey. The 3.5" ones are directly compatible and will also do Bluetooth :)
Included the general files today but the display itself still needs the correct custom driving, different resolution and different custom LUT for fast updates
Do these devices have a proper Antenna for bluetooth?
I read some docs about the product, and there was a NFC interface mentioned. Is it's just NFC or also WiFi?
@lippe-digital did you try to flash your nebular device successfully?
No. Didn't have time to get my hands on yet. But I'm really eager to figure it out.
Now it worked for me.. The soldered battery was may in the meantime quite low on voltage. So I removed it and sourced the nebular with the 3V3 from UART Adapter. The BLE Device is now appearing :). I will look at the source code next days, the display size/orientation not matches for my target.
I guess I was also able to flash the firmware via the web flasher, at least the LED blinked blue during flashing. Aside from that would you expect anything to work? Like should a "soft reset MCU" clear the display or anything?
After intial flashing and a power on reset there is a test routine which writes the whole display black and write for a fee cycles... And then this appear..
So you should see something displayed/changed after a reset
Nice to see something working out.
The Nebular ones are very very beta or even Alpha, please do not expect it to work usable.
It is just a POC to see the Basics(BLE, Flashing) working :)
thanks for the good work. I did not expect anything at this early stage, I'm just wondering why it does not seem to do anything at all in my case. flashing looks good, at least the LED is blue when sending stuff (I did send the unlock flash command), but then it does not show up as BLE device and does not change the display. FWIW this is a Nebular 350-RN. Looks like there are different revisions, my pin out is slightly different from the one shown in this thread. I have a second one that has a display attached (and cleaner soldering :) ). SWS is connected to UART TX, RST to UART RTS, VCC to 3V3, GND to GND. that should be correct, right? I also tried with RST unconnected. RST vs NRST in the other pin outs? anything obviously wrong with the wiring?
I think your wiring is correct.. Did you unlock and ERASE the flash memory like described in the youtube video?
I did. I don't know why, but it did not work with my flipper zero but did work with a bus pirate. Now I find the device in the BLE app and see output on the display :+1:
I did. I don't know why, but it did not work with my flipper zero but did work with a bus pirate. Now I find the device in the BLE app and see output on the display 👍
Had the same issue with a Flipper Zero. My FT232 did the trick though. Did you manage to upload something to the display?
This is my Hanshow Nebular 213R-N:
Did you manage to upload something to the display?
I only uploaded the initial firmware which then displayed the clock and the the device showed up as BLE device, but that is where I stopped to let others do the actual work :). Refresh did not really work and the display size was wrong, but that is AFAIK currently all expected.
I have more succes with the Nebular 154. Unfortunately the screen was cracked, but it shows the clock partially. I can't get it to fill the complete display just like @tobiasdroessler I even tried to changed the value's in epd.h to match the resolution of the Nebular 154
#define epd_height 200
#define epd_width 200
@atc1441 Why is the UART output garbled of a flashed device? Only connected the VCC, GND and TX-to-RX to my UART adapter at 115200bps
Is it possible that we need a weak pull-up resistor on the SWS when programming ? I'm seeing the LED on the Nebular flashing when I'm using the serial programmer - but it doesn't look like the Nebular is obeying the commands. Even the "Soft Reset MCU" button doesn't appear to do anything on the Nebular (other than flash the LED). So, something still isn't working with the Nebular.
Hi Thomas.. you should check the battery voltage.. and/or supply the device from your Uart adapter. I had problems because of a low battery and removed it, then it worked.
Connected UART Adapters in not supplied state will also drain the battery over days.
Hi tobiasdroessler . Thank for your prompt reply. I did remove the battery, and sourced the 3V3 from the CH340 USB/UART adaptor. But, still doesn't appear to be programming the Nebular.
- Hi Thomas.. you should check the battery voltage.. and/or supply the device from your Uart adapter. I had problems because of a low battery and removed it, then it worked.
Connected UART Adapters in not supplied state will also drain the battery over days.
I think the reset is needed just before flashing. Did you connected the RTS to the reset pin?
May your adapter not work as intended and the reset is not done. You could also issue a reset manually before click the flash button... more info may atc can provide.
My CH340 USB/UART adaptor doesn't have a RTS pin! There are 6 pins, labelled GND, CTS, VCC, TXD, RXD, DTR.
I've used GND, CTS, VCC and TXD. The CTS on the CH340 is connected to RST on the Hanshow Nebular. I don't know if that is correct though.
Oh I my opinion CTS is an input Signal for your Uart device.. So that should not work to force an reset.
@atc1441 Do you have any recommendations when there is no RTS on your adapter?
I'm using the Hanshow Nebular 350R-N . And, I'm looking at the EPD_BWR_350_detect function. It's trying to write 0xA5 in to 153 bytes of storage locations, and then read them back. I'm presuming this is to test that there are that many bytes of storage available - and from that we can determine the model. Well, unfortunately, the read-back is failing at byte number zero. So, it's failing to write 0xA5 in to any of the locations. Is this a symptom of a bigger problem for the Hanshow Nebular 350R-N ?
I suspect the GPIO pin configuration is all different for the Hanshow Nebular.
It would be nice to get hold of the Data Sheet for the Hanshow "HS9118 A6100". I understand that it has an embedded TLSR8359 chip. My current problem is that I think the GPIO assignment in main.h isn't valid for the Nebular 350R-N, and I don't know enough to reverse engineer from the hardware.
As usual there is no datasheet available, but the pinout is the same :)
Actually, it's these pin settings that I'm querying - from main.h : #define EPD_RESET GPIO_PD4 #define EPD_DC GPIO_PD7 #define EPD_BUSY GPIO_PA1 #define EPD_CS GPIO_PB4 #define EPD_CLK GPIO_PB5 #define EPD_MOSI GPIO_PB6 #define EPD_ENABLE GPIO_PC5
The code to read the battery power and battery temperature is working fine - but the SPI comms to the display aren't working. So, I'm wondering if those GPIO pins are different on the Nebular series.
The pinout is the same. But again, there is still work needed to get it fully running. Sorry for being so short on that but its how it is currently