Menu

#31 Syntax errors/Port index warning parsing ATMEL BSDL files

0.10
closed-fixed
UrJTAG (101)
5
2008-01-20
2008-01-20
No

I tried the "bsdl test" on various files from

http://www.atmel.com/dyn/resources/prod_documents/bsdl.ziphttp://www.atmel.com/dyn/resources/prod_documents/bsdl.zip

Some yield "Warning ... Port name index not suppored in Boundary Cell description" (e.g. atmega323.bsd) and some just yield an error (e.g. atmega64.bsd):

jtag> bsdl test atmega323.bsd
-W- Warning, Line 302, Port name index not supported in Boundary Cell description.
-W- Warning, Line 302, Port name index not supported in Boundary Cell description.
-N- BSDL file 'atmega323.bsd' compiled correctly
-N- Got IDCODE: 00001001010100000001000000111111

jtag> bsdl test atmega64.bsd
-N- Reading file 'atmega64.bsd'
-E- Error, Line 376, Error in Boundary Cell description.
-E- BSDL file 'atmega64.bsd' contains errors, stopping
bsdl: syntax error!
jtag>

Discussion

  • Arnim Läuger

    Arnim Läuger - 2008-01-20

    Logged In: YES
    user_id=156321
    Originator: NO

    Both error symptoms (the Warning actually flagged a consistency error) should be fixed with svn r935.
    There are three files however that still throw syntax errors (AT90CAN32.BSD, AT90CAN64.BSD, AT90CAN128.BSD). They contain invalid BSDL/VHDL syntax in my opinion (files garbled?).
    Please review and close this item if the output (bsdl dump) meets your requirements.

     
  • Arnim Läuger

    Arnim Läuger - 2008-01-20
    • status: open --> open-fixed
     
  • Kolja Waschk

    Kolja Waschk - 2008-01-20

    Logged In: YES
    user_id=478715
    Originator: YES

    Great, thanks, now it can read my "jim/some_cpu.bsd" as well, and the new "prototype" bus driver can be initialized to access the virtual target. Now it's time to actually implement the virtual bus and some flash "chips"...

     
  • Kolja Waschk

    Kolja Waschk - 2008-01-20
    • status: open-fixed --> closed-fixed
     
  • Kolja Waschk

    Kolja Waschk - 2017-02-12
    • Group: 0.x --> 0.10
     

Log in to post a comment.