gmane.comp.embedded.fx2lib.devel

[ fx2lib-Issues-2909385 ] segmentation fault

SourceForge.net — 2013-01-25T10:17:54

Issues item #2909385, was opened at 2009-12-05 11:45
Message generated for change (Comment added) made by maartenbrock
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1126193&aid=2909385&group_id=247216

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: segmentation fault

Initial Comment:
Receive segmentation fault from sdcclib due to a bad memory access when making fx2.lib.

Using sdcclib v1.2 and sdcc v2.9.0 on Mac OS X i386 (Snow Leopard v10.6.2).

Do not receive this error when using sdcclib for building other libraries, also for the FX2.

----------------------------------------------------------------------

Comment By: Maarten Brock (maartenbrock)
Date: 2013-01-25 02:17

Message:
Since the p

(no subject)

Tim michals — 2013-01-17T01:06:12

http://www.bbv-jugend.de/tmp/liketd.php !------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122712_______________________________________________
Fx2lib-devel mailing list
Fx2lib-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f< at >public.gmane.org
https://lists.sourceforge.net/lists/listinfo/fx2lib-devel

Re: FX2 firmware

Zohair Ahmad — 2012-05-01T00:36:09

Are you installing the driver that Cypress provides? You need to update the
driver inf with the VID/PID pair of the device your firmware loads up with.
Can you check and see if your device is even giving a VID/PID pair? In
device manager, you can go into the details tab and look under "Device
Instance ID" to see the VID/PID pair.

Zohair Ahmad


On Mon, Apr 30, 2012 at 9:12 PM, ANDRONIC BOANARIJESY <androjes-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org>wrote:

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
Fx2lib-devel mailing list
Fx2lib-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f< at >public.gmane.org
https://lists.sourceforge.net/l

Re: FX2 firmware

ANDRONIC BOANARIJESY — 2012-04-30T13:12:57

If you're using the Makefile under "fw" directory, You will get an ihx file
as output.


On Mon, Apr 30, 2012 at 1:10 PM, ANDRONIC BOANARIJESY <androjes-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org>wrote:

Re: FX2 firmware

ANDRONIC BOANARIJESY — 2012-04-30T13:10:29

Normally sdcv generates an ihx file. So, you need to convert it to hex file
using packihx before loading.
On Apr 30, 2012 12:09 PM, "Marco Casadio" <marco.casadio10-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> wrote:

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
Fx2lib-devel mailing list
Fx2lib-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f< at >public.gmane.org
https://lists.sourceforge.net/lists/listinfo/fx2lib-devel

Re: FX2 firmware

Marco Casadio — 2012-04-30T12:08:49

Thank you for your reply.

No, i generate a Hex file directly from a makefile with sdcc but the
options used are the same you've provided.

-Marco
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
Fx2lib-devel mailing list
Fx2lib-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f< at >public.gmane.org
https://lists.sourceforge.net/lists/listinfo/fx2lib-devel

Re: FX2 firmware

ANDRONIC BOANARIJESY — 2012-04-30T11:36:00

It works for me!!! I use the Cypress devBoard (CY3684)

Did you use the "packihx.exe" for converting *.ihx to *.hex?

Otherwise, ensure your compiler option fits with your target.
The default option :
DSCR_AREA?=-Wl"-b DSCR_AREA=0x3e00"
INT2JT?=-Wl"-b INT2JT=0x3f00"
CODE_SIZE?=--code-size 0x3c00
XRAM_SIZE?=--xram-size 0x0200
XRAM_LOC?=--xram-loc 0x3c00

On Mon, Apr 30, 2012 at 11:10 AM, Marco Casadio
<marco.casadio10-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org>wrote:

FX2 firmware

Marco Casadio — 2012-04-30T11:10:23

I've tried to build fx2-lib basic firmware from fw directory and the hex
file has been generated correctly. But, if i run this firmware on my FX2LP,
the device is not able to enumerate in the rigth way. In particular,
Windows says "USB Unknown device".
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
Fx2lib-devel mailing list
Fx2lib-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f< at >public.gmane.org
https://lists.sourceforge.net/lists/listinfo/fx2lib-devel

Re: View program size

Maarten Brock — 2012-04-23T21:14:17

Hello Andronic,


My apologies. On a second look it appears that it was me who replied 
off-list.

Maarten


------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2

Re: View program size

Maarten Brock — 2012-04-23T20:37:47

Hello Andronic,


No, I cannot, because on an FX2 they DO create a conflict. But SDCC was
not written for the FX2, but for the Intel 8051 instead. And the original
8051 has separate XRAM and separate CODE memory. So YOU must split the
memory using the --code-loc and --xdata-loc command line switches. And
while you're at it also supply SDCC with --code-size and --xdata-size so
it will warn of memory overflows.

Apart from reading the FX2 datsheets and the SDCC manual I advise you to
also read the original 8051 datasheet, a.k.a. the 8051 bible, to get
familiar with the architecture. Google it you will find it.

And please do not reply to me personally, but to the whole list so
everyone can benefit. If you want my personal guidance I expect you to pay
my salary.

