[GH-ISSUE #274] New firmware SOLUM? #707

Closed
opened 2026-03-20 18:12:01 +01:00 by sascha_hemi · 6 comments
Owner

Originally created by @ferrexevi on GitHub (Mar 17, 2024).
Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/274

I have SOLUM labels, and I flashed the WEMOS S2 mini with the NANO AP option. Despite that, I still have the same error, the tag is not flashed, and in the web interface it does not detect tags, I get the same "error" as before this firmware. Are they already supposed to be compatible? What would be the procedure? Why is this not working? What am I doing wrong?

Thanks for the time and effort!

thumbnail_IMG_9350
Captura de pantalla 2024-03-17 a las 12 21 06 a  m
Captura de pantalla 2024-03-17 a las 12 21 40 a  m
Captura de pantalla 2024-03-17 a las 12 22 09 a  m

Originally created by @ferrexevi on GitHub (Mar 17, 2024). Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/274 I have SOLUM labels, and I flashed the WEMOS S2 mini with the NANO AP option. Despite that, I still have the same error, the tag is not flashed, and in the web interface it does not detect tags, I get the same "error" as before this firmware. Are they already supposed to be compatible? What would be the procedure? Why is this not working? What am I doing wrong? Thanks for the time and effort! ![thumbnail_IMG_9350](https://github.com/jjwbruijn/OpenEPaperLink/assets/31113439/c1fb2b71-a4a8-4b45-bf8c-be066e75aeff) ![Captura de pantalla 2024-03-17 a las 12 21 06 a  m](https://github.com/jjwbruijn/OpenEPaperLink/assets/31113439/41a27bfb-a689-4285-b086-0f065a14dd60) ![Captura de pantalla 2024-03-17 a las 12 21 40 a  m](https://github.com/jjwbruijn/OpenEPaperLink/assets/31113439/23083e7f-92fb-41e6-97e5-361f752ddeef) ![Captura de pantalla 2024-03-17 a las 12 22 09 a  m](https://github.com/jjwbruijn/OpenEPaperLink/assets/31113439/10f8c5ba-6ee3-44fe-860d-185dae51bb46)
Author
Owner

@jjwbruijn commented on GitHub (Mar 17, 2024):

Support for SiliconLabs-based tags is not fully there yet. It's being worked on as we speak, please be patient

<!-- gh-comment-id:2002181262 --> @jjwbruijn commented on GitHub (Mar 17, 2024): Support for SiliconLabs-based tags is not fully there yet. It's being worked on as we speak, please be patient
Author
Owner

@jonasniesner commented on GitHub (Mar 17, 2024):

Do you want to use this tag as the AP? If yes, I recommend you to get an M2 one or a C6 for this, because this one will only be supported as a tag

<!-- gh-comment-id:2002322602 --> @jonasniesner commented on GitHub (Mar 17, 2024): Do you want to use this tag as the AP? If yes, I recommend you to get an M2 one or a C6 for this, because this one will only be supported as a tag
Author
Owner

@ferrexevi commented on GitHub (Mar 17, 2024):

Do you want to use this tag as the AP? If yes, I recommend you to get an M2 one or a C6 for this, because this one will only be supported as a tag

My goal is to be able to write to it, either as an AP or not, then once I can write, have an AP to manage them all from one point. Right now I just want to write and I thought that for this, an AP would be needed, if not, should I use the last tag flasher option? Will I be able to write with that? The last time it failed, this time I haven't tried it.

Would it be possible to obtain a connection diagram for this tag? Since it is missing a connection, I deduce that it is not the same as the one that appears in the image, since in the image it is an important pinout

Pin number 8 of this schematic is MOSI, and is required by ZBE, therefore that schematic does not make sense for this label in next image:

Captura de pantalla 2024-03-17 a las 12 23 27 p  m

My connection diagram is the following (Green line) (Exemple: pin 1 tag --> pin 34 Wemos):

IMG_9422

Based on this shcematic:

Captura de pantalla 2024-03-17 a las 7 10 11 p  m

Using the previous scheme and testing the TagFlasher option, everything seems to be going well, until reaching 100% this error appears:

TagFlasher

I also have a label from the SOLUM brand, model ELD58R2CRN, manufactured on July 05, 2023.

Which presents the following inscription in the pinouts:

thumbnail_IMG_9360

I try to provide as much information as possible, I am a newbie and I don't know how to proceed to do it in the most correct way possible, sorry. My intention with this is to have it compiled in the same thread, I hope there is no problem since they are two different models, but from the same SOLUM brand.

Thanks for the reply

<!-- gh-comment-id:2002385954 --> @ferrexevi commented on GitHub (Mar 17, 2024): > Do you want to use this tag as the AP? If yes, I recommend you to get an M2 one or a C6 for this, because this one will only be supported as a tag My goal is to be able to write to it, either as an AP or not, then once I can write, have an AP to manage them all from one point. Right now I just want to write and I thought that for this, an AP would be needed, if not, should I use the last tag flasher option? Will I be able to write with that? The last time it failed, this time I haven't tried it. Would it be possible to obtain a connection diagram for this tag? Since it is missing a connection, I deduce that it is not the same as the one that appears in the image, since in the image it is an important pinout Pin number 8 of this schematic is MOSI, and is required by ZBE, therefore that schematic does not make sense for this label in next image: ![Captura de pantalla 2024-03-17 a las 12 23 27 p  m](https://github.com/jjwbruijn/OpenEPaperLink/assets/31113439/f8430e6b-a4b5-4382-88d7-fba652ffb060) My connection diagram is the following (Green line) (Exemple: pin 1 tag --> pin 34 Wemos): ![IMG_9422](https://github.com/jjwbruijn/OpenEPaperLink/assets/31113439/bb2f0fe7-21e4-4107-b9c7-bec43a9b3014) Based on this shcematic: ![Captura de pantalla 2024-03-17 a las 7 10 11 p  m](https://github.com/jjwbruijn/OpenEPaperLink/assets/31113439/b6827337-dda9-4efb-99b4-bd68552a0964) Using the previous scheme and testing the TagFlasher option, everything seems to be going well, until reaching 100% this error appears: ![TagFlasher](https://github.com/jjwbruijn/OpenEPaperLink/assets/31113439/64910e7c-bcf9-42b2-9917-c27f245b1659) I also have a label from the SOLUM brand, model ELD58R2CRN, manufactured on July 05, 2023. Which presents the following inscription in the pinouts: ![thumbnail_IMG_9360](https://github.com/jjwbruijn/OpenEPaperLink/assets/31113439/0d114845-dc0f-4f27-b568-cc39cbeffe1b) I try to provide as much information as possible, I am a newbie and I don't know how to proceed to do it in the most correct way possible, sorry. My intention with this is to have it compiled in the same thread, I hope there is no problem since they are two different models, but from the same SOLUM brand. Thanks for the reply
Author
Owner

@jjwbruijn commented on GitHub (Mar 17, 2024):

Support for SiliconLabs-based tags is not fully there yet. It's being worked on as we speak, please be patient

Please read my previous reply

<!-- gh-comment-id:2002607393 --> @jjwbruijn commented on GitHub (Mar 17, 2024): > Support for SiliconLabs-based tags is not fully there yet. It's being worked on as we speak, please be patient Please read my previous reply
Author
Owner

@ferrexevi commented on GitHub (Mar 18, 2024):

Support for SiliconLabs-based tags is not fully there yet. It's being worked on as we speak, please be patient

Please read my previous reply

I read it, not only compatibility, it is ensuring that the connections are correct, of this model the only thing I have seen are pinouts registered as P0 25, P0 26, P027.... from the wiki of this site, they do not refer to MOSI , MISO etc...

Then the topic of tutorials, would the flashing procedure be the one mentioned? (when there is 100% compatibility). I also mentioned another model, it contains the pinout inscriptions, I hope it can help in some way.

Thank you for your comment

<!-- gh-comment-id:2003934291 --> @ferrexevi commented on GitHub (Mar 18, 2024): > > Support for SiliconLabs-based tags is not fully there yet. It's being worked on as we speak, please be patient > > Please read my previous reply I read it, not only compatibility, it is ensuring that the connections are correct, of this model the only thing I have seen are pinouts registered as P0 25, P0 26, P027.... from the wiki of this site, they do not refer to MOSI , MISO etc... Then the topic of tutorials, would the flashing procedure be the one mentioned? (when there is 100% compatibility). I also mentioned another model, it contains the pinout inscriptions, I hope it can help in some way. Thank you for your comment
Author
Owner

@stevew817 commented on GitHub (Jul 28, 2024):

For reference - Silicon Labs firmware is now out in the open, see https://github.com/OpenEPaperLink/Tag_FW_EFR32xG22

AP firmware for these tags will likely never happen - I don't feel like doing the work as it's much easier to just build a proper spaghetti AP. Therefore closing this issue. Further discussion on Silabs tags can happen on the repo linked above.

<!-- gh-comment-id:2254590839 --> @stevew817 commented on GitHub (Jul 28, 2024): For reference - Silicon Labs firmware is now out in the open, see https://github.com/OpenEPaperLink/Tag_FW_EFR32xG22 AP firmware for these tags will likely never happen - I don't feel like doing the work as it's much easier to just build a proper spaghetti AP. Therefore closing this issue. Further discussion on Silabs tags can happen on the repo linked above.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/OpenEPaperLink#707