Hi,

just a precision:
AE code goes to eeprom/page.x
firmware goes to firmware/function

Paul,
Upload seems not working on eeprom/page.x
however, interactive changes are ok.

Two workarounds:

   1. via a mounted ow filesystem (I use this method)
   2. or put manually hexadecimal content via the http interface
   you may output the compiled content is the correct format with the
   following command:
   hexdump  -v -e'32/1 "%02x" "\n"' rob.bin
   then copy paste the ouput in the page.0 field and click CHANGE

also replied in green below

Pascal

2010/3/10 Mr Robert Conway <[email protected]>

> Hi PAul,
> 1)  In normal operation does the contents of the uploaded file appear in
> the text window ? and then you press [change].   Knowing this would help me
> in fault finding.
>
yes it should, but seems not working for here.

>
> 2) Can the bin file you upload be on the client machine (win XP) ?
>
upload take the file from the browser context, can be windows/mac/nix

>
> 3) Pascal stated the AE file goes into the EEPROM Page0 ?
>
I confirm, AE generated code cannot replace firmware, it goes to eeprom

>
> rob
>
>
> ---- Paul Alfille <[email protected]> wrote:
> > On Tue, Mar 9, 2010 at 6:14 PM, Mr Robert Conway <[email protected]
> >wrote:
> >
> > > OK did some more testing,  If I type into the page0 area and [CHANGE]
> it
> > > saves it to the slave.  I think the problem is the [upload] as I now
> assume
> > > when you upload a file, its contents will appear in the Page0 text area
> then
> > > pressing [Change] will store it to the slave.
> > >
> > > Does anybody know how a file upload functions in owhttp.  Does it
> import
> > > the files data into the text box then you can write it to the device
> with
> > > the [Change] button. ?
> > >
> > > Could it be a security setting in my browser thats stops the file
> Upload
> > > functioning
> > >
> > >
> > > Rob
> > >
> > >
> > >
> > The Upload button uses the POST command. I've tested it extensively with
> > firefox and programmed my BAE0910 several times successfully with it.
> > Figuring out the details of the POST format took quite a bit of testing
> and
> > debugging.
> >
> > The code itself should go to firmware/function.
> >
> > Paul Alfille
>
>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Owfs-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>



-- 
Pascal
www.brain4home.eu
------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Reply via email to