Maarten



------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http:

Re: View program size

ANDRONIC BOANARIJESY — 2012-04-15T10:21:41

I can't see where are the code, xram sizes in my .mem file.
Could you show me?

################################################
firmware.mem
################################################
Internal RAM layout:
      0 1 2 3 4 5 6 7 8 9 A B C D E F
0x00:|0|0|0|0|0|0|0|0|a|a|a|a|a|a|a|Q|
0x10:|Q|Q| | | | | | | | | | | | | | |
0x20:|B|T|S|S|S|S|S|S|S|S|S|S|S|S|S|S|
0x30:|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|
0x40:|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|
0x50:|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|
0x60:|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|
0x70:|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|
0x80:|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|
0x90:|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|
0xa0:|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|
0xb0:|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|
0xc0:|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|
0xd0:|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|
0xe0:|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|
0xf0:|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|
0-3:Reg Banks, T:Bit regs, a-z:Data, B:Bits, Q:Overlay, I:iData, S:Stack,
A:Absolute

Stack starts at: 0x22 (sp set to 0x21) with 222 bytes available

Re: View program size

Maarten Brock — 2012-04-15T09:06:26

Hi,

Just open the .mem file.

Maarten




------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2

View program size

ANDRONIC BOANARIJESY — 2012-04-15T07:23:09

Hi everyone,

How can I see the program size (xram, code, data) on SDCC after compiling?

with Keil, we could see:
Program Size: data=90.0 xdata=4492 code=5455

Build target 'RAM'
assembling dscr.a51...
compiling fw.c...
Source\fw.c(34): warning C317: attempt to redefine macro '_IFREQ'
compiling device.c...
linking...
Program Size: data=90.0 xdata=4492 code=5455
[...]

Re: Isochronous Streaming Using LibUSB from FPGA

Vincent Pelletier — 2012-01-22T11:10:44

Hi.

<offtopic>
Sorry, this message is not properly threaded: I just happened to find the 
original thread in archives, and I cannot find a way to get relevant mail 
headers.
I hope this mail will catch original poster's attention.
</offtopic>

Nice to see someone using my python-libusb1 for isochronous with (some) 
success ! I must admit I haven't tested isochronous transfers support properly 
myself.

I have some comments on the python script from original post which might help 
improving the situation, if that's still relevant:
- You are creating one transfer object per actual transfer. You should
  probably reuse them instead by calling "newxfer.submit()" in
  SubmitThread.createDataThread. In turn, you should remove the infinite loop
  in SubmitThread.run, so that you only create a fixed amount of transfers,
  submit them, and do nothing (actually just looping over handleEvents()).
  In turn, this means you don't need to have 2 threads for creating transfers
  and handling events: just do that sequentia

Re: Setupdata at 0xe000

Maarten Brock — 2011-09-17T19:30:35

Hi,

Daniel wrote:

Ah yes, I forgot about this.

Chris wrote;

It works because the descriptors are initialized in assembly.


I admit I did not read further than 3.2 EZ-USB Startup Modes which 
states:
Note: Although the EZ-USB can perform C2 Loads from EEPROMs as large 
as 64 KB, code can only be downloaded to the 16K of on chip RAM.

On second thought I think "code" here means code space since 0xe000 
is xdata only. I had read it as 'binary data'.

Sorry for the noise,
Maarten

------------------------------------------------------------------------------
BlackBerry&reg; DevCon Americas, Oct. 18-20, San Francisco, CA
http://p.sf.net/sfu/rim-devcon-copy2

Re: Setupdata at 0xe000

Chris McClelland — 2011-09-17T08:35:26

Apologies, re-sending from correct account.

On Fri, 2011-09-16 at 21:55 +0200, Maarten Brock wrote:
My compile lines look like this:

sdcc -mmcs51 --code-size 0x3c00 --xram-size 0x0200 --xram-loc 0x3c00
-Wl"-b DSCR_AREA=0xe000" -Wl"-b INT2JT=0x3f00" -DEEPROM -c
--disable-warning 85 -I sdcc -I../../../3rd/fx2lib/include
-I../../../common firmware.c

And my link lines look like this:

sdcc -mmcs51 --code-size 0x3c00 --xram-size 0x0200 --xram-loc 0x3c00
-Wl"-b DSCR_AREA=0xe000" -Wl"-b INT2JT=0x3f00" -DEEPROM -o firmware.hex
app.rel firmware.rel infra.rel jtag.rel prom.rel sync.rel
descriptors.rel -L../../../3rd/fx2lib/lib fx2.lib

I tried a RAM-load and a 0xC2 EEPROM load. 

The final 0xC2 record for *code* does a load of 0x185 bytes at 0x21AB.
That is immediately followed by a 0xC2 record to load 0xB8 bytes of
xdata at 0x3f00, followed by a 0xC2 record to load 0xAC bytes of xdata
descriptors at 0xe000. This is naturally before any SDCC init code has
been called.

The init code I get from SDCC (2.9.0) looks li

Re: Setupdata at 0xe000

Chris McClelland — 2011-09-17T08:29:06

My compile lines look like this:

sdcc -mmcs51 --code-size 0x3c00 --xram-size 0x0200 --xram-loc 0x3c00
-Wl"-b DSCR_AREA=0x3e00" -Wl"-b INT2JT=0x3f00" -DEEPROM -c
--disable-warning 85 -I sdcc -I../../../3rd/fx2lib/include
-I../../../common firmware.c

And my link lines look like this:

sdcc -mmcs51 --code-size 0x3c00 --xram-size 0x0200 --xram-loc 0x3c00
-Wl"-b DSCR_AREA=0x3e00" -Wl"-b INT2JT=0x3f00" -DEEPROM -o firmware.hex
app.rel firmware.rel infra.rel jtag.rel prom.rel sync.rel
descriptors.rel -L../../../3rd/fx2lib/lib fx2.lib

I tried a RAM-load and a 0xC2 EEPROM load. 

The final 0xC2 record for *code* does a load of 0x185 bytes at 0x21AB.
That is immediately followed by a 0xC2 record to load 0xB8 bytes of
xdata at 0x3f00, followed by a 0xC2 record to load 0xAC bytes of xdata
descriptors at 0xe000. This is naturally before any SDCC init code has
been called.

The init code I get from SDCC (2.9.0) looks like this:

894 ;--------------------------------------------------------
895 ; global & static initial

Re: Setupdata at 0xe000

Chris McClelland — 2011-09-17T08:25:07

Evelyn the modified dog asks "why?"


Done. Works fine (I tested a RAM load and a 0xC2 EEPROM load, declared
xdata at 0x3e00 and 0xe000).


Thanks!



------------------------------------------------------------------------------
BlackBerry&reg; DevCon Americas, Oct. 18-20, San Francisco, CA
http://p.sf.net/sfu/rim-devcon-copy2

Re: Setupdata at 0xe000

Daniel O'Connor — 2011-09-17T01:55:17

On 17/09/2011, at 5:25, Maarten Brock wrote:

Yes, you can't put code there.


Hmm I didn't consider this, however I just examined the output file and I don't think it is doing that.
ie I did this..
gobjcopy -I ihex -O binary obj/ugsio.ihx obj/ugsio.bin
hexdump -Cv obj/ugsio.bin

and I see..
<snip>
0000e000  12 01 00 02 ff ff ff 40  53 47 01 00 01 00 01 02  |.......< at >SG......|
0000e010  04 01 0a 06 00 02 ff ff  ff 40 01 00 09 02 35 00  |.........< at >....5.|
<snip>
0000e080  07 05 08 02 00 02 00 00  04 03 09 04 22 03 47 00  |............".G.|
0000e090  65 00 6e 00 65 00 73 00  69 00 73 00 20 00 53 00  |e.n.e.s.i.s. .S.|
0000e0a0  6f 00 66 00 74 00 77 00  61 00 72 00 65 00 0c 03  |o.f.t.w.a.r.e...|
<snip>


I think it probably "just works" in this case because the descriptor table is defined in assembly and its address is forced in the linker.

Hence the declaration only affects how the C code accesses it.


I am using C2 mode, and the firmware is loaded into RAM using fxload.

EEPROM has a PID of 0xff01 and devd

Re: Setupdata at 0xe000

Daniel O'Connor — 2011-09-17T01:31:27

On 16/09/2011, at 22:43, Chris McClelland wrote:

Yes.


Hmm I'm not sure, I can't try it declared as __xdata at 0x3e00 because my code is too big :)


OK. can you try declaring it as __xdata but still at 0x3e00?


Yes, I changed them because my version of sdcc complains that code/xdata/etc is deprecated and you should use __code/__xdata/etc.

See this github pull request..
https://github.com/mulicheng/fx2lib/pull/2/files



Nice project :)

--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C







------------------------------------------------------------------------------
BlackBerry&reg; DevCon Americas, Oct. 18-20, San Francisco, CA
http://p.sf.net/sfu/rim-devcon-copy2

Re: Setupdata at 0xe000

Maarten Brock — 2011-09-16T19:55:55

But these can only be used as RAM accordign to the 
datasheet.


And how is that xdata filled? SDCC assumes the code 
memory is stored in a ROM-like memory and xdata is 
volatile. So during startup it copies initialized data 
from code to xdata. So you have two copies in memory and 
thus your memory footprint has grown. If you use --no-
xinit-opt it is not copied but initialized by lots of 
instructions, usually taking even more code memory.

I guess it works because SDCC's initialization code 
copied it from lower memory to xdata at 0xe000. I also 
guess you missed the downside.

SDCC does not support the concept of preinitialized 
xdata as the FX2 has when it gets the firmware from the 
driver or the I2C eeprom.


Are you using C0 or C2 mode? C2 mode cannot load 0xe000 
according to the datasheet. Can the driver download to 
0xe000 directly?

My advice is to keep these constants in code memory. And 
if you do want to change them at runtime cast a code 
pointer to xdata pointer to access them.

If the driv