-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
VSCP_TYPE_PROTOCOL_START_BLOCK - Message defined twice #10
Comments
You choose. If you load RAM from the flasj space is up to you. The ranges is defined for the different types. Where you put the code in the end is up to you. But in the hex file you read the address ranges should be used. Typical is fuses. They are often located in a special area and need other handling then ram/flash. |
btw When you send more than one memory type in one session the last checksum in activate new image should be the sum of all crc's for all blocks you sent to the device. |
Thanks for the hint! Thats quite important to know. BTW Ake do you still have a public demo daemon running somewhere? Just for testing purposes? And I realized that my vscp-helper dll for windows is outdated ... do you provide the dll somwhere and I could avoid installing visual studio stuff? Currently I try to live with the MSYS2 gcc compiler. |
ha ha, yes quite useful. tcp/ip interface demo: The old servers is no longer present. I will set one up on the demo server. i have later today vscp1.vscp.org admin/secret 9598 Demo server info is here and is mostly up to date. libhelper.dll: I will try to make a release of it as soon as I can. Things starting to stabelize a bit on that end now so it's time. |
btw. It is perfectly fine to load one memory type at the time also of course. Then the crc "is as before" |
Thanks! Do you think the connection establishment to vscp1.vscp.org:9598 with vscp-helper v15 will work? |
Yes it should work. |
I get connection timeouts. |
can be because there is nothing there yet to talk to... :) Will talke some days to fix it. |
VSCP_TYPE_PROTOCOL_START_BLOCK has the message definition table twice.
BTW how to use the abstract memory range definitions?
The text was updated successfully, but these errors were encountered: