How to Enable SEND_POSTANDGET on BK7231N/T and Compile Custom Firmware

I have several different paltforms. Mostly based on BK7231N/T but also others.

It seems to be, I can run command sendPOST http://Router_name/Temp.php?Device_name and it does run the PHP code Temp.php on the router and passes parameter Device_name to it just fine. It works as expected and makes it possible to trigger cool things depending on what happens on the OpenBK device.

But - it does only work by default on my ESP8266 device. The command seems to be commented out from other platforms I have.

I would like to turn it on for the rest of them and I have a couple questions about it.

I know there seems to be some documentation here: https://www.elektroda.com/news/news4033833.html but I did not quite understand how it is supposed to work.

Do I download the github code on my own computer, edit it, and somehow make remote computer to compile the code on my own PC. Or how is it supposed to work?

An other question is, the obk_config.h file has an exact section "PLATFORM_LN882H" and it has section "//#define ENABLE_SEND_POSTANDGET 1" to edit, but there seems not to be an an exact section for BK7231N or BK7231T. What should I edit to enable SEND_POSTANDGET for these two palforms?

B.T.W: my Temp.php looks like this




in case someone else would like to know. It's an OpenWRT router having PHP installed.

There is no need to download anything. Just fork repository, edit obk_config.h and open a PR. It could even work without PR, but I am not sure, as I never tried it from the contributor side. @divadiow ?

You need to make sure that the desired define exists in the target platform section. If that's not present, add it. So, if you want to have ENABLE_SEND_POSTANDGET on , let's say, BL602, you must find where BL602 section begins and add #define ENABLE_SEND_POSTANDGET 1 there.

I don't recall when but I enabled workflows in my own fork so now only do a PR when there's something for your attention.

You could try pencil icon edit to a file on main and it'll just do a little Patch-1 fork? Sometimes I do this for small edits like in obk_config.h

maybe @Tilator go here https://github.com/openshwprojects/OpenBK7231T_App/blob/main/src/obk_config.h

and then:

I made a fork.

Then I changed header file even though I'm still not sure what section there is for BK7231N and *T devices. There isn't such section.

If I now make a pull reguest, what exactly happens? It sounds like it does not start any compiling.

I managed to make my first release, but it contains only two source code packages. Do I only need to wait now for it to compile or what?

Tilator wrote:

There isn't such section.

stick it under here

https://github.com/divadiow/OpenBK7231T_App/blob/main/src/obk_config.h#L232C1-L232C21

Tilator wrote:

If I now make a pull reguest, what exactly happens? It sounds like it does not start any compiling.

make a PR to the main repo and it should begin building under here https://github.com/openshwprojects/OpenBK7231T_App/actions

or it'll sit needing admin approval. I'm not sure of the reasons why some people's PRs need approval and others don't. Maybe something @p.kaczmarek2 sets

This is the most lenient GitHub setting:



Both T and N are under PLATFORM_BEKEN.

Thank you everybody. I'm amazed, I got it working!

So, is the POST/GET working for you now on futher platforms?

And in general.... I think now you can agree, it's very easy to build OBK.

p.kaczmarek2 wrote:

I think now you can agree, it's very easy to build OBK.

Of course it was obviously easy. If you just know a few things on top of the documentation.

For example it does not tell, if you make your own fork, you must make pull request from the original copy. Not from the copy you have done. I was not completely sure if it ruins something for everyone else while I make PR from the original and not from my own copy.

I have compiled something like various kernel files and OpenWRT before. I knew what to expect happening next. For someone totally new it's a different ball game.