Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing support for factory command set #4

Open
edgetriggered opened this issue Jul 3, 2023 · 6 comments
Open

Missing support for factory command set #4

edgetriggered opened this issue Jul 3, 2023 · 6 comments
Assignees
Labels
enhancement New feature or request

Comments

@edgetriggered
Copy link
Collaborator

This firmware currently only provides I2C register control, but it would be convenient if it served as a direct drop-in replacement firmware for devices relying on the factory command set. Close this issue when support for the factory command set has been added.

@edgetriggered edgetriggered added the enhancement New feature or request label Jul 3, 2023
@edgetriggered edgetriggered self-assigned this Jul 3, 2023
@RE-Specto
Copy link

Hi there! any chance seeing progress on this one? I've seen many that are currently hesitant on switching to the firmware, for it being a one-way ticket while loosing support fro original functionality.
not trying to hurry up or something, just curious of the current state..

@edgetriggered
Copy link
Collaborator Author

@RE-Specto Hello, I am not actively working on this issue. I was able to backup the factory firmware but I am not using it in any projects that would be useful for feature testing by comparison. This issue can be reassigned to anyone who is better able to take on the effort.

@RE-Specto
Copy link

got you. I was looking into it, however it seems beyond my knowledge of embedded coding. maybe if you document registers a little bit more, then I or perhaps somebody else can give it a try 🤔

@RE-Specto
Copy link

RE-Specto commented May 18, 2024

I have done some research on the subject, and found at1846_registers.md and AT1846S_programming_guide.pdf
(which are slightly inconsistent btw 🤷 )
those the registers to be used by i2c_read (PEEK) and i2c_write (POKE) right?
is the original functionality can be wrapped around those two commands with the appropriate register values, or anything else is required?

@edgetriggered
Copy link
Collaborator Author

There are differences between the AT1846S and RDA1846S programming guides, which accounts for the inconsistencies. Commands not implemented by sa8x8-fw may be implemented from scratch by refering to these programming guides or can also be reverse engineered through monitoring I²C transactions on the hardware or even disassembling factory firmware. Publicly available documents appear to be missing some important registers that radio manufacturers seem to know about so that may be a difficult option. The included Python example is derived from the factory firmware on MD-UV380.

@RE-Specto
Copy link

hmm.. thanks for the clarification. so appears that more research is required at the moment. indeed somewhat above my current expertise unfortunately. maybe one day I'll be able to setup the correct equipment for eavesdropping on the I²C bus, and can document my findings, but until then hopefully someone better equipped for the task can take over

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants